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/pablo-albaladejo/kaiordWrote 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/pablo-albaladejo/kaiord/context7)<a href="https://agentmods.dev/mcp/pablo-albaladejo/kaiord/context7"><img src="https://agentmods.dev/badge/mcp/pablo-albaladejo/kaiord/context7/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/pablo-albaladejo/kaiord/context7"><img src="https://agentmods.dev/badge/mcp/pablo-albaladejo/kaiord/context7.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context7 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.
This is a copy
80% identical to context7 — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"context7": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@upstash/context7-mcp@latest"
],
"env": {}
}
}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.
- 1mo ago First seen · 11 lines scan A af2c66614240
context7 is an MCP server published in the GitHub repository pablo-albaladejo/kaiord (9 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. It is 80% identical to context7, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
hevy-coach
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
webcomponents-react-mcp-server
MCP server for UI5 Web Components for React - Developer documentation and API assistance. Runs locally from the @ui5/webcomponents-react-mcp npm package.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
oss-autopilot
Open source contribution manager with PR tracking, issue discovery, and CI diagnosis. Runs locally from the @oss-autopilot/mcp npm package. Needs 1 environment variable to run.
oss-autopilot
MCP server for OSS Autopilot — exposes PR tracking, issue discovery, and contribution management as MCP tools. Runs locally from the @oss-autopilot/mcp npm package.
forest-grove
MCP server "forest-grove" as configured in brendadeeznuts1111/betting-brain-v3. Launched with bun run scripts/mcp-server.ts. Needs 2 environment variables to run.