study.vela/corpus
REMOTE · VELA.STUDY
Read-only MCP access to Vela's corpus of human experience: cited passages, coordinates, reading path
Available components
Last scanned (16 minutes ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1392 tokens (~139/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
- Stability: fail → pass ▲ security
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 86 to 89.
- 10 Oct 26 −2
- Stability: pass → fail ▼ security
- 9 Oct 26 +1
- Stability: 0.93 → pass security
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 93. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 0
- Schema quality: 1262 → 1392 ▼ functional
- Schema quality: excellent → good functional
- New tool “vela.library.reading_list” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://vela.study/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vela.study | CN=YR2,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 59e3e189b9720ddd678934253055af63ffb |
| SANs: vela.study | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vela.study. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| study. | present | 14288 | 13 | Verified |
| vela.study. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vela.study/mcp | Verified | 200 | |
| http (plaintext) | http://vela.study/mcp | HTTPS enforced | 308 | https://vela.study/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
vela.corpus.describe_topic ~93
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]
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| declared | object | yes | – |
| inUse | object | yes | – |
No examples provided.
vela.corpus.ground_claim ~111
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]
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The claim to ground. |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | – |
| hits | array | yes | – |
No examples provided.
vela.corpus.list_topics ~73
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]
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| topics | array | yes | – |
No examples provided.
vela.corpus.query ~248
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]
| Name | Type | Req | Description |
|---|---|---|---|
| axes | object | – | Axis → allowed weights. ALL listed axes must match. e.g. {"religion":["T","s"],"work":["T","s"]} |
| genre | string | – | – |
| include_passages | boolean | – | Include theme-anchored passage pointers. |
| limit | integer | – | – |
| offset | integer | – | – |
| qualities | array | – | Cards carrying ANY of these qualities (emotions, for being-human). |
| text | string | – | Substring match over title / author / one-line claim. |
| themes | array | – | Cards citing ANY of these controlled themes. |
| topic | string | – | Coordinate system to query (topic_configs.slug). |
| Name | Type | Req | Description |
|---|---|---|---|
| applied | object | yes | – |
| hits | array | yes | – |
| returned | number | yes | – |
| topic | string | yes | – |
| total | number | yes | – |
| truncated | boolean | – | – |
No examples provided.
vela.corpus.witness ~315
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-extractor) until PRN-282 lands. FREE for claims; costs one embedding for the passage path. [capability: literary-witness · mirrors: GET /api/vela/witness]
| Name | Type | Req | Description |
|---|---|---|---|
| axes | object | – | Axis weight filters for claims only — same format as vela.corpus.query (e.g. {work:["T","s"]}). |
| condition_slug | string | – | ConditionFrame entity slug (same reservation as problem_slug). |
| emotions | array | – | Emotions to match (e.g. 'shame', 'betrayal', 'grief'). At least one of themes or emotions is required. |
| max_claims | integer | – | Max one-line claims to return (default 3). |
| max_passages | integer | – | Max passages to return (default 5). |
| problem_slug | string | – | ProblemFrame entity slug (echoed in response; reserved for frame_tags[] pre-cache after PA-1153 ID-freeze). |
| themes | array | – | Controlled themes from Vela's vocabulary (e.g. 'fairness', 'recognition'). |
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | – |
| evidence_grade | string | yes | – |
| passages | array | yes | – |
| query | object | yes | – |
No examples provided.
vela.library.reading_list ~130
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]
| Name | Type | Req | Description |
|---|---|---|---|
| emotion | string | – | Emotion primary slug (e.g. grief). Mutually exclusive with theme. |
| limit | integer | – | – |
| theme | string | – | Controlled theme slug (e.g. desire). Mutually exclusive with emotion. |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| limit | number | yes | – |
| ok | boolean | yes | – |
| rows | array | yes | – |
| slug | string | yes | – |
No examples provided.
vela.magazine.relation_floor ~104
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]
| Name | Type | Req | Description |
|---|---|---|---|
| property | string | – | Restrict to one property id; omit for every property with published pieces. |
| Name | Type | Req | Description |
|---|---|---|---|
| properties | array | yes | – |
No examples provided.
vela.magazine.sequence_path ~144
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]
| Name | Type | Req | Description |
|---|---|---|---|
| emotions | array | – | Emotions the reader is steering by. |
| forms | array | – | Article forms to steer by. At least one of emotions/forms is required. |
| limit | integer | – | Pieces to return (default 4). |
| property | string | – | Property id; defaults to vela. |
| Name | Type | Req | Description |
|---|---|---|---|
| path | array | yes | – |
| property | string | yes | – |
No examples provided.
vela.research.get_study ~76
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]
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Catalogue id, e.g. S-01. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| ok | boolean | yes | – |
| problems | array | yes | – |
| profile | object | yes | – |
| study | object | yes | – |
No examples provided.
vela.research.list_studies ~98
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]
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| discovery | object | yes | – |
| note | string | yes | – |
| ok | boolean | yes | – |
| problems | array | yes | – |
| sendable | number | yes | – |
| studies | array | yes | – |
No examples provided.
How do I install the study.vela/corpus MCP server?
study.vela/corpus is a hosted endpoint at https://vela.study/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vela.study
claude mcp add --transport http study-vela-corpus 'https://vela.study/mcp'
What is the study.vela/corpus MCP server?
study.vela/corpus is an MCP server listed in the public MCP registry as study.vela/corpus. Read-only MCP access to Vela's corpus of human experience: cited passages, coordinates, reading path. This page covers its hosted endpoint (https://vela.study/mcp).
Is the study.vela/corpus MCP server safe to use?
study.vela/corpus scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the study.vela/corpus MCP server expose?
study.vela/corpus exposes 10 tools: vela.corpus.query, vela.library.reading_list, vela.corpus.list_topics, vela.corpus.describe_topic, vela.corpus.ground_claim, and 5 more. Their descriptions and schemas cost roughly 1,392 tokens of context every time the server is loaded.
Does the study.vela/corpus MCP server require authentication?
No. We connected to study.vela/corpus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the study.vela/corpus MCP server still maintained?
study.vela/corpus is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.