Fix guide

Fix Missing MCP Server Card

A missing MCP server card finding is actionable when the site appears to expose agent-callable tools but no machine-readable MCP metadata is discoverable.

Read-only public scan. No login, no crawler install, and no private URLs are fetched.

Surface
Fix guide
Scope
Public web evidence
Auth
None required
Schema
TechArticle

Answer first

What the issue means

The scanner found MCP-like product or API signals but could not fetch a useful server card from a .well-known discovery path.

Detail 01

Exact fix

Publish metadata that truthfully describes the server, transport endpoint, capabilities, auth model, and documentation link.

Detail 02

Verify

Fetch the card as JSON, validate every URL, avoid claiming unsupported auth or transports, and re-run the MCP/API discovery checker.

FAQ

Common questions

Do all sites need an MCP card?
No. Only publish one when a real MCP-compatible tool surface exists or is intentionally being launched.
Can I publish placeholder MCP metadata?
Do not. Agents may attempt to use advertised tools, so placeholder capabilities create broken integrations and misleading scan evidence.