vera.ink
REMOTE · VERA-MCP-PRODUCTION.UP.RAILWAY.APP
Check documents against rules taken from the law itself. Every finding cites the exact clause.
Available components
Last scanned (3 hours ago)
Scores higher than 91% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Security
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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://vera-mcp-production.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vera-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vera-mcp-production.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://vera-mcp-production.up.railway.app/mcp | HTTPS enforced |
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 →
get_pack_build_status Check a Vera pack build ~76
Check a durable pack-build job. Poll only while active=true. When stopped, use readiness_summary and present available_actions honestly; a usable budget pause offers use now or a separately approved finite continuation. Never restart merely because the AI client's execution window ended.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id returned by start_pack_build |
Structured output declared, but exposes no named fields.
No examples provided.
get_pack_coverage Get a Vera pack's coverage ~84
Inspect readiness, source coverage and freshness before high-stakes use. Disclose incomplete or stale coverage. query_ready means usable, minimum_coverage_ready means every measured section has a rule, and fully_strengthened means every measured section is satisfied. fully_ready is legacy-compatible and is not a comprehensiveness claim.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_id | string | yes | The Vera pack ID |
Structured output declared, but exposes no named fields.
No examples provided.
get_verification_status Check a Vera verification run ~60
Poll a run using poll_after_ms until terminal=true. Only call it clean when verdict=clean, coverage_complete=true, and result_consistent=true; otherwise follow next_action.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The run_id returned by verify_document |
Structured output declared, but exposes no named fields.
No examples provided.
list_packs List available Vera packs ~61
List owned and public packs. Select from available_packs and require readiness.query_ready=true. If none fits, do not guess a pack_id: propose a finite pack plan, ask the user to approve a credit ceiling, then use start_pack_build if approved.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
query_pack Query a Vera pack ~78
Retrieve the best matching locked rules and exact evidence from a query-ready Vera pack. This costs credits. Preserve each verified quote and citation, distinguish them from your inference, and treat coverage=none as no answer.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_id | string | yes | The Vera pack ID (from list_packs) |
| question | string | yes | The question to ask |
Structured output declared, but exposes no named fields.
No examples provided.
start_pack_build Start or continue a Vera pack build ~185
Start a paid asynchronous pack build after the user explicitly approves max_credits. Supply exactly one of pack_id (an owned AI-buildable pack) or new_pack. The response returns immediately with job_id; poll get_pack_build_status only while active=true. max_credits is a hard ceiling, not a promised final charge. Reuse idempotency_key only for an exact retry.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Required retry key; reuse only for this exact build request |
| max_credits | integer | yes | Hard credit ceiling explicitly approved by the user for this build job |
| max_rounds | integer | – | Maximum strengthening rounds; normally 3 |
| new_pack | object | – | A new Vera pack to create; mutually exclusive with pack_id |
| pack_id | string | – | An existing owned AI-buildable pack; mutually exclusive with new_pack |
Structured output declared, but exposes no named fields.
No examples provided.
verify_document Verify a document against a Vera pack ~130
Start a paid, asynchronous check against a query-ready pack. Use one unique idempotency_key and reuse it only for an exact retry. Omit mode to use the pack's mode. Poll get_verification_status until terminal=true.
| Name | Type | Req | Description |
|---|---|---|---|
| document_text | string | yes | The full document text; whitespace does not count toward the minimum |
| idempotency_key | string | yes | Required retry key. Reuse only for this exact pack, document, and mode. |
| mode | string | – | Optional mode override; normally omit this |
| pack_id | string | yes | The Vera pack ID to verify against |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the vera.ink MCP server?
vera.ink is a hosted endpoint at https://vera-mcp-production.up.railway.app/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 · vera-mcp-production.up.railway.app
claude mcp add --transport http ink-vera-vera 'https://vera-mcp-production.up.railway.app/mcp'
What is the vera.ink MCP server?
vera.ink is an MCP server listed in the public MCP registry as ink.vera/vera. Check documents against rules taken from the law itself. Every finding cites the exact clause. This page covers its hosted endpoint (https://vera-mcp-production.up.railway.app/mcp).
Is the vera.ink MCP server safe to use?
vera.ink scores 85 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 vera.ink MCP server expose?
vera.ink exposes 7 tools: query_pack, verify_document, get_verification_status, list_packs, get_pack_coverage, and 2 more. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.
Does the vera.ink MCP server require authentication?
Its publisher declares that vera.ink requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the vera.ink MCP server still maintained?
vera.ink is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.