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/neskuchny/sima_atlasWrote 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/neskuchny/sima_atlas/sima-atlas)<a href="https://agentmods.dev/mcp/neskuchny/sima_atlas/sima-atlas"><img src="https://agentmods.dev/badge/mcp/neskuchny/sima_atlas/sima-atlas/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/neskuchny/sima_atlas/sima-atlas"><img src="https://agentmods.dev/badge/mcp/neskuchny/sima_atlas/sima-atlas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sima-atlas 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 11d 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
{
"sima-atlas": {
"command": "node",
"args": [
"scripts/mcp_atlas_server.mjs"
]
}
}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.
- 11d ago First seen · 8 lines scan A 92651d71a13a
sima-atlas is an MCP server published in the GitHub repository neskuchny/sima_atlas (6 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
dos-kernel
Dispatch Operating System — the domain-free trust substrate for fleets of autonomous agents (verdict spine, ship oracle, structured refusal, lane arbiter, correlation spine). Runs locally from the dos-kernel Python package. Needs 1 environment variable to run.
work-buddy
MCP server "work-buddy", hosted remotely at localhost, as configured in KadenMc/work-buddy.
agent-bus
MCP server "agent-bus" as configured in MustaphaSteph/agent-bus-plugins. Launched with agent-bus-mcp.
deepwiki
Lets the agent read DeepWiki's AI-generated documentation of any public GitHub repository and ask questions about a codebase. Runs locally from the deepwiki-mcp npm package.
sequential-thinking
Adds a structured step-by-step reasoning tool the agent can call to break a problem into revisable thoughts. Runs locally from the @modelcontextprotocol/server-sequential-thinking npm package.
slack
Lets the agent read channels and post messages in a Slack workspace. Runs locally from the @modelcontextprotocol/server-slack npm package. Needs 2 environment variables to run.