Skip to main content
ClaudeWave
Invokary avatar
Invokary

platform-requirements-mcp

Ver en GitHub

Read-only MCP server: what Claude, ChatGPT, Cursor and the MCP Registry require before they list a connector.

MCP ServersRegistry oficial0 estrellas0 forks● TypeScriptMITActualizado today
ClaudeWave Trust Score
95/100
✓ Verified
Passed
  • ✓Open-source license (MIT)
  • ✓Actively maintained (<30d)
  • ✓Clear description
  • ✓Topics declared
  • ✓Documented (README)
Last scanned: 10/6/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/Invokary/platform-requirements-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "platform-requirements-mcp": {
      "command": "node",
      "args": ["/path/to/platform-requirements-mcp/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/Invokary/platform-requirements-mcp and follow its README for install instructions.
Casos de uso

Resumen de MCP Servers

# Platform Requirements MCP server

A read-only MCP server for what Claude, ChatGPT, Cursor and the Official MCP Registry require before they list an MCP connector or plugin. Every answer carries the requirement's sources, an evidence label and the date it was last checked.

**Endpoint:** `https://mcp.invokary.com/mcp` (Streamable HTTP, no sign-in)

Maintained by [Invokary](https://invokary.com/open-source). The data is the [Platform Requirements dataset](https://invokary.com/platforms), published under CC BY 4.0.

## Connect

The server needs no account, key or sign-in. Add it by URL:

- **Claude:** add a custom connector with the URL `https://mcp.invokary.com/mcp`.
- **Claude Code:** `claude mcp add --transport http platform-requirements https://mcp.invokary.com/mcp`
- **ChatGPT:** in developer mode, add an MCP server with the URL `https://mcp.invokary.com/mcp`.
- **Cursor:** add this to `.cursor/mcp.json` (or install the plugin in `.cursor-plugin/`):

  ```json
  { "mcpServers": { "platform-requirements": { "url": "https://mcp.invokary.com/mcp" } } }
  ```

- **VS Code:** add this to `.vscode/mcp.json`:

  ```json
  { "servers": { "platform-requirements": { "type": "http", "url": "https://mcp.invokary.com/mcp" } } }
  ```

- **Any client:** try it with the MCP Inspector: `npx @modelcontextprotocol/inspector --cli https://mcp.invokary.com/mcp --method tools/list`

It speaks the 2026-07-28 protocol (`server/discover`, no sessions) and still serves clients that open with the 2025 `initialize` handshake.

## Tools

| Tool | What it does |
|---|---|
| `list_platforms` | Lists the platforms covered, with each one's directory, vendor, number of requirements, topics and latest check date. |
| `get_platform_requirements` | Returns one platform's requirements, optionally narrowed to a topic or a product surface. |
| `get_requirement` | Returns one requirement by id, such as `claude.rule-annotations`, or what replaced it if it was retired. |
| `compare_platforms` | Sets two or more platforms' requirements side by side, grouped by topic. |
| `search_requirements` | Finds requirements matching keywords or a question, such as "privacy policy" or "test cases". |
| `list_platform_changes` | Lists dated notes on changes to the platforms' submission rules. |

Every result has a text form and a structured form (each tool declares an output schema), and both end with the citation: the dataset's name, version, date, license and attribution. [`tools.json`](tools.json) holds the full tool definitions.

All six tools set the same hints, for the same reason: they only read a dataset bundled with the server.

| Hint | Value | Why |
|---|---|---|
| `readOnlyHint` | `true` | The tools read the bundled dataset and change nothing. |
| `destructiveHint` | `false` | Nothing is written or deleted, anywhere. |
| `openWorldHint` | `false` | The tools call no outside system; every answer comes from the bundled data. |
| `idempotentHint` | `true` | The same call returns the same answer until the data is next updated. |

## Data

`data/platform-requirements.json` is a copy of [invokary.com/data/platform-requirements.json](https://invokary.com/data/platform-requirements.json), the dataset's source of truth. A daily workflow ([`sync-data.yml`](.github/workflows/sync-data.yml)) copies a new version when there is one, after it passes validation and the tests, and the server redeploys from the commit.

- Each requirement has a stable `id`. An id is never reused; a removed requirement is listed as retired, with its replacement if there is one.
- `evidence` is `V` (verified against the platform's documentation), `3P` (third-party), `CC` (company claim) or `INF` (inference).
- `verifiedAt` is the date the requirement was last checked against its sources.

Spotted a requirement that is out of date? Open an issue with the platform page that says otherwise, or write to hello@invokary.com.

## Privacy

The server has no accounts and sets no cookies. For each request it records the method, the tool name, the client name and version the client declares, the protocol version, the outcome and the response time. It never records IP addresses, user agents or tool arguments. Cloudflare processes your IP address to deliver the response and to apply a rate limit, and the server does not store it. Invokary's privacy notice is at [invokary.com/legal/privacy](https://invokary.com/legal/privacy#mcp-server).

## Development

```sh
npm ci
npm test            # unit, protocol and HTTP tests, the submission test cases (evals/) and the tools.json check
npm run typecheck
npm run dev         # wrangler dev on http://127.0.0.1:8787/mcp
npm run tools:json  # regenerate tools.json after changing a tool
npm run data:sync   # refresh the dataset snapshot from invokary.com
```

The Worker deploys to `mcp.invokary.com` through Cloudflare Workers Builds on every push to `main`, so no Cloudflare credentials live in this repository.

## License

The code is under the [MIT License](LICENSE). The data in `data/` is under [CC BY 4.0](data/README.md): credit Invokary and link to https://invokary.com/platforms.

Invokary is an independent studio and is not affiliated with Anthropic, OpenAI or Anysphere. Claude, ChatGPT and Cursor are trademarks of their respective owners.
chatgptclaudecloudflare-workerscursormcpmcp-registrymcp-servermodel-context-protocol

Lo que la gente pregunta sobre platform-requirements-mcp

¿Qué es Invokary/platform-requirements-mcp?

+

Invokary/platform-requirements-mcp es mcp servers para el ecosistema de Claude AI. Read-only MCP server: what Claude, ChatGPT, Cursor and the MCP Registry require before they list a connector. Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-10-05.

¿Cómo se instala platform-requirements-mcp?

+

Puedes instalar platform-requirements-mcp clonando el repositorio (https://github.com/Invokary/platform-requirements-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar Invokary/platform-requirements-mcp?

+

Nuestro agente de seguridad ha analizado Invokary/platform-requirements-mcp y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene Invokary/platform-requirements-mcp?

+

Invokary/platform-requirements-mcp es mantenido por Invokary. La última actividad registrada en GitHub es del 2026-10-05, con 0 issues abiertos.

¿Hay alternativas a platform-requirements-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega platform-requirements-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: Invokary/platform-requirements-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/invokary-platform-requirements-mcp)](https://claudewave.com/repo/invokary-platform-requirements-mcp)
<a href="https://claudewave.com/repo/invokary-platform-requirements-mcp"><img src="https://claudewave.com/api/badge/invokary-platform-requirements-mcp" alt="Featured on ClaudeWave: Invokary/platform-requirements-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a platform-requirements-mcp