Skip to content
Methodology

MCP server card quality

ia.mcp-server-card · 4.18

Act MAY Recommendation AR-ACT-04

Why it matters

An MCP server card should be actionable, not just discoverable. Agents need identity, transport, capabilities, and auth metadata before they can connect safely.

How to fix it

Add serverInfo, a description, a transport, capabilities and auth to the server card.

  1. Complete the server card with all SEP-1649 fields.

    {
  "serverInfo": {"name": "Example MCP", "version": "1.0.0"},
  "description": "Search and read product docs.",
  "transport": {"type": "streamable-http", "endpoint": "https://example.com/mcp"},
  "capabilities": {"tools": {}},
  "auth": {"type": "oauth2"}
}

Verify

curl -sf https://{domain}/.well-known/mcp/server-card.json | jq -e '.serverInfo and .transport and .capabilities'

Expected: exit code 0

Run a new scan for this checkpoint:

isagentready results {domain} --checkpoint ia.mcp-server-card
Details Mapping, lifecycle and references
AR mapping
Full match
Score role
Bonus
Introduced
2026-08-24
Methodology version
2026-10-22

Checkpoint data (JSON)