INDIVIDUAL MCP TOOL

get_record

Fetch ONE of your own records by recordId — the FULL signed body: decision{agent, verdict, reasoning, inputs, actionProposed}, governingRule{ruleId, ruleText}, chainKey, seq, prevHash, bodyHash, signer/custodyClaim, proof, plus anchorState and any external anchor.

getvda.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://witness.getvda.ai/api/witness/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_record and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name or description suggests retrieving external content.

Parent server

getvda.ai

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.vda-witness]
url = "https://witness.getvda.ai/api/witness/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "vda-witness": {
      "type": "http",
      "url": "https://witness.getvda.ai/api/witness/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: vda-witness
Remote MCP URL: https://witness.getvda.ai/api/witness/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": {
    "vda-witness": {
      "url": "https://witness.getvda.ai/api/witness/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "vda-witness": {
      "type": "http",
      "url": "https://witness.getvda.ai/api/witness/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "vda-witness",
  "transport": "streamable-http",
  "url": "https://witness.getvda.ai/api/witness/mcp"
}

MCP Inspector

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

Related tools

get_test_key — Self-issue a SEALED-tier Witness API key IN-BAND (no human, no signup page).
renew_challenge — Step 1 of agent-provable, no-human key renewal for an EXISTING durable account.
renew_key — Step 2 of agent-provable renewal: prove control of your account by signing the challenge nonce with your controller key, and receive a FRESH short-TTL API key bound to the SAME account (same chains continue; prior keys stay valid until they expire — no seal gap).
seal — General-purpose seal (compatibility / unstructured).
seal_hitl_decision — Seal a governance record for a HUMAN-IN-THE-LOOP decision.
seal_agent_action — Seal a record for an action taken AUTONOMOUSLY by an agent under a governing rule.
seal_attestation — Seal an assertion that a fact or state held AS OF a point in time — e.g.
issue_admission_credential — Issue an agent ADMISSION CREDENTIAL — a sealed attestation admitting an agent (subject_did) to a customer environment with a scope, valid until expiry.