Agentguard47 runs on your own machine — the client starts it, so there is no endpoint to ping. 58 installs a week from npm. Last commit 31 Oct 2026.
Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.
We read the source, 1 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
subprocess.Popen(
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
subprocess.Popen(
normalized_trace = os.path.normpath(os.path.join(config_dir, normalized_trace))
…"bundle":{"mediaType":"application/vnd.dev.sigstore.bundle.v0.3+json","verificationMaterial":{"certificate":{"rawBytes":"MIIG8TCCBnegAwIBAgIUObrZhtSkVaCIYNJYUSPSi2LDia0wCgYIKoZIzj0EAwMwNzEVMBMGA1UEChMMc2lnc3RvcmUuZGV2MR4wHAYDVQQDExVzaWdzdG9yZS1pbnRlcm1lZGlhdGUwHhcNMjYwOTE1MDIzODM…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Agentguard47 and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add agentguard47 -e 'AGENTGUARD_API_KEY=<AGENTGUARD_API_KEY>' -- npx -y @agentguard47/mcp-server
{
"mcpServers": {
"agentguard47": {
"command": "npx",
"args": [
"-y",
"@agentguard47/mcp-server"
],
"env": {
"AGENTGUARD_API_KEY": "<AGENTGUARD_API_KEY>"
}
}
}
}
[mcp_servers.agentguard47]
command = "npx"
args = ["-y", "@agentguard47/mcp-server"]
env = { AGENTGUARD_API_KEY = "<AGENTGUARD_API_KEY>" }
{
"mcpServers": {
"agentguard47": {
"command": "npx",
"args": [
"-y",
"@agentguard47/mcp-server"
],
"env": {
"AGENTGUARD_API_KEY": "<AGENTGUARD_API_KEY>"
}
}
}
}
{
"servers": {
"agentguard47": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agentguard47/mcp-server"
],
"env": {
"AGENTGUARD_API_KEY": "<AGENTGUARD_API_KEY>"
}
}
}
}
Put your own value in place of
<AGENTGUARD_API_KEY> (AgentGuard read API key for querying traces, alerts, costs, usage, and savings).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
AGENTGUARD_URL (Optional AgentGuard API base URL. Defaults to production).
Read-only admin MCP server for LastSaaS — dashboards, users, tenants, billing, logs, health.
CLI and MCP server for Gradient MSP Synthesize: usage push, billing drift, alert tracing.
MCP server for querying Foxhound traces from Claude Code, Cursor, and other MCP clients
Read-only semantic filtering, code search, log triage and traceable evidence for AI agents.
MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.
MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.
MCP server for Microsoft Entra ID sign-in and audit-log triage (read-only by default)
MCP server for Blackpoint Cyber MDR — alerts, threats, and operations.
Answers built from our own checks of this server.