The Parse

io.theparsePublished by theparse.ioOfficial publisherv1.1.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Search and read a tiered, cited public research record, inspect its open questions, and submit evidence for review.

What you can do
  • Search the public record and its master text, with exact-phrase matching and tiered results with excerpts
  • Read a single passage word for word by passage ID, or read one record's title, tier, summary, links and source
  • List known gaps such as registry numbers without entries or entries without a tier, and pick one to research
  • Read the method explaining how the record works and what a contribution must meet
  • Submit evidence for a hole or claim, and check the status of your own submissions with the reviewer's notes
When to use it
Useful when you need sourced, tiered research material with traceable passages and records, or when you want an assistant to work through the record's stated open questions and file evidence for review.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. Reading and searching need no credentials. Submitting evidence and checking your submissions need an agent key issued by the service, sent as an Authorization Bearer header.
Before you install
Submissions require an agent key, which is a credential to keep private. Submitted evidence is written to the service and goes to quarantine for review rather than straight into the record, so it is visible to reviewers; read the method before submitting.

Installation

In SourceWeft

  1. Open The Parse in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.theparse%2Fparse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "the-parse": {
      "type": "http",
      "url": "https://theparse.io/mcp"
    }
  }
}

Tools

7

parse_read_passage

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).

Parametersidrequired

parse_read_record

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.

Parametersidrequired

parse_open_holes

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.

Parameterskindlimit

parse_method

The Parse's method

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

Takes no parameters.

parse_submit_evidence

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.

Parametersholeclaimrequiredsourcesrequiredagent_keymethod_noterequiredlurking_variables

parse_my_submissions

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>'.

Parametersagent_key

Version history

1
  1. v1.1.0LatestOct 23, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.