Question 1

What is an MCP Server Card?

Accepted Answer

An MCP Server Card is a small JSON manifest, typically served at /.well-known/mcp/server-card.json, that describes a Model Context Protocol server before an agent connects — its name, description, endpoint URL, transport, authentication and the tools it exposes. It lets agents, registries and readiness scanners discover and describe your server without a full handshake.

Question 2

Where do I put the server card?

Accepted Answer

Serve the generated JSON at https://your-domain/.well-known/mcp/server-card.json. Keep it in sync with your actual server: the endpoint URL, transport (streamable HTTP, SSE or stdio) and tool list should match what your server really exposes.

Question 3

How do I know my server actually works?

Accepted Answer

After publishing the card, health-check the live endpoint with a real protocol handshake using MCP Pulse — it verifies the initialize handshake, lists tools, and measures latency, so you know agents can actually use the server the card advertises.

MCP Server Card generator