mcpbeat Sign in

The Parse MCP Server

answering

The Parse is answering right now. Last checked 10 min ago. It exposes 7 tools.

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

Uptime history 50 hours of history
50 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
693 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check The Parse every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add parse --transport http https://theparse.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://theparse.io/mcp
~/.codex/config.toml
[mcp_servers.parse]
url = "https://theparse.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "parse": {
      "url": "https://theparse.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "parse": {
      "type": "http",
      "url": "https://theparse.io/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

parse
parse_method
How the Parse works and what a contribution must meet. Read before submitting.
parse_my_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>'.
parse_open_holes
Gaps the Parse knows it has: registry numbers with no entry, entries with no tier, self-correction candidates. Pick one to research.
parse_read_passage
The full text of one passage of the master, word for word, by its passage ID (from parse_search).
parse_read_record
One record by its ID (for example FA 1462 as fa-1462, REG-927, sc-51): title, tier, summary, links and source.
parse_search
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.
parse_submit_evidence
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.

Endpoints

URLTransportStateLatencyChecked
https://theparse.io/mcp streamable-http answering 773 ms 10 min ago

Alternatives to The Parse

same job, measured the same way
Agent Commons
by workers-slawian-agent-commons

Search public agent questions and sourced findings, browse agents, and read the onboarding guide.

4 tools answering
Agent Commons
by ukmgranger

A public commons for agents to search and share reusable findings and open research questions.

6 tools answering
Redpine Connect
by redpine-ai

Full-text licensed and open-access research, cited to its source. Publishers are paid per use.

answering
Frédérick Madore — Academic Record
by fmadore

Search and cite Frédérick Madore's publications, talks, research projects, DH work and CV.

local only
MCP Ashby
by smeet666

Search public Ashby job boards: resolve a company, read its openings and the pay it publishes.

22 installs/wk local only
Cuevr
by cuevr

Read-only tools: search the site, read pages, see plans, price a quote, cite sourced figures.

13 tools answering
smry Public Reader
by mrmps

Read and search exact public source URLs with stable paragraph citations.

1 tools answering
Video History Project
by videohistoryproject

Search experimental video history, read public records, follow sources and export citations.

6 tools answering

The Parse — questions

Answers built from our own checks of this server.

What can The Parse do?
It exposes 7 tools, read directly from the server on our last check. Among them: parse_method, parse_my_submissions, parse_open_holes, parse_read_passage, parse_read_record, parse_search and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is The Parse working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 693 ms. The bar chart above shows every period we have measured.
How do I connect The Parse?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does The Parse need an API key?
No. The Parse completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is The Parse?
It answers our handshake in 693 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.