vera.ink connects to your AI assistant as an MCP server. Your AI can then check a document against a pack of rules taken from the source itself — the legislation, the standard, the official guidance — and every finding comes back naming the exact clause it rests on, with the quoted source text. Not the model's memory.
01 / WHAT YOUR AI CAN DO
- Check a document. A privacy policy, cookie notice, contract, or code file, against a pack. Every gap, the clause behind it, and replacement wording.
- Ask a pack a question. Get the matching rules back with the exact quoted source text, so your AI answers from the rule rather than from memory.
- Build a pack you don't have yet. Describe what it must cover and in which jurisdiction. vera.ink finds and fetches sources, extracts the rules, and checks every rule's quote word for word against the page it cites before locking it. You set a hard credit ceiling first, and the build never spends past it.
02 / PACKS READY NOW
- Website Privacy & Cookies — UK GDPR and PECR
- Web Accessibility — WCAG 2.2
- Web Application Security — OWASP Top 10:2025
- API Security — OWASP API Security Top 10:2023
- Security Headers & Transport — OWASP
- US Severance Release — OWBPA/ADEA waiver compliance
Ask your AI to run list_packs for the current list, and get_pack_coverage to see exactly what a pack covers before you rely on it. Anything not on the list, you can build.
03 / CONNECT IN TWO MINUTES
1. Get a key. Sign in and create one on the API keys page: https://vera.ink/api-keys — it starts with vk_ and is shown once. Treat it like a password.
2. Claude Code — one command:
claude mcp add --transport http vera https://vera-mcp-production.up.railway.app/mcp \ --header "Authorization: Bearer vk_YOUR_KEY" --scope user
Then ask Claude: "List my Vera packs."
3. Cursor — add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"vera": {
"url": "https://vera-mcp-production.up.railway.app/mcp",
"headers": { "Authorization": "Bearer vk_YOUR_KEY" }
}
}
}Other clients. Any MCP client that can reach a remote HTTP server and send an Authorization header. Claude Code is the client we have tested end to end.
Not yet: ChatGPT and the Claude apps (claude.ai, desktop and mobile) connect through a sign-in flow that is not switched on yet.
04 / THE SEVEN TOOLS
- list_packs — your packs and the public ones. Free.
- get_pack_coverage — what a pack covers, and how fresh it is. Free.
- query_pack — the rules that answer a question, with quoted evidence. 2 credits.
- verify_document — check a document against a pack. 3 credits up to about 4,500 words, 5 up to 10,000, 8 up to 15,000.
- get_verification_status — follow a check until it finishes. Free.
- start_pack_build — build or strengthen a pack. You set max_credits; it is a ceiling, not a price.
- get_pack_build_status — follow a build. Free.
05 / CREDITS
New accounts start with 40 credits — about a dozen short checks. Plans start at $19 a month for 250 credits: https://vera.ink/pricing
06 / GOOD TO KNOW
- A finding cites a locked rule, and every rule carries the source text it was taken from, so you can check it yourself.
- A pack says what it covers. If a result matters, read get_pack_coverage first.
- A newly built pack is only as good as its sources. Read its rules before relying on it.
- vera.ink is a review aid, not legal advice.
- Keep your key out of chat transcripts and shared repositories. Revoke it any time on the API keys page.