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/scrapegraphai/scrapegraph-mcp/scrapegraphai-scrapegraph-mcpgit clone --depth 1 https://github.com/ScrapeGraphAI/scrapegraph-mcpWrote 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/scrapegraphai/scrapegraph-mcp/scrapegraphai-scrapegraph-mcp)<a href="https://agentmods.dev/mcp/scrapegraphai/scrapegraph-mcp/scrapegraphai-scrapegraph-mcp"><img src="https://agentmods.dev/badge/mcp/scrapegraphai/scrapegraph-mcp/scrapegraphai-scrapegraph-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ScrapeGraphAI-scrapegraph-mcp 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
{
"ScrapeGraphAI-scrapegraph-mcp": {
"url": "https://server.smithery.ai/@ScrapeGraphAI/scrapegraph-mcp/mcp",
"type": "streamable-http"
}
}What else server.json configures
This page is one entry in a file that holds 2. 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 · 6 lines scan A b77f25208dc1
ScrapeGraphAI-scrapegraph-mcp is an MCP server published in the GitHub repository ScrapeGraphAI/scrapegraph-mcp (102 stars, last pushed 1mo ago), 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
web-access
The most accurate web access API. Stop getting blocked. Runs locally from the @usestring/mcp npm package. Needs 1 environment variable to run.
Scrapling
Scrapling is an undetectable, powerful, flexible, high-performance Python library that makes Web Scraping easy and effortless as it should be! Runs locally from the scrapling Python package.
chrome-devtools-mcp
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
stdio-full
MCP server "stdio-full" as configured in apify/apify-mcp-server. Runs dist/stdio.js with node. Needs 2 environment variables to run.
apify-mcp-server
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡. Remote server at mcp.apify.com.
computer-use-mcp
Control your computer with screenshots, mouse, and keyboard automation. Runs locally from the computer-use-mcp npm package.