Invokary Platform Requirements

What Invokary Platform Requirements MCP server does

Invokary Platform Requirements MCP server helps developers inspect the conditions that platforms apply before listing an MCP connector or plugin. Its dataset covers Claude, ChatGPT, Cursor, and the Official MCP Registry. The service is read-only: it does not submit listings, change platform records, or call the platforms being researched.

Each result includes a text representation and structured output. Results also identify the dataset, its version and date, the applicable license, and attribution. Individual requirements have stable IDs. Retired requirements remain identifiable and can point to a replacement rather than being silently reused.

The dataset records an evidence category for each requirement: verified against platform documentation, sourced from a third party, based on a company claim, or marked as an inference. A verification date indicates when the requirement was last checked.

How it works

Connect an MCP client to https://mcp.invokary.com/mcp using Streamable HTTP. No account, API key, or sign-in is required. The service supports the 2026-07-28 protocol with server/discover and no sessions, while also accepting clients that begin with the 2025 initialize handshake.

The tools read a bundled copy of the Platform Requirements dataset. A daily workflow checks for a newer source snapshot, validates it, runs tests, and redeploys the server when the repository receives the update. Calls do not query external platform systems, so responses remain based on the currently bundled data.

Setup and configuration

Invokary Platform Requirements MCP server needs no environment variables or local credentials for normal use. Add the endpoint as a custom connector or remote MCP server in a compatible client. Claude Code can register it with claude mcp add --transport http platform-requirements https://mcp.invokary.com/mcp. Cursor and VS Code can reference the same URL in their MCP configuration files.

For a direct check, the MCP Inspector can list the available tools with npx @modelcontextprotocol/inspector --cli https://mcp.invokary.com/mcp --method tools/list.

Tools and capabilities

• list_platforms shows supported platforms, vendors, requirement counts, topics, and latest check dates.
• get_platform_requirements returns a platform’s requirements, with optional topic or product-surface filtering.
• get_requirement retrieves a requirement by ID and can identify its replacement when retired.
• compare_platforms places requirements from two or more platforms side by side by topic.
• search_requirements searches by keywords or natural-language questions, including topics such as privacy policies or test cases.
• list_platform_changes returns dated notes about changes to submission rules.

Limitations and notes

The Invokary Platform Requirements MCP server only reads its bundled dataset and cannot verify a platform’s current rules at request time. The dataset may therefore lag a source until the next update. Developers who find an outdated requirement should provide the relevant platform page to Invokary.

The service records request method, tool name, declared client details, protocol version, outcome, and response time. It does not record IP addresses, user agents, or tool arguments. Cloudflare processes the requester’s IP address for delivery and rate limiting without storing it.

The code is licensed under MIT. The data is published under CC BY 4.0 and requires credit to Invokary with a link to the platform dataset. Invokary states that it is independent and not affiliated with Anthropic, OpenAI, or Anysphere.