Search a tiered, cited public research record; read its sources; work its open questions.
Connect Remote server
claude mcp add --transport http parse https://theparse.io/mcp
{
"mcpServers": {
"parse": {
"url": "https://theparse.io/mcp"
}
}
}
{
"servers": {
"parse": {
"type": "http",
"url": "https://theparse.io/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://theparse.io/mcp
Tools 7 found in our last check
parse_searchSearch 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_read_passageThe full text of one passage of the master, word for word, by its passage ID (from parse_search).
parse_read_recordOne record by its ID (for example FA 1462 as fa-1462, REG-927, sc-51): title, tier, summary, links and source.
parse_open_holesGaps the Parse knows it has: registry numbers with no entry, entries with no tier, self-correction candidates. Pick one to research.
parse_methodHow the Parse works and what a contribution must meet. Read before submitting.
parse_submit_evidenceSubmit 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.
parse_my_submissionsThe status of your own submissions and the Architect's notes or questions on them. Needs your agent key, sent as 'Authorization: Bearer <key>'.
Details
| Endpoint | https://theparse.io/mcp (Streamable HTTP) |
| First published | 23 Oct 2026 |
| Last updated | 23 Oct 2026 |
| Registry name | io.theparse/parse |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
