Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.4hmetuyar/agent-graph-auditor

NPM · @GUARDBEE/MCP-AGENT-GRAPH-AUDITOR

Finds transitive excessive agency across LangGraph/CrewAI/AutoGen orchestration graphs

0 this week 85 Trust /100

Last scanned (16 hours ago)

Scores higher than 77% of npm servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 21 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 319 tokens (~79/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
  • 19 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 10 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 9 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@guardbee/mcp-agent-graph-auditor@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~319 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_patterns ~30

List every dangerous-capability rule this auditor looks for at the end of a delegation path, grouped by category

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scan_directory ~136

Recursively scan a directory of Python files and report excessive-agency paths found in each. Each file's agent/tool graph is analyzed independently — variable references don't resolve across files, so a Crew/GroupChat whose members are defined in a different file than the assembling call won't be connected.

NameTypeReqDescription
excludearray–Skip files/dirs whose path contains one of these strings
includearray–Only scan files whose path contains one of these strings
maxFilesinteger–Maximum number of files to scan (default: 2000)
pathstringyesAbsolute or relative path to the directory to scan

No output schema declared.

No examples provided.

scan_file ~49

Scan a single Python file for excessive-agency paths across LangGraph/CrewAI/AutoGen orchestration constructs

NameTypeReqDescription
pathstringyesAbsolute or relative path to the .py file to scan

No output schema declared.

No examples provided.

scan_text ~104

Scan a Python snippet defining a multi-agent orchestration (LangGraph, CrewAI, or AutoGen/ag2) for excessive agency reachable through delegation or group membership — an agent with no dangerous tool of its own that can still reach one (shell/code-exec/file-write/network/credentials) through another agent it can hand off to.

NameTypeReqDescription
contentstringyesThe Python source to scan
labelstring–Optional label shown in findings (e.g. filename)

No output schema declared.

No examples provided.

Install

How do I install the io.github.4hmetuyar/agent-graph-auditor MCP server?

io.github.4hmetuyar/agent-graph-auditor runs locally as an npm package, launched with npx -y @guardbee/mcp-agent-graph-auditor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @guardbee/mcp-agent-graph-auditor

# add to Claude Code
claude mcp add 4hmetuyar-agent-graph-auditor -- npx -y @guardbee/mcp-agent-graph-auditor
Common questions

What is the io.github.4hmetuyar/agent-graph-auditor MCP server?

io.github.4hmetuyar/agent-graph-auditor is an MCP server listed in the public MCP registry as io.github.4hmetuyar/agent-graph-auditor. Finds transitive excessive agency across LangGraph/CrewAI/AutoGen orchestration graphs. This page covers its npm package (@guardbee/mcp-agent-graph-auditor).

Is the io.github.4hmetuyar/agent-graph-auditor MCP server safe to use?

io.github.4hmetuyar/agent-graph-auditor scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.4hmetuyar/agent-graph-auditor MCP server expose?

io.github.4hmetuyar/agent-graph-auditor exposes 4 tools: scan_text, scan_file, scan_directory, list_patterns. Their descriptions and schemas cost roughly 319 tokens of context every time the server is loaded.

Is the io.github.4hmetuyar/agent-graph-auditor MCP server still maintained?

io.github.4hmetuyar/agent-graph-auditor is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.4hmetuyar/agent-graph-auditor MCP server under?

io.github.4hmetuyar/agent-graph-auditor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.4hmetuyar/agent-graph-auditor MCP server?

VerifyMCP ran 16 checks on io.github.4hmetuyar/agent-graph-auditor, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.