# MCP server cards

> A JSON file that describes a remote MCP server before anyone connects.

Source: https://agentrelations.org/standards/mcp-server-cards

## What it is

A server card is a small file that lists a remote server’s transports, versions and tools, so a client or registry can learn what is there without connecting.

An analogy

The sign outside a shop that lists opening hours and what it sells.

## At a glance

Owner

MCP project (SEP-2127)

Maturity

Emerging Reported final on 2026-10-06; the primary page has not been confirmed. Served at /.well-known/mcp/server-card.json.

Where it lives

[MCP project](https://modelcontextprotocol.io/)

Framework domain

[Converse: Be asked](https://agentrelations.org/framework/domains/converse)

What it serves

- Make your MCP server discoverable
- Say what it supports before a connection

## Who should care

The roles this standard touches most. See all the roles on the personas page.

- **Engineering and product.** Build the access, data, endpoints and actions that agents use, on open standards.

[Framework personas →](https://agentrelations.org/framework/personas)

## How to adopt it

1. 1
Publish the card at /.well-known/mcp/server-card.json.
1. 2
Keep its tool list in step with the server.
1. 3
Check it against the final schema before you rely on it.

## The Institute’s view

Adopt with care

A sensible small file. Because its final status is reported rather than confirmed, check the schema before you invest in tooling around it.

Standards change fast. Last reviewed November 2026.

[← Back to the Standards Map](https://agentrelations.org/standards)
