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/philipyaz/cos/bodygit clone --depth 1 https://github.com/philipyaz/cosWrote 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/philipyaz/cos/body)<a href="https://agentmods.dev/mcp/philipyaz/cos/body"><img src="https://agentmods.dev/badge/mcp/philipyaz/cos/body.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
body 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 4d 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
{
"body": {
"type": "http",
"url": "http://localhost:8012/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 9. 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.
- 4d ago First seen · 6 lines scan A 3fdcf5d38509
body is an MCP server published in the GitHub repository philipyaz/cos (4 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
knowledge-inbox
MCP server "knowledge-inbox" as configured in lyc403223157-source/knowledge-inbox. Runs locally from the knowledge-inbox Python package.
laver-mcp
Kanban boards, sprints, tickets and a team wiki, with versioned writes for concurrent agents. Runs locally from the @laver/mcp npm package. Needs 3 environment variables to run.
obsidian
MCP server "obsidian" as configured in studentepercaso/obsidian-bridge. Runs ./dist/server.mjs with node.
big-brain
MCP server "big-brain" as configured in jzhao234/big-brain. Runs locally from the big-brain npm package.
mcp-mem
An MCP server implementing memory solution for data-rich applications. Runs locally from the mcp-mem Python package.
mcp-apple-obsidian
MCP server "mcp-apple-obsidian" as configured in rex/mcp-apple-obsidian. Runs locally from the mcp-apple-obsidian Python package.