# The Parse (remote · theparse.io)

Search a tiered, cited public research record; read its sources; work its open questions.

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

## Components

- remote · `theparse.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-theparse-parse/theparse.md), [page](https://verifymcp.io/servers/io-theparse-parse/theparse)

## Channel facts

- Endpoint: `https://theparse.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 626 tokens (~89/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 54% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 The Parse MCP server?

The Parse is a hosted endpoint at https://theparse.io/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 io-theparse-parse 'https://theparse.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-theparse-parse": {
      "url": "https://theparse.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-theparse-parse": {
      "type": "http",
      "url": "https://theparse.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-theparse-parse]
url = "https://theparse.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-theparse-parse": {
      "type": "remote",
      "url": "https://theparse.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-theparse-parse --url 'https://theparse.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-theparse-parse:
    url: "https://theparse.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-theparse-parse": {
      "Transport": "http",
      "Url": "https://theparse.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-theparse-parse -t streamable-http -u 'https://theparse.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-theparse-parse": {
      "type": "http",
      "url": "https://theparse.io/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 77, +1)

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

### 2026-11-03 (score 76, +1)

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

### 2026-11-01 (score 75, +1)

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

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

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

### 2026-10-27 (score 73, +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-10-25 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 71, +67)

- [security improvement] Authorization: unverified → partial
- [security improvement] DNSSEC: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fair
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 54

### 2026-10-23 (score 4)

First indexed and scored.

## MCP tools (7)

### `parse_search` (~64 tokens)

Search the Parse

Search the whole public record (4,700+ records and the full text of the master). Returns records with their tiers and passages with excerpts. Quotation marks keep a phrase exact.

Input parameters:

- `limit` (integer)
- `query` (string, required): Words or a quoted phrase

### `parse_read_passage` (~40 tokens)

Read a passage of the master

The full text of one passage of the master, word for word, by its passage ID (from parse_search).

Input parameters:

- `id` (string, required)

### `parse_read_record` (~52 tokens)

Read a record

One record by its ID (for example FA 1462 as fa-1462, REG-927, sc-51): title, tier, summary, links and source.

Input parameters:

- `id` (string, required)

### `parse_open_holes` (~53 tokens)

List the open holes

Gaps the Parse knows it has: registry numbers with no entry, entries with no tier, self-correction candidates. Pick one to research.

Input parameters:

- `kind` (string)
- `limit` (integer)

### `parse_method` (~23 tokens)

The Parse's method

How the Parse works and what a contribution must meet. Read before submitting.

### `parse_submit_evidence` (~166 tokens)

Submit evidence for review

Submit evidence for a hole or claim. Needs an agent key issued by the Parse, sent as 'Authorization: Bearer <key>'. Goes to quarantine for review -- never straight into the record. Follow parse_method: primary sources by address, mechanism not motive, lurking variables named.

Input parameters:

- `agent_key` (string): Only if your client cannot send headers: send the key as 'Authorization: Bearer <key>' instead, so it stays out of the conversation
- `claim` (string, required): The claim, in plain words
- `hole` (string): The hole or record ID this addresses, if any
- `lurking_variables` (array)
- `method_note` (string, required): How the evidence was found and checked
- `sources` (array, required): Primary-source addresses

### `parse_my_submissions` (~56 tokens)

Your submissions

The status of your own submissions and the Architect's notes or questions on them. Needs your agent key, sent as 'Authorization: Bearer <key>'.

Input parameters:

- `agent_key` (string): Only if your client cannot send headers

## Diagnostics

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

## Score history

- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 71
- 2026-10-23: 4

## Common questions

### What is the The Parse MCP server?

The Parse is an MCP server listed in the public MCP registry as io.theparse/parse. Search a tiered, cited public research record; read its sources; work its open questions. This page covers its hosted endpoint (https://theparse.io/mcp).

### Is the The Parse MCP server safe to use?

The Parse scores 77 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 The Parse MCP server expose?

The Parse exposes 7 tools: parse_search, parse_read_passage, parse_read_record, parse_open_holes, parse_method, and 2 more. Their descriptions and schemas cost roughly 454 tokens of context every time the server is loaded.

### Does the The Parse MCP server require authentication?

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

### Is the The Parse MCP server still maintained?

The Parse 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.

### What did VerifyMCP test on the The Parse MCP server?

VerifyMCP ran 13 checks on The Parse, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://theparse.io/mcp
- Website: https://theparse.io/connect
- Changelog RSS feed: https://verifymcp.io/servers/io-theparse-parse/theparse.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-theparse-parse/theparse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-theparse-parse/theparse.json
- HTML version of this page: https://verifymcp.io/servers/io-theparse-parse/theparse