# protogrid (remote · api.protogrid.dev)

Find MCP servers by intent and get exactly how to connect to them right now. No proxying.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `api.protogrid.dev`: 72/100 (this document), [markdown](https://verifymcp.io/servers/dev-protogrid-registry/api.md), [page](https://verifymcp.io/servers/dev-protogrid-registry/api)

## Channel facts

- Endpoint: `https://api.protogrid.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-09-27.

- **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**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 709 tokens (~141/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 protogrid MCP server?

protogrid is a hosted endpoint at https://api.protogrid.dev/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 dev-protogrid-registry 'https://api.protogrid.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-protogrid-registry": {
      "url": "https://api.protogrid.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-protogrid-registry": {
      "type": "http",
      "url": "https://api.protogrid.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-protogrid-registry]
url = "https://api.protogrid.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-protogrid-registry": {
      "type": "remote",
      "url": "https://api.protogrid.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-protogrid-registry --url 'https://api.protogrid.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-protogrid-registry:
    url: "https://api.protogrid.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-protogrid-registry": {
      "Transport": "http",
      "Url": "https://api.protogrid.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-protogrid-registry -t streamable-http -u 'https://api.protogrid.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-protogrid-registry": {
      "type": "http",
      "url": "https://api.protogrid.dev/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-09-26 (score 72, +1)

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

### 2026-09-25 (score 71, +7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [functional] Server version: 0.1.0 → 0.2.0

### 2026-09-23 (score 64)

First indexed and scored.

## MCP tools (5)

### `search` (~178 tokens)

Search MCP servers by intent

Hybrid (keyword + semantic) search over servers and their tools. Filter by connection class to keep only what you can reach autonomously (R0, R1).

Input parameters:

- `category` (string)
- `class` (array): Connection classes to keep, e.g. ['R0','R1']
- `exclude_flags` (array): Trust flags, any of which excludes a server, e.g. ['multi-version-spam','duplicate-repo']
- `flags` (array): Trust flags that must all be present
- `limit` (integer): Results to return (default 10)
- `min_trust` (integer): Minimum trust score 0-100
- `q` (string, required): What you want to do, in plain words, e.g. 'send an email' or 'query postgres'
- `transport` (string)

### `get_server` (~84 tokens)

Get a server descriptor

Official server.json plus connectability (class, remotes with auth/health, packages), current tools, trust breakdown and identity for one server name.

Input parameters:

- `name` (string, required): Official reverse-DNS name, e.g. io.github.acme/acme-mcp
- `schemas` (boolean): Include tool input/output schemas (default false; use list_tools for full schemas)

### `list_tools` (~58 tokens)

List a server's tools

Every current tool of a server with full input/output schemas, paginated by tool name.

Input parameters:

- `cursor` (string): next_cursor from the previous page
- `limit` (integer)
- `name` (string, required): Official reverse-DNS name

### `get_connection` (~64 tokens)

Get a connection block

Minimal connection block for the preferred remote (or package) with ${SECRET} placeholders, formatted for a target client. Secrets are never accepted or returned.

Input parameters:

- `name` (string, required): Official reverse-DNS name
- `target` (string): Output format (default mcpServers)

### `check_server` (~150 tokens)

Check an MCP server URL

Probe a remote MCP server URL once, credential-free and without calling its tools, and get its quality checks and its readiness for the Claude and OpenAI directories. Pass `url` to start a check (waits up to 25 s for the result), or `id` to read one. Quota: a few checks per hour anonymously, more with an API key.

Input parameters:

- `id` (string): A check id returned earlier, to read its result
- `url` (string): The server's streamable HTTP or SSE URL, e.g. https://mcp.example.com/mcp. Never include credentials.
- `wait` (integer): Seconds to wait for the result (default 25)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-protogrid-registry/api#diagnostics

## Score history

- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 71
- 2026-09-24: 64
- 2026-09-23: 64

## Common questions

### What is the protogrid MCP server?

protogrid is an MCP server listed in the public MCP registry as dev.protogrid/registry. Find MCP servers by intent and get exactly how to connect to them right now. No proxying. This page covers its hosted endpoint (https://api.protogrid.dev/mcp).

### Is the protogrid MCP server safe to use?

protogrid scores 72 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 protogrid MCP server expose?

protogrid exposes 5 tools: search, get_server, list_tools, get_connection, check_server. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.

### Does the protogrid MCP server require authentication?

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

### Is the protogrid MCP server still maintained?

protogrid is still listed as active in the MCP registry. We last reached this channel on 27 September 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://api.protogrid.dev/mcp
- Website: https://protogrid.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-protogrid-registry/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-protogrid-registry/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-protogrid-registry/api