agent-utils (gibtang/agent-utils) is an MCP server listed on the M8ven Trust Index. It scores 56 out of 100, grade D. It declares 8 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
56/100

agent-utils

One API key. Agent-native utilities for AI agents. File hosting, PII redaction, dead letter queues, and more.

→ gibtang/agent-utils· listed on github_repo_search

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

⚡ 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

gibtang

Source: github_repo_search

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

GitHub

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: TELEGRAM_REGISTRATION_BOT_TOKEN, TELEGRAM_BOT_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 11 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: B2_APPLICATION_KEY, CRON_SECRET, RESEND_API_KEY, TELEGRAM_BOT_TOKEN, TELEGRAM_REGISTRATION_BOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes8 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.

pair_connection
connection_status
create_agent

Creates a new agent. Names are unique per account. Owner-only: never exposed as an MCP tool.

rename_agent
handoff_create

Creates a handoff owned by the calling connection and returns its one-time view and submit tokens. The HTTP route applies connection rate limits.

handoff_decrypt

Returns plaintext values only to the creating connection. Uses POST /v1/handoffs/decrypt with handoffId in the body so the shared registry has a single JSON input schema.

handoff_close

Crypto-erases a handoff with the done reason. Owner revocation is intentionally owner-route-only and is never an MCP operation.

handoff_status

Any connection in the owning account may poll non-secret metadata. Uses POST /v1/handoffs/status with handoffId in the body; it never returns field values, tokens, or ciphertext metadata.

// known CVEs in dependencies2 critical11 high5 medium9 low

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

criticalnext@16.2.4GHSA-2xp9-vwfh-vxw4

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

criticalnext@16.2.4GHSA-p293-qw3h-jr36

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

highnext@16.2.4GHSA-267c-6grr-h53f

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

highnext@16.2.4GHSA-26hh-7cqf-hhc6

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

highnext@16.2.4GHSA-36qx-fr4f-26g5

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

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.
🔐 secretB2_APPLICATION_KEY
configB2_BUCKET_NAME
configB2_ENDPOINT
configB2_KEY_ID
🔐 secretCRON_SECRET
configFIREBASE_PROJECT_ID
🔐 secretRESEND_API_KEY
configRESEND_FROM_EMAIL
🔐 secretTELEGRAM_BOT_TOKEN
configTELEGRAM_CHAT_ID
🔐 secretTELEGRAM_REGISTRATION_BOT_TOKEN
configTELEGRAM_REGISTRATION_CHAT_ID
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployMONGODB_URI
deployNEXT_PUBLIC_APP_URL
deployNEXT_PUBLIC_BASE_URL
deployNEXT_PUBLIC_FIREBASE_API_KEY
deployNEXT_PUBLIC_FIREBASE_APP_ID
deployNEXT_PUBLIC_FIREBASE_AUTH_DOMAIN
deployNEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID
deployNEXT_PUBLIC_FIREBASE_PROJECT_ID
deployNEXT_PUBLIC_FIREBASE_STORAGE_BUCKET
deployNEXT_PUBLIC_GA_MEASUREMENT_ID
// quality suggestions

Dependencies

22 runtime dependencies (17 dev), 3 flagged: playwright, playwright-extra, puppeteer-extra-plugin-stealth

All four hints declared on every tool

8/8 tools missing one or more hints — pair_connection (missing: openWorldHint); connection_status (missing: openWorldHint); create_agent (missing: openWorldHint), +5 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.

Production dependencies are patched

2 critical, 11 high severity in production deps — next@16.2.4 (critical), next@16.2.4 (critical)

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

Dependency freshness

2/22 production deps stale: playwright-extra@2023-03-01 (3.5y), puppeteer-extra-plugin-stealth@2023-04-11 (3.4y)

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 2 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/gibtang/agent-utils?variant=verified)](https://m8ven.ai/mcp/gibtang/agent-utils)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0b5678e4ffe38da081400206c1e5e84e5381ce1f
code hash: f51c0c5e084594c15e11ade7af58be7920a0cb90d3e03c1aeb7980b189b2ec16
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