C
Emerging
74/100
5 days ago

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

OsamabinAdnan

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 →

Install from

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

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: OPENROUTER_API_KEY, LLM_MODEL_API_KEY, PROXY_API_KEY, REFRESH_TOKEN
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.
🔐 secretOPENROUTER_API_KEY
configLLM_MODEL
🔐 secretLLM_MODEL_API_KEY
configLLM_CHAT_COMPLETION_URL
configMCP_SERVER_URL
configHTTP_PROXY
configHTTPS_PROXY
configALL_PROXY
configNO_PROXY
configPROFILE_ARN"arn:aws:codewhisperer:us-east-1:..."
configKIRO_REGION"us-east-1"
configKIRO_API_REGION"eu-central-1" # or us-east-1
configSERVER_HOST
configSERVER_PORT
🔐 secretPROXY_API_KEY"my-super-secret-password-123"
configVPN_PROXY_URLsocks5://127.0.0.1:1080
🔐 secretREFRESH_TOKEN"your_kiro_refresh_token"
configKIRO_CREDS_FILE"~/.aws/sso/cache/kiro-auth-token.json"
configKIRO_CLI_DB_FILE"~/.local/share/kiro-cli/data.sqlite3"
configSQLITE_READONLY
configTOOL_DESCRIPTION_MAX_LENGTH
configTRUNCATION_RECOVERY
configLOG_LEVEL
configFIRST_TOKEN_TIMEOUT
configSTREAMING_READ_TIMEOUT
configFIRST_TOKEN_MAX_RETRIES
configFAKE_REASONING
configFAKE_REASONING_MAX_TOKENS
configFAKE_REASONING_BUDGET_CAP
configFAKE_REASONING_HANDLING
configFAKE_REASONING_INITIAL_BUFFER_SIZE
configKIRO_MAX_PAYLOAD_BYTES
configAUTO_TRIM_PAYLOAD
configWEB_SEARCH_ENABLED
configACCOUNT_SYSTEM
configACCOUNTS_CONFIG_FILE
configACCOUNTS_STATE_FILE
configACCOUNT_RECOVERY_TIMEOUT
configACCOUNT_MAX_BACKOFF_MULTIPLIER
configACCOUNT_PROBABILISTIC_RETRY_CHANCE
configACCOUNT_CACHE_TTL
configSTATE_SAVE_INTERVAL_SECONDS
// 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

11/11 tools missing one or more hints — get_forecast (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); server_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); hello (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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 test coverage

Only 2/11 tools referenced in tests (18%)

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

Secrets not logged

3 secret values sent to console.log

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 4 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 Score](https://m8ven.ai/badge/mcp/osamabinadnan-quarter05-learning-alhkb9)](https://m8ven.ai/mcp/osamabinadnan-quarter05-learning-alhkb9)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 68b16ea5b38518650be38d5b7bb91c4eb2ba8abe
code hash: e2f8494089bce088bb3ed25f59b4b8fbd9b536fd9ad62dc1658df344f40bb701
verified: 8/16/2026, 6:53:22 PM
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