Registry Rot Watch

Registry Rot Watch: liveness + successor-contract verdicts for MCP endpoints.

Should I use this

Quality & Safety

B
Description quality
78%
Schema completeness
30%
Naming quality
92%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'add_watch' description lacks action verbin add_watch

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~180Tokens (tool definitions)
~51 BTypical response size
Minimal attention impact (0.14% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "registry-rot-watch": {
      "url": "https://textforagents.com/products/registry-rot-watch/mcp"
    }
  }
}

Remote endpoints

https://textforagents.com/products/registry-rot-watch/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_verdict

Latest vault verdict for an endpoint ($0.01/call; one free trial query per operator)

Input Schema

{
  "type": "object"
}
⚪probe_endpoint

Live anonymous MCP probe of an endpoint, stored to the vault ($0.01/call)

Input Schema

{
  "type": "object"
}
🟢successor_check

Successor-contract verdict from the stored pre-move snapshot ($0.01/call)

Input Schema

{
  "type": "object"
}
🟡add_watch

Watch an endpoint for status/contract changes (watch entitlement required)

Input Schema

{
  "type": "object"
}
🟢list_watches

List your watches and alerts

Input Schema

{
  "type": "object"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools