monitor
Check if an MCP server tool changed or hides injection patterns before you trust it.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
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": {
"monitor": {
"url": "https://tooldrift.agentexchange.work/mcp"
}
}
}Remote endpoints
https://tooldrift.agentexchange.work/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢check_mcp_server(url, 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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "The MCP server's HTTP endpoint to probe live."
},
"server": {
"type": "string",
"description": "Registry name of the server, if the URL is unknown."
}
}
}🟢get_drift_feed(limit)
List MCP tools across the public ecosystem whose definitions recently changed, newest first. Use to see whether a dependency mutated.
Input Schema
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"description": "Max rows, default 25."
}
}
}🟢get_findings(severity, limit)
List tools whose descriptions contain detected injection, concealment, or exfiltration patterns. Filter by severity: critical, high, medium, low.
Input Schema
{
"type": "object",
"properties": {
"severity": {
"type": "string"
},
"limit": {
"type": "integer"
}
}
}Community
Evidence