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.
npx agentmods add mcp/assafkip/kipi-system/apifygit clone --depth 1 https://github.com/assafkip/kipi-systemWrote 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/assafkip/kipi-system/apify)<a href="https://agentmods.dev/mcp/assafkip/kipi-system/apify"><img src="https://agentmods.dev/badge/mcp/assafkip/kipi-system/apify.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
apify 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 6d 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
{
"apify": {
"command": "npx",
"args": [
"-y",
"@apify/[email protected]"
],
"env": {
"APIFY_TOKEN": "${APIFY_TOKEN}",
"TOOLS": "actors,curious_coder/twitter-scraper"
}
}
}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.
- 6d ago First seen · 13 lines scan A 5ca51b081fb4
apify is an MCP server published in the GitHub repository assafkip/kipi-system (109 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-30.
Other mcp servers, from other repositories
vulcanus
A validated Markdown memory vault your coding agent can recall, project by project. Runs locally from the @sunsato/vulcanus npm package.
scraps
MCP server "scraps", hosted remotely, as configured in boykush/scraps.
universal-memory
MCP server "universal-memory", hosted remotely at localhost, as configured in goldenwo/universal-memory.
amenbo
Japanese-web-native MCP server for low-impact, token-efficient web collection. Runs locally from the amenbo npm package.
mcp-memory-suite
MCP server "mcp-memory-suite" as configured in sscctv/mcp-memory-suite. Runs locally from the mcp-memory-suite Python package.
scout
MCP server "scout" as configured in tools-for-agents/scout. Runs locally from the @tools-for-agents/scout npm package.