vera.ink

vera.ink gives your AI a set of rules taken from the source itself: legislation, standards and official guidance.

Community: Submitted by a user or imported; check the owner before granting accessOnlineAPI key requiredGlobalFreeRead-only

What it can do

  • Query 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
  • Verify Document: 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_verificati
  • Get Verification Status: 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.

What data it sees

Do you need an account

An API key from the service settings is required

vera.ink gives your AI a set of rules taken from the source itself: legislation, standards and official guidance. It checks a document against them and returns every gap with the exact clause it rests on, the quoted source text, and replacement wording. The answers come from the rule, not from the model's memory.

  • Check a document: a privacy policy, cookie notice, contract or code file, against a pack.
  • Ask a pack a question: get the matching rules with the quoted evidence.
  • Build a pack you don't have: describe the coverage and the jurisdiction. vera.ink fetches sources, extracts rules and checks every quote word for word against its source before locking it. You set a hard credit ceiling.

Public packs: UK GDPR & PECR (website privacy and cookies), WCAG 2.2, OWASP Top 10:2025, OWASP API Top 10:2023, security headers, and US severance-release (OWBPA/ADEA) compliance.

Seven tools: list_packs, get_pack_coverage, get_verification_status and get_pack_build_status are free; query_pack costs 2 credits; verify_document costs 3–8 credits by length; start_pack_build runs to a ceiling you set. New accounts get 40 credits.

Tested end to end in Claude Code. ChatGPT and the Claude apps are not supported yet.

How to connect

How to connect vera.ink to Claude

The server address to paste into Claude settings:

https://vera--simon-kiea.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect vera.ink to ChatGPT

The server address to paste into ChatGPT settings:

https://vera--simon-kiea.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect vera.ink to Cursor

The server address to paste into Cursor settings:

https://vera--simon-kiea.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (7)

Raw names from tools/list. Only developers need these.

query_packRetrieve 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.
verify_documentStart 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.
get_verification_statusPoll 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.
list_packsList 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_coverageInspect 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.
start_pack_buildStart 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.
get_pack_build_statusCheck 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.