Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/MatiasPujado/Project_LensWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/matiaspujado/project_lens/project-lens)<a href="https://agentmods.dev/mcp/matiaspujado/project_lens/project-lens"><img src="https://agentmods.dev/badge/mcp/matiaspujado/project_lens/project-lens/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/matiaspujado/project_lens/project-lens"><img src="https://agentmods.dev/badge/mcp/matiaspujado/project_lens/project-lens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
project-lens scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "project-lens": { "command": "npx", "args": [ "-y", "@mpujado/project-lens" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 9 lines scan A 29a7104108c9
project-lens is an MCP server published in the GitHub repository MatiasPujado/Project_Lens (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-redmine-rest
Model Context Protocol server that connects Claude, or any other MCP client, to a Redmine instance via its REST API. Runs locally from the mcp-redmine-rest Python package.
cas-genesis-world-mcp
MCP server for the CAS genesisWorld REST Webservice v7.0 — tools, flows, and resources with an optional read-only mode. Runs locally from the cas-genesis-world-mcp npm package.
kanban
MCP server "kanban" as configured in kanban-rs/kanban. Launched with nix run .#kanban-mcp -- kanban.json.
metamcp
Route long-tail MCP servers through three lazy tools and reviewed declarative Methods. Runs locally from the @mentu/metamcp npm package.
2009scape-wiki
MCP server "2009scape-wiki" as configured in arsalan-anwari/2009scape-wiki-api. Runs locally from the . Python package. Needs 1 environment variable to run.
saidsef-mcp-github-pr-issue-analyser
A Model Context Protocol (MCP) application for automated GitHub PR analysis and issue management.… Remote server at server.smithery.ai.