# vera.ink (remote · vera-mcp-production.up.railway.app)

Check documents against rules taken from the law itself. Every finding cites the exact clause.

- Trust score: 85/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `vera-mcp-production.up.railway.app`: 85/100 (this document), [markdown](https://verifymcp.io/servers/ink-vera-vera/vera-mcp-production.md), [page](https://verifymcp.io/servers/ink-vera-vera/vera-mcp-production)

## Channel facts

- Endpoint: `https://vera-mcp-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

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

### Claude

```bash
claude mcp add --transport http ink-vera-vera 'https://vera-mcp-production.up.railway.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ink-vera-vera": {
      "url": "https://vera-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ink-vera-vera": {
      "type": "http",
      "url": "https://vera-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ink-vera-vera]
url = "https://vera-mcp-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ink-vera-vera": {
      "type": "remote",
      "url": "https://vera-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ink-vera-vera --url 'https://vera-mcp-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ink-vera-vera:
    url: "https://vera-mcp-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ink-vera-vera": {
      "Transport": "http",
      "Url": "https://vera-mcp-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ink-vera-vera -t streamable-http -u 'https://vera-mcp-production.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ink-vera-vera": {
      "type": "http",
      "url": "https://vera-mcp-production.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-29 (score 85, +1)

- [security] Stability: 0.97 → pass

### 2026-10-27 (score 84, +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.

### 2026-10-25 (score 83, +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.

### 2026-10-22 (score 82, +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.

### 2026-10-20 (score 81, +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.

### 2026-10-18 (score 80, +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.

### 2026-10-16 (score 79, +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.

## MCP tools (7)

### `query_pack` (~78 tokens)

Query a Vera pack

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.

Input parameters:

- `pack_id` (string, required): The Vera pack ID (from list_packs)
- `question` (string, required): The question to ask

### `verify_document` (~130 tokens)

Verify a document against a Vera pack

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.

Input parameters:

- `document_text` (string, required): The full document text; whitespace does not count toward the minimum
- `idempotency_key` (string, required): Required retry key. Reuse only for this exact pack, document, and mode.
- `mode` (string): Optional mode override; normally omit this
- `pack_id` (string, required): The Vera pack ID to verify against

### `get_verification_status` (~60 tokens)

Check a Vera verification run

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.

Input parameters:

- `run_id` (string, required): The run_id returned by verify_document

### `list_packs` (~61 tokens)

List available Vera packs

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.

### `get_pack_coverage` (~84 tokens)

Get a Vera pack's coverage

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.

Input parameters:

- `pack_id` (string, required): The Vera pack ID

### `start_pack_build` (~185 tokens)

Start or continue a Vera pack build

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.

Input parameters:

- `idempotency_key` (string, required): Required retry key; reuse only for this exact build request
- `max_credits` (integer, required): 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

### `get_pack_build_status` (~76 tokens)

Check a Vera pack build

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.

Input parameters:

- `job_id` (string, required): The job_id returned by start_pack_build

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ink-vera-vera/vera-mcp-production#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 85
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 84
- 2026-10-27: 84
- 2026-10-26: 83
- 2026-10-25: 83
- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-10: 76
- 2026-10-08: 75
- 2026-10-06: 74
- 2026-10-04: 73
- 2026-10-03: 73

## Common questions

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

## Links

- Remote endpoint: https://vera-mcp-production.up.railway.app/mcp
- Authorisation metadata: https://vera-mcp-production.up.railway.app/.well-known/oauth-protected-resource/mcp
- Website: https://vera.ink/developers
- Changelog RSS feed: https://verifymcp.io/servers/ink-vera-vera/vera-mcp-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/ink-vera-vera/vera-mcp-production.json
- HTML version of this page: https://verifymcp.io/servers/ink-vera-vera/vera-mcp-production