VerifiedState adds a cryptographic receipt to every assertion your MCP agent makes.
Facts Flow Through MCP Without Verification
1
No persistent verified memory between sessions
2
Agent beliefs have no audit trail
3
No receipts on agent decisions
The Fix: Three Lines of Code
Install the SDK. Ingest a fact. Get a signed receipt.
bash
npm install @verifiedstate/sdk
typescript
import { VerifiedStateClient } from '@verifiedstate/sdk';
const client = new VerifiedStateClient({ apiKey: 'vs_live_...' });
// Store and verify a fact from your MCP agent
const artifact = await client.ingest({
namespace_id: 'ns_1',
content: 'User prefers dark mode',
source_type: 'mcp_agent',
});
const extracted = await client.extract({
namespace_id: 'ns_1',
artifact_id: artifact.artifact_id,
});
const receipt = await client.verify({
assertion_id: extracted.assertion_ids[0],
namespace_id: 'ns_1',
});
// receipt.status -> "verified", receipt.confidence -> 0.94
What Your MCP Agent Gets Back
A cryptographic receipt — not just a database row. Signed, timestamped, queryable.
// Every fact gets a receipt like this:
{
"receipt_id": "rc_7f3a...",
"assertion": "User prefers dark mode",
"status": "verified",
"confidence": 0.94,
"signature": "ed25519:abc123...",
"verified_at": "2026-03-15T09:14:22Z"
}
Frequently Asked Questions
How does VerifiedState integrate with MCP?
+
Install the @verifiedstate/sdk package and call client.ingest() to store facts from your MCP agent. Each fact is cryptographically signed and returns a queryable receipt. Three lines of code.
What does a "verified" fact mean?
+
A verified fact has been through the VerifiedState verification pipeline: ingested, assertions extracted, confidence scored, and signed with an Ed25519 cryptographic receipt. The receipt is queryable, auditable, and proves what was believed at the moment of decision.
Is VerifiedState free?
+
Yes. The free tier includes 25,000 decision traces per month. No credit card required. Enterprise tiers available for regulated industries.
Is this production-ready?
+
VerifiedState is currently in beta. It is suitable for development, testing, and early production workloads. It is not yet certified for production use in regulated industries (healthcare, financial services, legal) without independent compliance review. We are actively working toward SOC 2 and HIPAA certification.