MCP Server for server card generation, validation and discovery — .well-known/mcp-server-card.json protocol
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"agent-server-card-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP Server Cards An MCP server for generating, validating, and discovering MCP server cards — a standardized way to describe MCP servers so AI agents can automatically find and understand them. ## What are Server Cards? Server Cards are machine-readable JSON files that describe an MCP server's capabilities, similar to how `robots.txt` describes crawling rules or `manifest.json` describes web apps. They live at `.well-known/mcp-server-card.json` and contain: - **Name & Description** — What the server does - **Tools** — List of available tools with descriptions - **Author & Repository** — Who built it, where to find the source - **Categories** — Tags for discovery and search - **Pricing** — Whether it's free, freemium, or paid - **Transport** — Whether it uses stdio, HTTP, or both - **Auth** — Whether authentication is required ## Why Server Cards? As the MCP ecosystem grows, agents need a way to discover and evaluate servers automatically. Server Cards solve this by providing: 1. **Automatic Discovery** — Agents can check `.well-known/mcp-server-card.json` on any domain 2. **Standardized Metadata** — Consistent format for comparing servers 3. **Capability Description** — Agents know what tools are available before connecting 4. **Trust Signals** — Author, repository, and pricing information ## Installation ```bash pip install agent-server-card-mcp ``` ## Usage ### As MCP Server ```json { "mcpServers": { "server-cards": { "command": "server-card-server" } } } ``` ### With uvx ```json { "mcpServers": { "server-cards": { "command": "uvx", "args": ["agent-server-card-mcp"] } } } ``` ## Available Tools | Tool | Description | |------|-------------| | `generate_card` | Generate a `.well-known/mcp-server-card.json` for any MCP server | | `validate_card` | Validate a server card against the JSON schema | | `discover` | Try to discover a server card from a URL via `.well-known` | | `search` | Search indexed server ca…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.