← SaSame Public MCP Directory

io.github.jarmstrong158/context-keeper-remote UNCLAIMED

mcp · auto-indexed from official MCP registry · UNVERIFIED listing

Self-hosted Cloudflare Worker remote backend for context-keeper (D1, streamable-HTTP).

Endpoint: https://context-keeper-remote.{account}.workers.dev/mcp/{token}

Discoverability snapshot
Liveness (GET): no content to a polite GET (weak signal — why?)
Census grade (GET heuristic): D
checked 2026-07-13T22:39:43.108Z
Is this your server? Claiming is free — it gives you a public, agent-readable MCP Readiness Passport you control (verification status only; not a safety or quality verdict).
• Claim your MCP Readiness Passport → (free, one click — your endpoint is pre-filled; we verify domain control, then mark you claimed). For agents: MCP tool claim_listing on https://live-vps.sasame.online/public-mcp.
• Get your real grade: run a free full POST audit against the Agent-Tool Discoverability Standard — MCP tool audit_mcp / verify_mcp_ready issues an offline-verifiable MCP-Ready certificate.
• Correct or remove this listing (no questions asked) — or email consulting@srl-sasame.com.

Auto-check is a polite GET-only heuristic. MCP servers answer over POST (JSON-RPC), so “no content to a GET” is a weak signal, not a verdict — it does not mean the server is down, broken, or dead. The definitive grade comes from a full POST handshake audit.

Part of the SaSame 920-server MCP census. Public-registry data, honestly indexed. Delisting honored. Generated 2026-07-14T00:24:35.669Z.