C
Warning
74/100
1 day ago

AgentGuard MCP Server

Provides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

vaasu202

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: SLACK_BOT_TOKEN, PYTHON_SERVICE_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 7 credentials: GITHUB_TOKEN, LITELLM_API_KEY, OPENAI_API_KEY, PYTHON_SERVICE_API_KEY, QDRANT_API_KEY, SLACK_BOT_TOKEN, VLLM_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configGITHUB_REPOSITORY
🔐 secretGITHUB_TOKEN
🔐 secretLITELLM_API_KEY
configLITELLM_BASE_URL
configLITELLM_MODEL
🔐 secretOPENAI_API_KEY
configOPENAI_DEFAULT_MODEL
🔐 secretPYTHON_SERVICE_API_KEY
configPYTHON_SERVICE_URL
🔐 secretQDRANT_API_KEY
configQDRANT_URL
🔐 secretSLACK_BOT_TOKEN
configSLACK_CHANNEL_ID
🔐 secretVLLM_API_KEY
configVLLM_BASE_URL
configVLLM_MODEL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployNEXT_PUBLIC_APP_URL
// quality suggestions

Dependencies

23 dependencies, 1 flagged: @playwright/test

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

6/6 tools missing one or more hints — github_search_issues (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); slack_send_message (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); database_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/6 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (PYTHON_SERVICE_API_KEY → dynamic) (1 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/vaasu202-agentguard-bklt11?variant=verified)](https://m8ven.ai/mcp/vaasu202-agentguard-bklt11)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 8a382e7c3d844d14209b6dbe65bdc0d047d3ed1e
code hash: 760ccdb7ceec8e7889ab171680b3d35387dea1f2f85964cee6811af248dd9ff2
verified: 8/18/2026, 4:04:12 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client