MCP server for advanced web search using Tavily
Corpus is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read-only MCP access to Vela's corpus of human experience: cited passages, coordinates, reading path
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http vela-corpus-mcp https://vela.study/mcp
# 2 — ask your agent for something these tools do
# vela.corpus.query, vela.library.reading_list, vela.corpus.list_topics and 7 more
Corpus costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http vela-corpus-mcp https://vela.study/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Ask the corpus by COORDINATE rather than keyword. Filter works by axis weights (e.g. religion ∈ {T,s} AND work ∈ {T,s} returns the God-and-Work source set across genres), controlled themes, qualities/emotions, genre, and free text. Returns card metadata: the one-line claim, themes, coordinates, qualities. FREE and read-only. [capability: library-extraction-cards · mirrors: POST /api/corpus/query]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Coordinate system to query (topic_configs.slug). |
| axes | object | no | Axis → allowed weights. ALL listed axes must match. e.g. {"religion":["T","s"],"work":["T","s"]} |
| themes | array | no | Cards citing ANY of these controlled themes. |
| qualities | array | no | Cards carrying ANY of these qualities (emotions, for being-human). |
| genre | string | no | — |
| text | string | no | Substring match over title / author / one-line claim. |
| include_passages | boolean | no | Include theme-anchored passage pointers. |
| limit | integer | no | — |
| offset | integer | no | — |
The reading list an emotion or theme page shows: books with one-line claims and a short attributed passage (≤300 chars). Exactly one of emotion or theme. FREE and read-only. Every url carries ?ref=mcp for citation arrival measurement. [capability: library-extraction-cards · mirrors: GET /api/corpus/reading-list]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| emotion | string | no | Emotion primary slug (e.g. grief). Mutually exclusive with theme. |
| theme | string | no | Controlled theme slug (e.g. desire). Mutually exclusive with emotion. |
| limit | integer | no | — |
List the coordinate systems the corpus can be queried through — each with its thesis, axes, and controlled vocabularies. Call this before vela.corpus.query to learn what axes and themes exist. FREE and read-only. [capability: topic-coordinate-systems · mirrors: GET /api/corpus/topics]
No parameter schema on file.
Describe ONE topic in full — its axes and their operative definitions, its complete controlled theme and quality vocabularies, plus the vocabulary actually IN USE across the corpus with counts. The declared vocabulary and the used vocabulary are different facts; this returns both. FREE and read-only. [capability: topic-coordinate-systems · mirrors: GET /api/corpus/topics/:slug]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | — |
Ground a claim in the corpus: hybrid semantic + theme retrieval over real passages, returning citations with source, passage code, scores, and a SHORT snippet. Use to check whether the corpus supports, complicates or is silent on an assertion. COSTS a small amount (one embedding per call). [capability: corpus-ingestion-dual-grade · mirrors: internal — lib/audit/retrieve.ts]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| claim | string | yes | The claim to ground. |
| limit | integer | no | — |
Literary Witness Rail (ASN-1577): return passages and one-line claims from Vela's 762-work corpus that illuminate the given themes and/or emotions. Designed for frame-family profile pages — PersonFrame × ProblemFrame × ConditionFrame — to add an inside-out layer (what writers who lived this say) alongside the outside-in portrait the frame join produces. Results carry evidence_grade 'T1' (single-ex
| Parameter | Type | Required | Notes |
|---|---|---|---|
| themes | array | no | Controlled themes from Vela's vocabulary (e.g. 'fairness', 'recognition'). |
| emotions | array | no | Emotions to match (e.g. 'shame', 'betrayal', 'grief'). At least one of themes or emotions is required. |
| axes | object | no | Axis weight filters for claims only — same format as vela.corpus.query (e.g. {work:["T","s"]}). |
| problem_slug | string | no | ProblemFrame entity slug (echoed in response; reserved for frame_tags[] pre-cache after PA-1153 ID-freeze). |
| condition_slug | string | no | ConditionFrame entity slug (same reservation as problem_slug). |
| max_passages | integer | no | Max passages to return (default 5). |
| max_claims | integer | no | Max one-line claims to return (default 3). |
Ask what this magazine would actually give a reader who said they wanted these things. Returns the REAL sequenced path with the rationale for each piece — the same core the anonymous intake calls, not a preview. Read-only: writes nothing and records no signal. [capability: adaptive-magazine-engine · mirrors: POST /api/magazine/start-path]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| emotions | array | no | Emotions the reader is steering by. |
| forms | array | no | Article forms to steer by. At least one of emotions/forms is required. |
| property | string | no | Property id; defaults to vela. |
| limit | integer | no | Pieces to return (default 4). |
Whether a magazine's corpus can support the adaptive promise its pages render. Reports, per property, each relational dimension's fill AND its separating power — a field present on every piece with one distinct value carries no information, so fill rate alone is misleading. Read-only. [capability: adaptive-magazine-engine · mirrors: npm run magazine:relation-floor]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| property | string | no | Restrict to one property id; omit for every property with published pieces. |
List FieldStation research ideas as a library-kit DiscoveryDTO. Each card is a study we can support, not a running participant surface. The honesty gate (limitations, readiness, doNotClaim) is enforced by research:catalog-check — this tool publishes that same file. FREE and read-only. Presence is gated; truth is not. [capability: study-catalogue · mirrors: GET /api/research/studies]
No parameter schema on file.
One FieldStation study as a library-kit ProfileDTO plus the raw StudyRecord. Unknown id is an error. FREE and read-only. [capability: study-catalogue · mirrors: GET /api/research/studies/:id]
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Catalogue id, e.g. S-01. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Corpus or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Corpus can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.