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/PackmindHub/packmindWrote 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/packmindhub/packmind/michel-packmind-user-docs)<a href="https://agentmods.dev/mcp/packmindhub/packmind/michel-packmind-user-docs"><img src="https://agentmods.dev/badge/mcp/packmindhub/packmind/michel-packmind-user-docs.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
packmind-user-docs 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 4d 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
{
"packmind-user-docs": {
"type": "http",
"url": "https://docs.packmind.com/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 4d ago First seen · 6 lines scan A bb7be9852486
packmind-user-docs is an MCP server published in the GitHub repository PackmindHub/packmind (309 stars, last pushed today), 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-09-03.
Other mcp servers, from other repositories
ai-context-kit
Lint, measure, and sync AI context files across Cursor, Claude Code, Copilot. Runs locally from the ai-context-kit npm package.
kupu
MCP server "kupu" as configured in taniwhaai/arai. Launched with kupu.
Context7_authenticated
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
CloudflareDocumentation
MCP server "CloudflareDocumentation", hosted remotely at docs.mcp.cloudflare.com, as configured in spacehendrix/clauder.
AWSKnowledge
MCP server "AWSKnowledge", hosted remotely at knowledge-mcp.global.api.aws, as configured in spacehendrix/clauder.
repomemory
Your codebase never forgets. Persistent, structured memory for AI coding agents. Runs locally from the repomemory npm package.