Discovery

Where the MCP server is

A pointer, not a second transport: the endpoint (POST /mcp, streamable HTTP), the protocol versions it negotiates, the methods that answer without payment, the capabilities actually served, the readable resources on the shelf, and the exact initialize body that completes a handshake. Also served at /.well-known/mcp.json, because half of what probes a well-known path appends the extension. A POST here completes the handshake too, against the same server /mcp answers from — scanners POST their initialize at the manifest path, and a 405 they never read the body of reads to them as no MCP server at all. /mcp remains the canonical endpoint and the one this document names.

get/.well-known/mcp

Request

  • Base URL: https://scvd.store
  • URL: https://scvd.store/.well-known/mcp
  • Auth: none required

Headers

If-None-Matchstring

Send a prior ETag (SHA-256 of exact response bytes). Unchanged content returns 304 with no body.

Response

OK

$schemastring

The SEP-2127 schema URI. The draft's own URI does not resolve yet; it is published as the identifier the spec names, not as a fetchable document.

namestring required
titlestring
versionstring required

Derived from the server's one version constant.

iconsobject[]
descriptionstring
endpointstring uri required
urlstring uri
transportstring required

Streamable HTTP.

methodsstring[]
protocol_versionsstring[] required
authenticationobject

There is nothing to issue: free tools are open and paid ones take a signed x402 payment per call.

handshakeobject
free_methodsstring[]

The methods that never cost anything — tools/list among them, so a client can look before it pays.

capabilitiesobject
resourcesobject[]
documentationstring uri
openapistring uri

Changes

No recorded changes to this operation across all 1 revision of this API.