ActionGuard Protocol Inspector Agent
Diff and poisoning detection for MCP servers: catch schema drift and prompt poisoning.
Should I use this
Quality & Safety
A
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~181Tokens (tool definitions)
~572 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": {
"actionguard": {
"url": "https://actionguard.ai/mcp"
}
}
}Remote endpoints
https://actionguard.ai/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢actionguard_inspect(url)
Run a 5-stage continuous reliability, security, and schema audit of an MCP server or AI agent endpoint.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "The target MCP server or agent endpoint URL to audit"
}
},
"required": [
"url"
]
}🟢actionguard_check_drift(url, pinnedSchemaHash)
Verify whether an MCP server's tools schema or descriptions have drifted from a pinned Dual-Hash.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "The target MCP server endpoint URL"
},
"pinnedSchemaHash": {
"type": "string",
"description": "Pinned 64-char hex SHA-256 schema hash"
}
},
"required": [
"url",
"pinnedSchemaHash"
]
}Community
Evidence
Recent observations
verifiedversion not recorded2 tools