Monitor MCP Server

by agentexchange-tooldrift Your server? Claim it

answering

Monitor is answering right now. Last checked 10 min ago. It exposes 3 tools.

Check if an MCP server tool changed or hides injection patterns before you trust it.

Uptime history 65 days of history · worst day 92%

65 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

79 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

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

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add monitor --transport http https://tooldrift.agentexchange.work/mcp

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

{
  "mcpServers": {
    "monitor": {
      "url": "https://tooldrift.agentexchange.work/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.monitor]
url = "https://tooldrift.agentexchange.work/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "monitor": {
      "url": "https://tooldrift.agentexchange.work/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "monitor": {
      "url": "https://tooldrift.agentexchange.work/mcp"
    }
  }
}

Available tools 3

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

drift

get_drift_feed

List MCP tools across the public ecosystem whose definitions recently changed, newest first. Use to see whether a dependency mutated.

findings

get_findings

List tools whose descriptions contain detected injection, concealment, or exfiltration patterns. Filter by severity: critical, high, medium, low.

mcp

check_mcp_server

Check whether an MCP server's tools have changed since they were first recorded, and whether any tool description contains prompt-injection or data-exfiltration patterns. Call this BEFORE trusting a newly added or recently updated MCP server. Returns a verdict of clean or REVIEW_BEFORE_USE.

Endpoints

URL	Transport	State	Latency	Checked
https://tooldrift.agentexchange.work/mcp	streamable-http	answering	53 ms	10 min ago

Alternatives to Monitor

same job, measured the same way

mcp-pin

by gautamtalksdev

Check if an MCP server's tool definitions changed after approval, from a signed public log.

158 installs/wk local only

ChangeDetection.io MCP Server

by rusty4444

MCP server for ChangeDetection.io website monitoring and change history.

100 installs/wk local only

Agentscore

by thezenmonster

MCP security trust layer: scan packages, inspect repos, check exposure, monitor changes.

60 installs/wk local only

OpenWrt MCP

by stanislav-testhub

MCP server that runs on an OpenWrt router: deny-by-default policy, audit log, rollback-armed changes

local only

Scout MCP Local

by scoutapm

An MCP server for Scout Monitoring data interactions.

151 installs/wk local only

Fleet MCP

by simplyminimal

An MCP server that provides tools for managing and monitoring your Fleet Device Management instance.

313 installs/wk local only

Synapse RMCP

by dinglebear

Rust MCP and CLI server for Docker, host inspection, SSH, logs, ZFS, and safe file operations.

local only

MCP Ordali Memory

by robin-deruyck

MCP server for Ordali memory: SQLite-backed project memory and governance traces.

34 installs/wk local only

Monitor — questions

Answers built from our own checks of this server.

What can Monitor do?

It exposes 3 tools, read directly from the server on our last check. Among them: check_mcp_server, get_drift_feed, get_findings. 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 →

Is Monitor 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 79 ms. The bar chart above shows every period we have measured.

How do I connect Monitor?

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 Monitor need an API key?

No. Monitor completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Monitor?

It answers our handshake in 79 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.