Retention Policy Planner MCP Server

io.github.Wxt-ai/profile-retention-key-identifier

not responding

Retention Policy Planner is listed as active in the registry but did not answer our last check.

Plan a profile governance setting

Uptime history 41 hours of history · worst hour 0%

41 hours agonow

0.0%

Uptime 24h

0 of 91 checks

—

Tools

hidden behind auth

6 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add profile-retention-key-identifier --transport http https://antibody-package-occasional-floppy.trycloudflare.com/mcp/profile-retention-key/upstream

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "profile-retention-key-identifier": {
      "url": "https://antibody-package-occasional-floppy.trycloudflare.com/mcp/profile-retention-key/upstream"
    }
  }
}

~/.codex/config.toml

[mcp_servers.profile-retention-key-identifier]
url = "https://antibody-package-occasional-floppy.trycloudflare.com/mcp/profile-retention-key/upstream"

.cursor/mcp.json

{
  "mcpServers": {
    "profile-retention-key-identifier": {
      "url": "https://antibody-package-occasional-floppy.trycloudflare.com/mcp/profile-retention-key/upstream"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "profile-retention-key-identifier": {
      "url": "https://antibody-package-occasional-floppy.trycloudflare.com/mcp/profile-retention-key/upstream"
    }
  }
}

Endpoints

URL	Transport	State	Latency	Checked
https://antibody-package-occasional-floppy.trycloudflare.com/mcp/profile-retention-key/upstream	streamable-http	answering	6 ms	12 min ago

Retention Policy Planner — questions

Answers built from our own checks of this server.

Is Retention Policy Planner working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 6 ms. The bar chart above shows every period we have measured.

The registry lists Retention Policy Planner as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Retention Policy Planner?

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.

Does Retention Policy Planner need an API key?

No. Retention Policy Planner completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.