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/SAIHM-Admin/saihm-mcpWrote 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/saihm-admin/saihm-mcp/saihm)<a href="https://agentmods.dev/mcp/saihm-admin/saihm-mcp/saihm"><img src="https://agentmods.dev/badge/mcp/saihm-admin/saihm-mcp/saihm/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/saihm-admin/saihm-mcp/saihm"><img src="https://agentmods.dev/badge/mcp/saihm-admin/saihm-mcp/saihm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
saihm 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
{
"saihm": {
"command": "npx",
"args": [
"-y",
"@saihm/mcp-server"
],
"env": {
"SAIHM_ENDPOINT_URL": "https://operator.example.com/mcp",
"SAIHM_AUTH_HEADER": "Bearer <token>"
}
}
}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 · 13 lines scan A 4bdd5768bd67
saihm is an MCP server published in the GitHub repository SAIHM-Admin/saihm-mcp (2 stars, last pushed 12d 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
prism-coder
Session memory for coding agents: local-first recall, drift detection, on-device inference. Runs locally from the prism-mcp-server npm package. Needs 8 environment variables to run.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
xmemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST. Runs locally from the @xmemo/client npm package. Needs 2 environment variables to run.
inspeximus
MCP server "inspeximus", hosted remotely at pypi.org, as configured in DanceNitra/inspeximus. Needs 1 environment variable to run.
gmem
Persistent, Solana-aware project memory for AI coding agents. Typed entities + git-aware diffs. Runs locally from the @yksanjo/gmem npm package. Needs 1 environment variable to run.
engrava
Model Context Protocol server for Engrava - expose an agent memory database to any MCP client over stdio. Runs locally from the engrava-mcp Python package. Needs 3 environment variables to run.