mcpbeat Sign in

Directory Submission Retention Proof MCP Server

answering

Directory Submission Retention Proof is answering right now. Last checked 6 min ago. It exposes 5 tools.

Pre-submission escrow receipts and coverage-aware retention diffs.

Uptime history 70 hours of history
70 hours agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
320 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Directory Submission Retention Proof every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 6 min ago.

run in your terminal
claude mcp add directory-submission-retention-proof --transport http https://textforagents.com/products/directory-submission-retention-proof/mcp
Settings → Connectors → Add custom connector, then paste this address
https://textforagents.com/products/directory-submission-retention-proof/mcp
~/.codex/config.toml
[mcp_servers.directory-submission-retention-proof]
url = "https://textforagents.com/products/directory-submission-retention-proof/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "directory-submission-retention-proof": {
      "url": "https://textforagents.com/products/directory-submission-retention-proof/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "directory-submission-retention-proof": {
      "type": "http",
      "url": "https://textforagents.com/products/directory-submission-retention-proof/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

retention
retention_diff
Coverage-aware diff of published state against an escrow.
retention_escrow
Escrow a submission bundle -> HMAC retention receipt ($0.50; first free once per operator).
retention_packet
Recovery packet (receipt + diff + preserve-ID checklist) for support.
watch
watch_check
Run a watch check now (real fetch for the MCP Registry shape).
watch_create
Create a retention watch on an escrow (subscription required).

Endpoints

URLTransportStateLatencyChecked
https://textforagents.com/products/directory-submission-retention-proof/mcp streamable-http answering 318 ms 6 min ago

Alternatives to Directory Submission Retention Proof

same job, measured the same way
Coverageshield
by djanacek

Insurance coverage requirements, gap detection, and risk profiles for US businesses.

11 installs/wk local only
B
BotSupply
by iambrettforbes

Verifiable purchase receipts for agents: record approval and proof. Wallets and escrow (test mode).

14 tools answering
Verzi Health
by verzi

Medicare DME coverage by HCPCS code and date of service, with CMS citations and signed receipts.

6 tools answering
TechSnif
by techsnif

Agent-first tech news: ranked story clusters, coverage and discussion links, trends, and events.

13 installs/wk 13 tools answering
DiffCI
by adityankale190895

Change-aware CI validation and affected-test guidance for coding agents.

749 installs/wk 3 tools answering
Cronometer
by ekelly95

Your Cronometer diary, nutrition with honest coverage (missing is never zero), and safe writes.

684 installs/wk local only
Conarium
by dogrucanemek-alt

Governed database access for AI assistants: masking, signed receipts, coverage reconciliation.

175 installs/wk local only
RewindMap
by rewindmap

Historical borders and dated map events with source attribution and coverage limits.

4 tools answering

Directory Submission Retention Proof — questions

Answers built from our own checks of this server.

What can Directory Submission Retention Proof do?
It exposes 5 tools, read directly from the server on our last check. Among them: retention_diff, retention_escrow, retention_packet, watch_check, watch_create. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Directory Submission Retention Proof mostly used for?
Its tools cluster around retention and watch. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Directory Submission Retention Proof working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 320 ms. The bar chart above shows every period we have measured.
How do I connect Directory Submission Retention Proof?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Directory Submission Retention Proof need an API key?
No. Directory Submission Retention Proof completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Directory Submission Retention Proof?
It answers our handshake in 320 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.