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/sanjibani/passare-mcpWrote 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/sanjibani/passare-mcp/passare_mcp)<a href="https://agentmods.dev/mcp/sanjibani/passare-mcp/passare_mcp"><img src="https://agentmods.dev/badge/mcp/sanjibani/passare-mcp/passare_mcp/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/sanjibani/passare-mcp/passare_mcp"><img src="https://agentmods.dev/badge/mcp/sanjibani/passare-mcp/passare_mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
passare_mcp 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
{ "passare_mcp": { "command": "uvx", "args": [ "passare_mcp" ] } }
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 · 8 lines scan A 0dca3859596f
passare_mcp is an MCP server published in the GitHub repository sanjibani/passare-mcp (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
cinc_systems_mcp
MCP server "cincsystemsmcp" as configured in sanjibani/cincsystems-mcp. Runs locally from the cinc_systems_mcp Python package.
kicksite_mcp
MCP server "kicksitemcp" as configured in sanjibani/kicksite-mcp. Runs locally from the kicksite_mcp Python package.
archstone
Compile your own business capabilities from declarative YAML and serve them as MCP tools. Runs locally from the @archstone/cli npm package.
volante
Volante — a transparent, user-owned model router and orchestration control plane. Runs locally from the volante Python package. Needs 85 environment variables to run.
volante
MCP server "volante" as configured in ribato22/volante. Runs locally from the volante[mcp] Python package.
playmetrics_mcp
MCP server "playmetricsmcp" as configured in sanjibani/playmetrics-mcp. Runs locally from the playmetrics_mcp Python package.