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/paulogarciarego/switchboardWrote 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/paulogarciarego/switchboard/claude-switchboard)<a href="https://agentmods.dev/mcp/paulogarciarego/switchboard/claude-switchboard"><img src="https://agentmods.dev/badge/mcp/paulogarciarego/switchboard/claude-switchboard.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
claude-switchboard 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 7d 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
{ "claude-switchboard": { "command": "npx", "args": [ "-y", "claude-switchboard" ] } }
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.
- 7d ago First seen · 9 lines scan A b0a239302326
claude-switchboard is an MCP server published in the GitHub repository paulogarciarego/switchboard (0 stars, last pushed 2mo 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
xyne-genius-rca
MCP server "xyne-genius-rca", hosted remotely at grafana.spaces.xyne.juspay.net, as configured in juspay/xyne-spaces.
session-collab
Provider-agnostic Model Context Protocol (MCP) collaboration server: claim files, persist working memory, and prevent multi-agent session conflicts. Runs locally from the session-collab-mcp npm package.
loomiomcp
Model Context Protocol server for Loomio. Lets Claude (Desktop, Code, or web Projects via Custom Connector) read and create Loomio discussions, polls, and comments, manage group memberships, and analyse member activity in plain English. Runs locally from the loomiomcp npm package.
swarm-rd-orchestrator
Ray-native context/memory sharing for parallel research agents, with an agent-native CLI and MCP server (Milestone 1 spike). Runs locally from the swarm-rd-orchestrator-cli Python package.
board-mcp
MCP server "board-mcp" as configured in maoxiangzhe/board-mcp. Runs locally from the board-mcp Python package.
derive
Publish agent output to permanent versioned URLs, read review comments back, and revise. Remote server at derive.to.