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/infino-ai/infino-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/infino-ai/infino-mcp/infino)<a href="https://agentmods.dev/mcp/infino-ai/infino-mcp/infino"><img src="https://agentmods.dev/badge/mcp/infino-ai/infino-mcp/infino/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/infino-ai/infino-mcp/infino"><img src="https://agentmods.dev/badge/mcp/infino-ai/infino-mcp/infino.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
infino 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
{
"infino": {
"command": "npx",
"args": [
"-y",
"@infino-ai/mcp-server"
],
"env": {
"INFINO_MCP_URI": "${user_config.infino_uri}",
"INFINO_API_KEY": "${user_config.infino_api_key}"
}
}
}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 Changed · -1 lines be027d251a01
- 12d ago First seen · 14 lines scan A a7442ee33b27
infino is an MCP server published in the GitHub repository infino-ai/infino-mcp (0 stars, last pushed yesterday), 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
corpus-rag
Single-user RAG framework for personal archives. Local-first, MCP-native. Runs locally from the corpus-rag Python package.
shelfmark-rag
Local hybrid retrieval (BM25 + embeddings + RRF) for agent memory and codebases — one SQLite file, MCP server included. Runs locally from the shelfmark-rag Python package.
mcp-local-rag
Easy-to-setup local RAG server with minimal configuration. Runs locally from the mcp-local-rag npm package. Needs 8 environment variables to run.
inspeximus
MCP server "inspeximus" as configured in DanceNitra/inspeximus. Runs locally from the inspeximus[mcp] Python package. Needs 1 environment variable to run.
re-call
Trustworthy retrieval for an AI agent's own memory — verdict, confidence and provenance per hit, or an explicit abstention. Runs locally from the recall-rag Python package. Needs 3 environment variables to run.
ragmap
DEPRECATED: hosted backend discontinued; npm package deprecated. Formerly a retriever-MCP finder. Runs locally from the @khalidsaidi/ragmap-mcp npm package.