---
title: "The product MCP server card"
method: GET
path: "/mcp/v1"
tags: ["MCP"]
---

# The product MCP server card

`GET /mcp/v1`

## Request

- Base URL: `https://youspot.com`
- URL: `https://youspot.com/mcp/v1`
- Auth: none required

The same document as https://youspot.com/.well-known/mcp/server-card.json, built from the live tool table, when `Accept` names `application/mcp-server-card+json` or `text/html`. Without a credential, any other `GET` answers 401 with the OAuth challenge, so a client discovering sign-in is pointed at the RFC 9728 document.

## Headers

- `If-None-Match` string

## Response `200`

The card.

- McpServerCard
  - `$schema` string, uri
  - `name` string, required: Reverse-DNS, e.g. `com.youspot/youspot`.
  - `title` string
  - `description` string, required
  - `version` string, required
  - `url` string, uri, required: Where to POST JSON-RPC.
  - `serverUrl` string, uri
  - `endpoint` string, uri
  - `transport` 'streamable-http', required
  - `kind` string: `product`, `docs` or `sandbox`.
  - `instructions` string
  - `protocolVersions` string[]
  - `documentationUrl` string, uri
  - `websiteUrl` string, uri
  - `capabilities` object
  - `authentication` object
    - `type` string
    - `required` boolean
    - `description` string
  - `tools` object[], required: Names and one-line summaries. The typed schemas come from `tools/list`.
    - `name` string, required
    - `description` string

## Other responses

- `304`: The document has not changed since the ETag you sent. No body.
- `401`: No credential and no card type in `Accept`. `WWW-Authenticate` names the protected-resource metadata.

---

[API](https://skmtc.dev/youspot/apis/youspot-http-api.md) · [All operations](https://skmtc.dev/youspot/apis/youspot-http-api/llms.txt) · [OpenAPI document](https://skmtc.dev/youspot/apis/youspot-http-api/revisions/6615ad5d017d?raw)