Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MSApps-Mobile/claude-plugins/plugin install apify-scraperWrote 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/msapps-mobile/claude-plugins/apify-scraper-apify)<a href="https://agentmods.dev/mcp/msapps-mobile/claude-plugins/apify-scraper-apify"><img src="https://agentmods.dev/badge/mcp/msapps-mobile/claude-plugins/apify-scraper-apify/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/msapps-mobile/claude-plugins/apify-scraper-apify"><img src="https://agentmods.dev/badge/mcp/msapps-mobile/claude-plugins/apify-scraper-apify.svg" alt="Reviewed on agentmods" width="80" 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 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.
What it actually says
{
"apify": {
"command": "npx",
"args": [
"tsx",
"${CLAUDE_PLUGIN_ROOT}/servers/apify/src/index.ts"
],
"env": {
"APIFY_API_TOKEN": "${APIFY_API_TOKEN}"
}
}
}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 · 12 lines scan A 4ac6da4abe13
apify is an MCP server published in the GitHub repository MSApps-Mobile/claude-plugins (10 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-31.
Other mcp servers, from other repositories
deskcert
Certify whether an AI agent is safe to operate your internal web application before production rollout. Author a YAML task suite against your own app, run it with Playwright, and gate CI/CD on a forbidden-action safety score. Runs locally from the deskcert-cli Python package.
playwright-browser
MCP server "playwright-browser" as configured in CSOAI-ORG/playwright-browser. Runs locally from the @meok-ai-labs/playwright-browser npm package.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
url-ai-mcp
Url Ai MCP server. Tools: parse url, shorten url data, check url safety. Built by MEOK AI Labs. Runs locally from the url-ai-mcp Python package.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.