vera.ink

ink.veraPublished by vera.inkv1.2.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemorySecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that checks documents against rule packs drawn from legal text, returning findings with exact clause citations.

What you can do
List owned and public rule packs and inspect their readiness, source coverage and freshness before relying on them. Query a query-ready pack for the best matching locked rules and exact evidence, with verified quotes and citations. Start a paid asynchronous document verification against a pack, then poll its status until it finishes and read the verdict, coverage and consistency flags. Start a paid asynchronous pack build after an approved credit ceiling, and poll the build job while it is active.
When to use it
Useful when an assistant must check a document against rules grounded in legal clauses and every finding needs a citable source. Also suited to reviewing whether a pack's coverage is complete or stale before high-stakes use.
Requirements
Remote streamable HTTP endpoint; no local package. Requires a bearer token in the Authorization header, created in the provider's developer console. Network access to the provider's endpoint.
Before you install
Queries, document verification and pack builds consume credits and cost money; pack builds need an explicit approved maximum credit ceiling. Documents submitted for verification are sent to a third party. Verification and build runs are asynchronous and must be polled; a clean result should only be claimed when the verdict, coverage and consistency checks all pass.

Installation

In SourceWeft

  1. Open vera.ink in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ink.vera%2Fvera/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vera-ink": {
      "type": "http",
      "url": "https://vera-mcp-production.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

7

query_pack

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.

Parameterspack_idrequiredquestionrequired

verify_document

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.

Parametersmodepack_idrequireddocument_textrequiredidempotency_keyrequired

get_verification_status

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.

Parametersrun_idrequired

list_packs

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.

Takes no parameters.

get_pack_coverage

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.

Parameterspack_idrequired

start_pack_build

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.

Parameterspack_idnew_packmax_roundsmax_creditsrequiredidempotency_keyrequired

get_pack_build_status

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.

Parametersjob_idrequired

Version history

1
  1. v1.2.1LatestSep 29, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.