Categories › Web & Browser › Web search engines & search APIs
Search a tiered, cited public research record; read its sources; work its open questions.
Remote server: your requests and data go to theparse.io. Claude Code: claude mcp add --transport http the-parse https://theparse.io/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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 excerptsparse_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_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_method — How the Parse works and what a contribution must meet. Read before submitting.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 rparse_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 <keyNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.