Back to MCP Trust Indexm8ven
C
Emerging
74/100
8 days ago

codeintel

A unified code-intelligence gateway MCP server that gives coding agents a single safe API to search, trace, and understand any codebase using graph, LSP, and semantic engines, with a local-first privacy model and a safe-null contract.

→ hamilton-sky/codeintel· listed on glama

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

hamilton-sky

Source: Glama

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

Glama

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 1 credential: CODEINTEL_HTTP_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.
🔐 secretCODEINTEL_HTTP_TOKENBearer token required by serve-http (equivalent to --token)
configCODEINTEL_HTTP_ACCESS_LOG1 One log line per HTTP request (method, path, status, latency)
configCODEINTEL_ALLOW_NO_AUTH
configCODEINTEL_AUTH_CONFIGPath to an RBAC token→role config (default ~/.codeintel/auth.toml) — per-token roles + op scopes
configCODEINTEL_LOG_LEVELDEBUG\INFO\WARNING(default)\ERROR for the server logger
configCODEINTEL_LOG_FORMATjson Structured (JSON-per-line) logs for ELK / Splunk / Datadog
configCODEINTEL_DEBUG1 Log the full traceback of any error the never-throw contract swallows (silent by default) — the switch for diagnosing an unexpected null
configCODEINTEL_REINDEXoff Disable the background reindexer; queries then index inline to stay fresh
configTERM
configFORCE_COLOR
// 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

4/4 tools missing one or more hints — _code_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); _code_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); _code_doctor (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 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

3/4 tools referenced in tests (75%)

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/hamilton-sky-codeintel-vwcjr3)](https://m8ven.ai/mcp/hamilton-sky-codeintel-vwcjr3)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2b2548c2bf3f1f8da7c18df58817f2589dee45c5
code hash: 11fd7c565a0eb32b32272b5a305536078aac39379da3d8b86a1d59ddbd8ca74a
verified: 8/13/2026, 8:12:57 AM
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