← Registry

API Tools

vera.ink

Provides tools to query Vera evidence packs, verify documents asynchronously, poll verification status, and inspect pack coverage and listings via API.

1 endpoint7 known toolsFirst detected September 29, 2026Last detected September 29, 2026

ENDPOINT 1

https://vera-mcp-production.up.railway.app/mcp

No auth detected

MCP server metadata

Name
vera-mcp
Version
1.2.0
Capabilities
tools.listChanged
Server instructions

Use Vera as an evidence layer, not as a source of uncited guesses. 1. Call list_packs before choosing a pack. Select from available_packs and only use a pack whose readiness.query_ready is true. 2. If no relevant query-ready pack exists, do not invent a pack_id and do not run query_pack or verify_document. Propose a concise finite pack plan: name, intended check, authoritative source types, jurisdiction, and version/date requirements. Ask whether the user wants Vera to build it. 3. Never call start_pack_build until the user explicitly approves a specific max_credits integer for that exact pack plan. Explain that it is a hard ceiling, not an estimate or guaranteed charge; work can stop earlier. At current pricing a cap below 28 may pause before one planning/discovery/extraction cycle completes. Do not infer approval from a general request to check a document. 4. start_pack_build requires exactly one of pack_id or new_pack and a unique idempotency_key. Reuse that key only for an exact retry. Poll get_pack_build_status using poll_after_ms only while active=true. Stop when terminal=true or requires_action=true. If your execution window ends, report job_id and resume status polling later; never restart the build merely because polling was interrupted. 5. Read readiness_summary literally: usable_now means the pack can be queried; minimum_coverage_ready means each measured section has at least one locked rule; build_finished means this funded job completed. To claim fully_strengthened, call get_pack_coverage and require readiness.fully_strengthened=true. Never use fully_ready, build_finished, or another signal as a substitute. 6. When requires_action=true, present available_actions without implying that more spending is required. A usable budget-paused pack offers exactly two choices: use_pack now, or start_new_job_with_additional_budget after explicit approval. Never spend automatically. 7. When a build completes with next_action=use_pack, use its pack_id directly or call list_packs again, then continue the user's original task. Clearly explain any budget, credit, or source requirement without claiming unfinished work is complete. 8. For high-stakes work, call get_pack_coverage before relying on a pack. Disclose incomplete coverage or stale sources. 9. Use query_pack to retrieve exact locked rules before drafting. Keep Vera's verified quote and citation distinct from your own inference. 10. verify_document requires an idempotency_key. Reuse the same key only for an exact retry; use a new key whenever the pack, document, or mode changes. Poll get_verification_status using poll_after_ms until terminal is true. 11. Never describe a verification as clean unless the terminal response says verdict=clean, coverage_complete=true, and result_consistent=true. Follow next_action for every other verdict.

Known tools 7

query_pack

Retrieve the best matching locked rules and exact evidence from a query-ready Vera pack.

Inferred read-only
verify_document

Start a paid, asynchronous check against a query-ready pack.

Inferred read-only
get_verification_status

Poll a run using poll_after_ms until terminal=true.

Potential side effects
list_packs

List owned and public packs.

Inferred read-only
get_pack_coverage

Inspect readiness, source coverage and freshness before high-stakes use.

Inferred read-only
start_pack_build

Start a paid asynchronous pack build after the user explicitly approves max_credits.

Inferred read-only
get_pack_build_status

Check a durable pack-build job.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vera-mcp]
url = "https://vera-mcp-production.up.railway.app/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "vera-mcp": {
      "type": "http",
      "url": "https://vera-mcp-production.up.railway.app/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: vera-mcp
Remote MCP URL: https://vera-mcp-production.up.railway.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vera-mcp": {
      "url": "https://vera-mcp-production.up.railway.app/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "vera-mcp": {
      "type": "http",
      "url": "https://vera-mcp-production.up.railway.app/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "vera-mcp",
  "transport": "streamable-http",
  "url": "https://vera-mcp-production.up.railway.app/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for railway.app was fetched 2026-09-24T22:25:30.993Z.

Trust status Trusted

railway.app is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.