agno-repo (carloshhr/agno-repo) is an MCP server listed on the M8ven Trust Index. It scores 28 out of 100, grade F. It declares 16 tools. No publisher has claimed this listing.

Warning

28/100

agno-repo

Item: agno-repo
Rating: 28
Author: M8ven

Agno Main Repo, This will be used to run the cookbook

→ carloshhr/agno-repo · listed on github_code

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 push why connect →

Who stands behind it

carloshhr

Source: github_code

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

3 flows detected: OS_SECURITY_KEY. We can’t prove the destination matches the brand the credential belongs to.

🚨

Hardcoded credentials detected

2 live-looking API keys in source: 2 OpenAI API key

🔐

You'll be asked for 8 credentials: NOTION_TOKEN, OS_SECURITY_KEY, OXYLABS_PASSWORD, GEMINI_API_KEY, STRIPE_SECRET_KEY, SUPABASE_ACCESS_TOKEN, DISCORD_BOT_TOKEN, NEO4J_PASSWORD

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

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

configAGENTOS_MCP_URL

🔐 secretNOTION_TOKEN

configAGENTOS_URL

🔐 secretOS_SECURITY_KEY

configMCP_ALLOWED_HOSTS

configOXYLABS_USERNAME

🔐 secretOXYLABS_PASSWORD

🔐 secretGEMINI_API_KEY

configMCP_SERVER_URL

🔐 secretSTRIPE_SECRET_KEY

🔐 secretSUPABASE_ACCESS_TOKEN

🔐 secretDISCORD_BOT_TOKEN

configNEO4J_URI

configNEO4J_USERNAME

🔐 secretNEO4J_PASSWORD

// quality suggestions

Tool annotations

8/18 tools have annotations

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

All four hints declared on every tool

18/18 tools missing one or more hints — greet (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_weather (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_temperature (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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.

Tool inputs are validated

16/18 tool handlers declare input schemas (89%)

Declare an inputSchema with zod/joi/yup on every tool definition.

No hardcoded API keys

2 live-looking API keys in source: 2 OpenAI API key

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

12/18 tools referenced in tests (67%)

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

Secrets stay with their owner

3 secrets sent to a request target we could not resolve (OS_SECURITY_KEY → dynamic, OS_SECURITY_KEY → dynamic) — often a configured endpoint, not necessarily third-party

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

Secrets not logged

4 secret values sent to print

Redact or omit secret values from log output.

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

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

commit: 8de271c47bb6d1313215d78dd58928b13ecbc0b2

code hash: 3ffda2456061e3037d86e45b7cf95860ac39676653d92e6586e38e82531faa4a

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