# Invokary Platform Requirements (remote · mcp.invokary.com)

What Claude, ChatGPT, Cursor and the MCP Registry require to list an MCP connector or plugin.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.invokary.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-invokary-platform-requirements/mcp.md), [page](https://verifymcp.io/servers/com-invokary-platform-requirements/mcp)

## Channel facts

- Endpoint: `https://mcp.invokary.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 583 tokens (~97/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Invokary Platform Requirements MCP server?

Invokary Platform Requirements is a hosted endpoint at https://mcp.invokary.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-invokary-platform-requirements 'https://mcp.invokary.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-invokary-platform-requirements]
url = "https://mcp.invokary.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-invokary-platform-requirements": {
      "type": "remote",
      "url": "https://mcp.invokary.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-invokary-platform-requirements --url 'https://mcp.invokary.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-invokary-platform-requirements:
    url: "https://mcp.invokary.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-invokary-platform-requirements": {
      "Transport": "http",
      "Url": "https://mcp.invokary.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-invokary-platform-requirements -t streamable-http -u 'https://mcp.invokary.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `list_platforms` (~62 tokens)

List platforms

Lists the platforms in the Platform Requirements dataset (Claude, ChatGPT, Cursor and the Official MCP Registry): each one's directory, vendor, number of requirements, topics and latest check date. Use it to see what the dataset covers and which ids the other tools take.

Output parameters:

- `citation` (object)
- `platforms` (array)
- `protocolRequirementCount` (number)

### `get_platform_requirements` (~138 tokens)

Get a platform's requirements

Returns what one platform requires before it lists an MCP connector or plugin, each requirement with its sources, evidence label and the date it was last checked. Narrow the list to one topic (category) or one product surface. Platforms: claude (Claude), chatgpt (ChatGPT), cursor (Cursor), mcp-registry (MCP Registry), ecosystem (MCP specification).

Input parameters:

- `category` (string): Only requirements on this topic.
- `platform` (string, required): The platform id.
- `productSurface` (string): Only requirements that hold for this product surface, e.g. claude-connectors or claude-plugins.

Output parameters:

- `citation` (object)
- `platform`
- `requirements` (array)

### `get_requirement` (~67 tokens)

Get one requirement

Returns one requirement by its id, for example claude.rule-annotations, with its sources and the date it was last checked. For a retired id it returns the retirement date and the requirement that replaced it.

Input parameters:

- `id` (string, required): The requirement id, as returned by the other tools.

Output parameters:

- `citation` (object)
- `replacement` (object)
- `requirement` (object)
- `retired` (object)

### `compare_platforms` (~89 tokens)

Compare platforms

Sets the requirements of two or more platforms side by side, grouped by topic, to show where they differ, for example on authentication or on what a submission needs. Leave platforms out to compare all four directories.

Input parameters:

- `category` (string): Only this topic.
- `platforms` (array): Two or more platform ids. Default: claude, chatgpt, cursor, mcp-registry.

Output parameters:

- `citation` (object)
- `platforms` (array)
- `topics` (array)

### `search_requirements` (~78 tokens)

Search requirements

Finds requirements whose text matches keywords or a question, such as "privacy policy", "OAuth" or "test cases", across every platform or within one. Returns up to 10 matches, best first, with their sources and check dates.

Input parameters:

- `platform` (string): Only this platform.
- `query` (string, required): Keywords or a question.

Output parameters:

- `citation` (object)
- `query` (string)
- `requirements` (array)

### `list_platform_changes` (~81 tokens)

List platform changes

Lists Invokary's dated notes on changes to these platforms' submission rules, most recently updated first, optionally for one platform or updated on or after a date. Each note links to its full text.

Input parameters:

- `platform` (string): Only notes about this platform.
- `since` (string): Only notes updated on or after this date (YYYY-MM-DD).

Output parameters:

- `changes` (array)
- `citation` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-invokary-platform-requirements/mcp#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 80
- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-10: 74
- 2026-10-07: 72

## Common questions

### What is the Invokary Platform Requirements MCP server?

Invokary Platform Requirements is an MCP server listed in the public MCP registry as com.invokary/platform-requirements. What Claude, ChatGPT, Cursor and the MCP Registry require to list an MCP connector or plugin. This page covers its hosted endpoint (https://mcp.invokary.com/mcp).

### Is the Invokary Platform Requirements MCP server safe to use?

Invokary Platform Requirements scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Invokary Platform Requirements MCP server expose?

Invokary Platform Requirements exposes 6 tools: list_platforms, get_platform_requirements, get_requirement, compare_platforms, search_requirements, list_platform_changes. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.

### Does the Invokary Platform Requirements MCP server require authentication?

No. We connected to Invokary Platform Requirements without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Invokary Platform Requirements MCP server still maintained?

Invokary Platform Requirements is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.invokary.com/mcp
- Repository: https://github.com/Invokary/platform-requirements-mcp
- Website: https://invokary.com/open-source
- Changelog RSS feed: https://verifymcp.io/servers/com-invokary-platform-requirements/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-invokary-platform-requirements/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-invokary-platform-requirements/mcp