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/emergent-wisdom/sema/semahashgit clone --depth 1 https://github.com/emergent-wisdom/semaWrote 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/emergent-wisdom/sema/semahash)<a href="https://agentmods.dev/mcp/emergent-wisdom/sema/semahash"><img src="https://agentmods.dev/badge/mcp/emergent-wisdom/sema/semahash.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
semahash 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
{
"semahash": {
"command": "uvx",
"args": [
"semahash",
"--from",
"semahash",
"sema"
],
"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 · 12 lines scan A 6832bb0d1b21
semahash is an MCP server published in the GitHub repository emergent-wisdom/sema (13 stars, last pushed 4d 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-30.
Other mcp servers, from other repositories
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.
buzz-mcp
MCP server "buzz-mcp" as configured in CedricConday/buzz-mcp. Runs locally from the buzz-mcp Python package.
j5ed-knowledge-graph
A knowledge graph memory server for MCP with multi-agent tenant isolation, tiered search, index navigation, and three transport modes. Runs locally from the j5ed-knowledge-graph npm package.
mcp
Persistent memory for AI agents, governed by the human and stored on their own machine. Runs locally from the @mnemosyne_os/mcp npm package. Needs 2 environment variables to run.