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/justinstimatze/gemotWrote 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/justinstimatze/gemot/gemot)<a href="https://agentmods.dev/mcp/justinstimatze/gemot/gemot"><img src="https://agentmods.dev/badge/mcp/justinstimatze/gemot/gemot/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/justinstimatze/gemot/gemot"><img src="https://agentmods.dev/badge/mcp/justinstimatze/gemot/gemot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gemot 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 1mo 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
{
"gemot": {
"url": "https://gemot.dev/mcp",
"type": "streamable-http"
}
}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.
- 1mo ago First seen · 6 lines scan A ad796d1914a5
gemot is an MCP server published in the GitHub repository justinstimatze/gemot (3 stars, last pushed 3d ago), licensed Apache-2.0. 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
coordinate_agents
MCP server "coordinateagents" as configured in hogancv/coordinate-agents. Runs ./mcp/server.mjs with node.
agent-mesh-core
MCP server "agent-mesh-core" as configured in jcbmrrs/agent-mesh-core. Runs locally from the agent-mesh-core Python package.
council
Multi-model consensus: 2-6 frontier LLMs answer, an independent judge synthesises one answer. Runs locally from the tokonomix-council-mcp npm package. Needs 1 environment variable to run.
llm-bus
Coordinate multiple AI agents over MCP: atomic claims, leases, shared ledger, handoffs, tasks. Remote server at mcp.llm-bus.com.
bus-mcp
Ergonomic MCP server fronting the self-hosted AlphaHive coordination-bus HTTP API (backend/coordinationbus.py) -- post/read/claim/release/heartbeat/status as MCP tools instead of hand-rolled curl. Fast-follow to the coordination-bus arc, github-mcp-shaped (MCP over an HTTP API). Runs locally from the bus-mcp Python…
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.