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/shibley/aisotools-mcp-serverWrote 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/shibley/aisotools-mcp-server/aisotools)<a href="https://agentmods.dev/mcp/shibley/aisotools-mcp-server/aisotools"><img src="https://agentmods.dev/badge/mcp/shibley/aisotools-mcp-server/aisotools/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/shibley/aisotools-mcp-server/aisotools"><img src="https://agentmods.dev/badge/mcp/shibley/aisotools-mcp-server/aisotools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
aisotools 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 8d 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
{
"aisotools": {
"url": "https://aisotools.com/api/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.
- 8d ago First seen · 6 lines scan A fc205f4c33d0
aisotools is an MCP server published in the GitHub repository shibley/aisotools-mcp-server (3 stars, last pushed today), 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
hmem-mcp
Persistent 5-level hierarchical memory for AI agents. SQLite-backed, lazy-loaded. Runs locally from the hmem-mcp npm package. Needs 1 environment variable to run.
weather-intel-mcp
US weather, alerts, earthquakes and elevation for AI agents, from NWS/NOAA and USGS. No API keys. Remote server at weather.datakoot.com.
mcp-searxng-local
MCP server "mcp-searxng-local" as configured in dduartee/mcp-searxng-local. Runs locally from the mcp-searxng-local npm package.
catalog
Search 2,000+ AI tools: pricing, alternatives, comparisons, and live, dead or acquired status. Remote server at tooldirectory.ai.
tg-mcp
Local MCP server for your Telegram personal account — channels, digests, messaging, folders and more. Runs locally from the tg-mcp npm package.
mcp-server-metasearch
A local MCP server aggregating web tools with API-key-gated dynamic exposure. Runs locally from the mcp-server-metasearch Python package.