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.
npx agentmods add mcp/codyz123/schelling-protocol/mcp-server-schelling-protocolgit clone --depth 1 https://github.com/codyz123/schelling-protocolWrote 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/codyz123/schelling-protocol/mcp-server-schelling-protocol)<a href="https://agentmods.dev/mcp/codyz123/schelling-protocol/mcp-server-schelling-protocol"><img src="https://agentmods.dev/badge/mcp/codyz123/schelling-protocol/mcp-server-schelling-protocol.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
schelling-protocol 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 5d 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
{
"schelling-protocol": {
"command": "npx",
"args": [
"-y",
"@schelling/mcp-server"
],
"env": {}
}
}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.
- 5d ago First seen · 10 lines scan A f2adfc419a04
schelling-protocol is an MCP server published in the GitHub repository codyz123/schelling-protocol (4 stars, last pushed 5mo 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
semahash
Content-addressed semantics for multi-agent coordination. When the hash is the word. Runs locally from the semahash Python package.
dibs
MCP server "dibs" as configured in Agenxy/dibs. Launched with dibs mcp-stdio.
shift-mcp-server
Lightweight coordination layer for multiple AI agents working on the same codebase simultaneously. Runs locally from the @cyanheads/shift-mcp-server npm package. Needs 1 environment variable to run.
octopus-blackboard
Shared memory & coordination for AI coding agents — a blackboard, not an orchestrator. Runs locally from the octopus-blackboard npm package. Needs 2 environment variables to run.
agent-trust
Tamper-evident action receipts, trust scoring & capability tokens for AI agents. 29 MCP tools. Runs locally from the @garl-protocol/mcp-server npm package. Needs 3 environment variables to run.
dotrepo
MCP server "dotrepo" as configured in maxwellsantoro/dotrepo. Launched with https://github.com/maxwellsantoro/dotrepo/releases/download/v1.0.1/dotrepo-mcp-1.