Integrations › MCP

Protocol

Every MCP Client. One Trusted State Layer.

Advanced path: add the hosted MCP server. Prefer vsync init for capture + hot-context.

Get API Key →
12MCP tools
0.01mslookup
Freefor individuals
ed25519signed

The Problem

MCP gives agents tools. It doesn't give them Trusted State. Between sessions, everything resets. Agents re-learn. Users repeat themselves. When something goes wrong, there's no History & Sources for what the agent believed.

Memory flows between MCP clients. Receipts prove it.

• • • Claude Desktop
> Remember: deploy target is us-east-1
✓ Stored · rct_d41a · 0.95
• • • Cursor
> Where do we deploy?
✦ 1 verified assertion
us-east-1 — stored via Claude Desktop.
Receipt: rct_d41a

Two clients. One memory. Same receipt.

Step 1
Connect
→
Step 2
Ingest + Extract
→
Step 3
Verify + Receipt

The Fix

Connect my first agentReturns here after auth · then run vsync init

Shortest path for most users: vsync init. Advanced MCP-only:

json
npx @verifiedstate/sync init # Prefer this — provisions key, MCP, daemon, hot-context. # Advanced MCP-only (Bearer API key required): { "mcpServers": { "verifiedstate": { "url": "https://mcp.verifiedstate.ai/mcp", "headers": { "Authorization": "Bearer vs_live_..." } } } } // 23 tools available: // Memory: memory_ingest, memory_query, memory_verify, memory_health, memory_query_events, memory_subscribe // Meter (Proof Meter — related product): meter_authorize, meter_spend, meter_budget, meter_settle, meter_verify, meter_receipts // Session: session_save, session_load, session_list, session_delete, session_end // State: working_state_get, working_state_update // Alerts: alerts_get_unacknowledged, alerts_acknowledge, alerts_resolve // Teams: teams_list

What You Get Back

✓ VERIFIED
receipt.json
{ "receipt_id": "rct_7f3a...", "assertion": "User prefers dark mode", "status": "verified", "confidence": 0.94, "signature": "ed25519:a8c3f1...", "verified_at": "2026-04-06T14:32:01Z", "chain_position": 42 }

Without VerifiedState vs. With VerifiedState

FeatureWithoutWith VerifiedState
Between sessions Agent forgets Trusted State continuity
Fact conflicts Silent overwrite Auto-detected + flagged
History & Sources Nothing Full provenance chain
Proof of knowledge "Check the logs" Signed receipt

FAQ

Which MCP clients work?

Any MCP-compatible client — Claude Desktop, Cursor, Windsurf, Goose, Cline, Continue, OpenCode, and custom clients. Protocol version 2024-11-05.

Do I need the SDK too?

No. The MCP server IS the integration. SDK is for programmatic access.

How fast?

Zero-hop existence checks in 0.01ms. Full retrieval under 100ms.

Related Integrations

Never explain your project twice.

Add VerifiedState once. Keep project state available across your AI agents.