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/toolbeltai/toolbelt-skillsWrote 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/toolbeltai/toolbelt-skills/toolbelt)<a href="https://agentmods.dev/mcp/toolbeltai/toolbelt-skills/toolbelt"><img src="https://agentmods.dev/badge/mcp/toolbeltai/toolbelt-skills/toolbelt/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/toolbeltai/toolbelt-skills/toolbelt"><img src="https://agentmods.dev/badge/mcp/toolbeltai/toolbelt-skills/toolbelt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
toolbelt 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 12d 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
{
"toolbelt": {
"url": "https://mcp.toolbelt.ai/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.
- 12d ago First seen · 6 lines scan A f4914f773094
toolbelt is an MCP server published in the GitHub repository toolbeltai/toolbelt-skills (2 stars, last pushed 1mo 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
chromadb-remote-mcp
MCP server "chromadb-remote-mcp" as configured in meloncafe/chromadb-remote-mcp. Runs in Docker (devsaurus/chromadb-remote-mcp:latest). Needs 2 environment variables to run.
ethora-mcp-server
MCP server for the Ethora chat & messaging platform: chat ops, AI agents, RAG, automation. Runs locally from the @ethora/mcp-server npm package. Needs 5 environment variables to run.
bookmark-lens
Local-first MCP server for intelligent bookmark management with semantic search. Runs locally from the bookmark-lens Python package.
haiku-rag
Local-first agentic RAG with citations - hybrid search, reranking and multimodal retrieval over your own documents, no database server required. Runs locally from the haiku-rag Python package.
mcp-neo4j-knowledge-graph
Neo4j-based knowledge graph MCP server with temporal versioning and semantic search. Runs locally from the @henrychong-ai/mcp-neo4j-knowledge-graph npm package.
datris
MCP server for AI-driven data pipeline operations — ingest, validate, transform, analyze, and query data. Tools covering ETL, AI data quality, vector search, PostgreSQL, MongoDB, Snowflake, Databricks, Kafka, S3/MinIO, HashiCorp Vault, Qdrant, Weaviate, Milvus, Chroma, pgvector. Runs locally from the datris-mcp-server…