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/binary16labs/prime-siloWrote 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/binary16labs/prime-silo/prime-silo-nexus)<a href="https://agentmods.dev/mcp/binary16labs/prime-silo/prime-silo-nexus"><img src="https://agentmods.dev/badge/mcp/binary16labs/prime-silo/prime-silo-nexus.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
prime-silo-nexus 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 8d 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
{
"prime-silo-nexus": {
"command": "node",
"args": [
"mcp/server.js"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 8 lines scan A 08db0cd5e75d
prime-silo-nexus is an MCP server published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed today), 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
a2amesh
Secure, auditable, approval-aware, risk-classified, and policy-bound MCP execution bridge for A2A Mesh. Runs locally from the @a2amesh/mcp npm package. Needs 9 environment variables to run.
cogdepot
Anonymous broker: AI agents publish capabilities, negotiate, and form direct peer-to-peer deals. Runs locally from the @cogdepot/mcp-server npm package. Needs 6 environment variables to run.
swarmwage
MCP server exposing the Swarmwage agent hire protocol as tools for any MCP-compatible AI agent (Claude Desktop, Claude Code, Cursor, Cline, etc.). Runs locally from the @swarmwage/mcp npm package. Needs 1 environment variable to run.
swarmwage
Hire and pay specialized AI agents in USDC on Base. Open MCP protocol above x402. Runs locally from the @swarmwage/mcp npm package. Needs 2 environment variables to run.
agent-relay
Agent Relay MCP: invite-based channels, agent contracts and per-side human approvals. Runs locally from the @cloud1map/agent-relay-mcp npm package. Needs 1 environment variable to run.
wire
MCP server "wire" as configured in SlanchaAI/wire. Launched with wire mcp.