Goose Runs. VerifiedState Remembers.

MCP-native verified memory for Goose.

Get API Key →

12MCP tools

0.01mslookup

Freefor individuals

ed25519signed

The Problem

Goose is Block's open-source agent with 27k+ stars. It's MCP-native. But between sessions, context resets. Autonomous decisions happen without an audit trail. When something goes wrong, there's no receipt of what Goose believed.

Step 1

Connect

→

Step 2

Ingest + Extract

→

Step 3

Verify + Receipt

The Fix

No install — Goose is MCP-native:

json
{
  "mcpServers": {
    "verifiedstate": {
      "url": "https://mcp.verifiedstate.ai/mcp",
      "headers": {
        "Authorization": "Bearer vs_live_..."
      }
    }
  }
}
// Goose now has verified memory across sessions
// All 23 VerifiedState tools available

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

Feature	Without	With VerifiedState
Session memory	Resets every session	Persistent verified memory
Autonomous decisions	No paper trail	Signed receipt per action
Multi-project	Separate contexts	Namespace-isolated memory

FAQ

Does Goose already support MCP?

Yes. Goose is MCP-native. Just add the server config and restart.

Related Integrations

Start building with verified memory.

Free: 50,000 assertions/month. No credit card. No trial expiration.

Get Free API Key Read the Docs GitHub →