F
Warning
18/100
9 days ago

Project-Lens

MCP server that scans workspace roots to build a registry of version-controlled projects, exposing tools for searching, listing, and inspecting projects to help AI coding agents navigate multi-repo workspaces efficiently.

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 pushwhy connect →

Who stands behind it

MatiasPujado

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 →

Install from

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

// key findings
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
🔐
You'll be asked for 3 credentials: ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, CLAUDE_CODE_OAUTH_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.
🔐 secretANTHROPIC_API_KEY
🔐 secretANTHROPIC_AUTH_TOKEN
configANTHROPIC_BASE_URL
🔐 secretCLAUDE_CODE_OAUTH_TOKEN
configLENS_BENCH_COUNTER
configLENS_BENCH_MODEL
configLENS_BENCH_PROJECT"<group>/<Project>" npm run bench
configPROJECTS_MCP_CONFIG
configPROJECT_LENS_PATHexport ="$HOME/Projects"
// 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 — map_workspace (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_groups (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_projects (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.

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

3 child_process/subprocess calls in production code — runs shell commands (benchmark/tokens.ts:16, src/search.ts:32, src/search.ts:180)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Readable source code

1 file appear obfuscated

Ship unminified, readable source.

Domain consistency

npm scope @mpujado doesn't match GitHub owner matiaspujado

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 6 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/matiaspujado-project-lens-1t6ae7?variant=verified)](https://m8ven.ai/mcp/matiaspujado-project-lens-1t6ae7)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3c408ead09f6dcb84e75c42be6e893dbdb53f05f
code hash: 8d9edfd02470aeb2db46ba7e799baf22d9312d733a5f8801822d82c5555a4b25
verified: 8/10/2026, 8:07:40 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