AgentGuard MCP Server (vaasu202/agentguard) is an MCP server listed on the M8ven Trust Index. It scores 52 out of 100, grade D. It declares 6 tools. No publisher has claimed this listing.

Caution

52/100

AgentGuard MCP Server

Item: AgentGuard MCP Server
Rating: 52
Author: M8ven

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.

→ vaasu202/agentguard · listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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 push why 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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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: 3 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.

// tools this server exposes6 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

github_search_issues

Searches issues in the configured repository through an AgentGuard read policy.

slack_send_message

Sends a message only after AgentGuard scans and sanitizes outbound content.

database_query

Runs an allowlisted read query through the guarded database adapter.

database_execute

Demonstration-only administrative database tool protected by default-deny policies.

deployment_rollback

Creates a production rollback request that always pauses for human approval.

billing_issue_refund

Issues a refund subject to role, amount, and approval policies.

// known CVEs in dependencies3 critical1 low

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

criticalnext@16.2.12GHSA-2xp9-vwfh-vxw4

Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used

criticalnext@16.2.12GHSA-p293-qw3h-jr36

Next.js: Unauthenticated Remote Code Execution on windows-hosted servers

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

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

lowvitest@3.2.4GHSA-82fw-gwwq-j7x9

Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock

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

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.

Production dependencies are patched

2 critical, 0 high severity in production deps — next@16.2.12 (critical), next@16.2.12 (critical)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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?variant=verified)](https://m8ven.ai/mcp/vaasu202/agentguard)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 37aaf3fd6511c23afac26f9709cbc2cb634ea988

code hash: c3f23ceb84a82dc18f52a4a8cb80962b70643d01c888f5561c6969aff176bf15

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