mcpbeat Sign in

SPM MCP Server

answering

SPM is answering right now. Last checked 10 min ago.

Agent memory that refuses to guess: evidence-gated recall, exact-source reads, verifiable deletion.

Uptime history 6 days of history · worst day 97%
6 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
514 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

SPM does not always answer

Over the last week it answered 99.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add spm --transport http https://api.spmos.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "spm": {
      "url": "https://api.spmos.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.spm]
url = "https://api.spmos.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "spm": {
      "url": "https://api.spmos.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "spm": {
      "url": "https://api.spmos.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://api.spmos.ai/mcp streamable-http needs key 1490 ms 10 min ago

Alternatives to SPM

same job, measured the same way
A202
by a202-protocol

Verifiable agreements for agent-led commerce: mandates, obligations, evidence, transaction records.

local only
Attestari
by attestari

Auditable memory for AI agents: provable deletion, tamper-evident audit, time-travel recall.

146 installs/wk local only
Homestead Memory
by fuckbigtech-ai

Tamper-evident record of what your AI agent did, plus local-first verifiable memory.

529 installs/wk local only
Elite Reasoning MCP
by snehgabani

Evidence-gated verification, selection, and measurement MCP for coding agents.

43 installs/wk local only
Fireweed
by starksood

Agent memory where every fact carries a receipt, and deletion is provable.

333 installs/wk local only
Netcafe Memory
by ainetcafe

Cross-session, cross-device memory for your agent: remember and recall notes. No key to start.

4 tools answering
Kodiak
by azurecarbon

Verifiable fact-checking: verdict, confidence, sources, and a tamper-evident certificate.

60 installs/wk local only
AI Agent Firewall
by fidacy

Every agent action watched, every money-moving one gated, every verdict independently verifiable.

local only

SPM — questions

Answers built from our own checks of this server.

Why is there no tool list for SPM?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is SPM working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 514 ms. The bar chart above shows every period we have measured.
How do I connect SPM?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to SPM?
No API key is involved. SPM answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is SPM?
It answers our handshake in 514 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.