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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
11 days ago

CommunityOverview

→ jakobengdahl/CommunityOverview· listed on github_code

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

jakobengdahl

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
✅
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: BRAVE_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, AUTH_PASSWORD, AUTH_BEARER_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.
🔐 secretBRAVE_API_KEY
configSCHEMA_FILE
configE2E_SERVER_URL
configAGENTS_ENABLED
configLLM_PROVIDER
configLLM_MODEL
configOPENAI_MODEL
🔐 secretOPENAI_API_KEY
🔐 secretANTHROPIC_API_KEY
configMCP_INTEGRATIONS
configAGENTS_MAX_TURNS
configAGENTS_EVENT_TIMEOUT
configAGENTS_RUN_HISTORY_DB
configAGENTS_GOVERNANCE_DB
configGRAPH_FILE
configEMBEDDINGS_FILE
configSESSIONS_DIR
configHOST
configAPI_PREFIX
configWEB_STATIC_PATH
configWIDGET_STATIC_PATH
configMCP_NAME
configAUTH_ENABLEDEnable Basic Auth on all endpoints (except /health, /info)
configAUTH_USERNAMEUsername for Basic Auth
🔐 secretAUTH_PASSWORDPassword for Basic Auth (required for either mode to activate)
🔐 secretAUTH_BEARER_TOKEN
configCORS_ALLOWED_ORIGINS
configMCP_BASIC_AUTHEnable Basic Auth only on /mcp/ and /execute_tool
configTRUSTED_PROXY_HOPS
configMCP_AUTH_ENABLED
configCONFIG_PROFILE
configLOG_FORMAT
configSECRET_STORE_HEALTH_CHECK_SECRET_ID
configLOGOUT_REDIRECT_URL
configCOMMUNITYOVERVIEW_RUNTIME_MODE
configCOMMUNITYOVERVIEW_ENABLED_EXTENSIONS
configCOMMUNITYOVERVIEW_TENANT_ID
configCOMMUNITYOVERVIEW_TENANT_NAME
configCOMMUNITYOVERVIEW_ENVIRONMENT
configOPENAI_BASE_URL
configOPENAI_TOOL_CALLING
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

59/59 tools missing one or more hints — search_graph (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_node_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_related_nodes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +56 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.

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 Score](https://m8ven.ai/badge/mcp/jakobengdahl/communityoverview)](https://m8ven.ai/mcp/jakobengdahl/communityoverview)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b883e23eecef8ee9a008d23514e1cd5f544c30e0
code hash: 3634a9e61a77787b61a208c768d60090caf4997bfb3996740a5852bf2f767a7a
verified: 9/2/2026, 6:48:35 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