Proof flow
Live agent proof flow
The page points agents at the existing OpenInvoke flow instead of pretending this is the official MCP Registry.
GET /agent-index.jsonFetch the route map agents should use first.
SearchGET /api/search?q=submit%20mcp%20serverSearch the catalog by intent, not logo memory.
Inspect JSONGET /services/untitledui-mcp.jsonRead an MCP-style service card with honest callable status.
Inspect MarkdownGET /services/untitledui-mcp.mdUse a lower-token human-readable summary when that is enough.
GET /agent-index.json
GET /api/search?q=submit%20mcp%20server
GET /services/untitledui-mcp.json
GET /services/untitledui-mcp.mdHonest boundaries
- OpenInvoke is not the official MCP Registry.
- OpenInvoke is not a hosted MCP JSON-RPC endpoint.
- Free submission means reviewed intake, not instant publication.
- A listing improves agent-readable packaging and search fit. It does not guarantee ChatGPT, Claude, Google, or any external assistant will recommend the server.
- Local STDIO MCP servers can be listed, but callable status must be honest. Do not label them as hosted APIs unless that is verified.
Example service IDs
Measurement
Privacy-safe activation markers
These pages expose data attributes for activation reporting. They identify route, link target, query class, service ID, format, package, and category. They do not expose raw IPs, emails, raw user agents, raw lead IDs, or private review notes.
- organic_page_view: route=/submit-mcp-server, source_class, campaign_class, landing_route
- organic_proof_flow_click: route=/submit-mcp-server, target=/api/search, query=submit mcp server
- service_card_inspected: route=/submit-mcp-server, service_id=untitledui-mcp, format=json|markdown
- listing_submission_intent: route=/submit-mcp-server, package=Free listing, category=Developer tooling
- listing_submission_success: route=/submit-mcp-server, source_class, submission_package=Free listing, no raw lead ID in public reports
