MonkeyLLM (JimmyWesley/MonkeyLLM) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 38 tools. No publisher has claimed this listing.

C
Emerging
74/100

MonkeyLLM

Knowledge engine for AI agents: your documents become a git-versioned markdown knowledge graph the agent navigates over MCP. Curated summaries, typed edges, cited answers, SQL over your spreadsheets, no chunking. Same 12B local model: 0/11 on multi-hop questions as top-k RAG, 11/11 as a navigator. Python, Apache-2.0, self-hostable.

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

JimmyWesley

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 →

Install from

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
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 5 credentials: MONKEYLLM_STATION_PASSWORD, GITHUB_TOKEN, GH_TOKEN, MONKEYLLM_EMBED_API_KEY, MONKEYLLM_LLM_API_KEY
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.
configSTATION_URL
configMONKEYLLM_STATION_ADMIN
🔐 secretMONKEYLLM_STATION_PASSWORD
configMONKEYLLM_STATION_READERS
configMONKEYLLM_EMBED_ENDPOINT
🔐 secretGITHUB_TOKEN
🔐 secretGH_TOKEN
configMONKEYLLM_EMBED_MODEL
🔐 secretMONKEYLLM_EMBED_API_KEY
configMONKEYLLM_LLM_ENDPOINT
configMONKEYLLM_LLM_MODEL
🔐 secretMONKEYLLM_LLM_API_KEY
configMONKEYLLM_LLM_MAX_TOKENS
configMONKEYLLM_LLM_REASONING
configMONKEYLLM_S3_ENDPOINT
configMONKEYLLM_HARVEST_MAX_K
configMONKEYLLM_STATION_ROOT
configMONKEYLLM_STATION_REGISTRY
configMONKEYLLM_TRANSCRIBE_TIMEOUT
configMONKEYLLM_STATION_EXT_UPLOAD_MAX_MB
configMONKEYLLM_EXT_HOME
configMONKEYLLM_EXT_WORKER_TIMEOUT
// 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

38/38 tools missing one or more hints — forests (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); harvest (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); locate (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +35 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

21/38 tools referenced in tests (55%)

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

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 3 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/jimmywesley/monkeyllm)](https://m8ven.ai/mcp/jimmywesley/monkeyllm)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 07c50dfdf6df6ad880ff10c757e94bb2f9f1f43a
code hash: 7aae65998d6e6ade33c639c9f3b00976b97be124f2726eb5ad373d8cbb1d0da4
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