VerifiedState Memory

io.github.verifiedstatePublished by GitHub account verifiedstatev1.1.0Updated Oct 24, 2026

Verified memory for AI agents. Signed assertions, billing attestation, session continuity.

The publisher's own server: Memory.fit

VerifiedStreamable HTTPWeb executableKnowledge & MemorySecurity & Monitoring

Overview

AI-generated overview

VerifiedState Memory is a remote MCP server that gives AI assistants verified memory, with signed assertions, billing attestation and session continuity.

What you can do
Provides verified memory for AI agents, so an assistant can carry context across sessions with session continuity support. Records signed assertions and billing attestation alongside that memory. Connects over a remote streamable HTTP endpoint authenticated with an API key. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs persistent, verifiable memory between sessions, or when signed assertions and billing attestation matter for auditability. It is less useful if you only need ordinary local note storage.
Requirements
A remote endpoint at mcp.verifiedstate.ai over streamable HTTP. OAuth authentication is required, using an Authorization header carrying a Bearer token, which is a VerifiedState API key obtained from the provider's keys page. No local runtime or packages are needed.
Before you install
The server requires an API key sent as a Bearer token in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configuration. Memory content and assertions are stored with a third-party remote service, so consider what data you let the assistant persist there. Billing attestation implies usage may be metered or charged.

Installation

In SourceWeft

  1. Open VerifiedState Memory in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.verifiedstate%2Fverifiedstate-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "verifiedstate-memory": {
      "type": "http",
      "url": "https://mcp.verifiedstate.ai/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations