Talk to your trust infrastructure.

VLI exposes your sealed inventory, compliance state, attestations, registry, and live operational data through the Model Context Protocol — so Claude Code (or any MCP-compatible agent) can query it like a teammate.

Install the MCP → Looking for AI accountability? →

Claude Code on the left talking to the VLI infrastructure stack on the right via the Model Context Protocol

In conversation

What this unlocks.

Ask in plain English. Every answer comes back with a sealed tool call underneath.

Prompt "Show me every cold-chain reading from yesterday that was outside spec, sealed."

</> Underlying tool call

vli_coldseal_readings({
  "from": "2026-04-26T00:00:00Z",
  "to":   "2026-04-26T23:59:59Z",
  "out_of_spec_only": true
})
→ returns array of sealed readings
  with bundle hashes + registry inclusion proofs

Prompt "Who attested to this audit bundle and when?"

</> Underlying tool call

vli_attestations({
  "subject_hash": "sha256:abc123..."
})
→ ordered chain of signed attestations
  (issuer DID + timestamp + signature)

Prompt "What inventory has moved through node 47A this week?"

</> Underlying tool call

vli_inventory_chain({
  "node_id": "47A",
  "since": "2026-04-21"
})
→ custody chain with sealed handoff events
  per item

Catalog

Sixteen tools, seven groups.

Each tool returns signed evidence. Claude doesn't say it happened — it shows you the sealed record.

Group Health & dashboard

vli_dashboard
vli_health

Group Compliance

vli_incidents
vli_compliance_status
vli_attestations

Group Registry

vli_registry_query
vli_seal_event

Group Inventory chain

vli_inventory_status
vli_inventory_item
vli_inventory_chain

Group Patient & check-in

vli_checkin_arrivals
vli_patient_receipts

Group Cold chain

vli_coldseal_nodes
vli_coldseal_readings

Group Members & access

vli_member_activity
vli_members_list

Install

Install + configure

Your SAPI token lives in your Vault session — copy it into VLI_AUTH_TOKEN. Then add to your Claude Code MCP config:

{
  "mcpServers": {
    "vli": {
      "command": "node",
      "args": ["./mcp-server-vli/src/server.js"],
      "env": {
        "VLI_WORKSPACES_API": "https://your-org.vliworkspaces.com",
        "VLI_REGISTRY_API":   "https://verifylinkinfra.com/registry-api",
        "VLI_SAPI_API":       "https://verifylinkinfra.com/sapi-api",
        "VLI_AUTH_TOKEN":     "your-sapi-token",
        "VLI_ORG_ID":         "your-org-id"
      }
    }
  }
}

Source: github.com/VerifyLinkInfra-cloud/mcp-server-vli · Apache 2.0

Built for orgs

Built for organizations.

If your org runs Pact, WorkSpaces, TapIn, or Origin, this MCP turns your operational data into a conversation. Your compliance team can ask in plain English. Your auditors can query receipts directly. Your incident response team can check chain-of-custody without opening a dashboard.

Every response is backed by signed evidence. Claude doesn't say the cold chain stayed in spec — it shows you the sealed reading and the registry inclusion proof.

Open source

Building your own MCP on VLI?

The MCP server is open source. Fork it, extend it, build your own tools that read from VLI infrastructure. Pull request welcome.

github.com/VerifyLinkInfra-cloud/mcp-server-vli →

Sealing AI agent decisions instead? AI Trust MCP at /ai/ →

New to VLI? Read the protocol →