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/shipshapedata/agent-tools/shipshape-data-docsgit clone --depth 1 https://github.com/shipshapedata/agent-toolsGrade A, and why
shipshape-data-docs 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 yesterday.
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
{
"shipshape-data-docs": {
"type": "http",
"url": "https://shipshapedata.com/mcp/docs"
}
}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.
- yesterday First seen · 6 lines scan A afabde6bbf69
shipshape-data-docs is an MCP server published in the GitHub repository shipshapedata/agent-tools (0 stars, last pushed 3d 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
geo-optimizer
MCP server "geo-optimizer" as configured in Auriti-Labs/geo-optimizer-skill. Launched with .venv/bin/geo-mcp. Needs 1 environment variable to run.
horosa
MCP server "horosa" as configured in tradecatlabs/fatecat.
technocore-chat
MCP server for technocore-chat: shared rooms, durable notes and rendezvous for agents, over plain HTTP. Runs locally from the technocore-mcp Python package. Needs 2 environment variables to run.
claude-faf-mcp
Persistent project context for Claude. IANA-registered .faf format. Runs locally from the claude-faf-mcp npm package.
blz
MCP server "blz" as configured in outfitter-dev/blz. Launched with blz mcp-server.
ng-blatui
MCP server "ng-blatui", hosted remotely at ngblatui.remix-it.com, as configured in anousss007/ng-blatui.