Web tools for AI agents: scrape pages to Markdown, audit SEO, detect tech stacks, check sitemaps
MCPpedia last refreshed this data
io.tooltrace/mcp-server is an MCP server that web tools for AI agents: scrape pages to Markdown, audit SEO, detect tech stacks, check sitemaps. Its tool list has not been published yet over stdio and http, requires no API key, and scores 82/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"tooltrace": {
"env": {
"TOOLTRACE_API_KEY": "your-api-key"
},
"command": "tooltrace-mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Web tools for AI agents: scrape pages to Markdown, audit SEO, detect tech stacks, check sitemaps
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @tooltrace/mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml / writing
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
MCP Security Weekly
Get CVE alerts and security updates for io.tooltrace/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Give AI agents a complete web intelligence toolkit. This Model Context Protocol server connects Claude Code, Claude Desktop, Cursor, VS Code, Codex, Windsurf and any other MCP client to the ToolTrace API.
One tool per ToolTrace endpoint: scrape any page to clean Markdown, read metadata and JSON-LD, extract links, run on-page SEO audits, detect a site's tech stack, and check XML sitemaps. Free tier included, no card required.
Setup guide: tooltrace.io/mcp
| Tool | Description |
|---|---|
tooltrace_extract | Extract clean Markdown, text, metadata, links, JSON-LD, and sections from any webpage |
tooltrace_metadata | Get page title, description, canonical URL, Open Graph, and Twitter card fields |
tooltrace_links | Extract all internal and external links with anchor text |
tooltrace_schema | Extract JSON-LD structured data (Article, Product, FAQ, etc.) |
tooltrace_seo_audit | Run an SEO audit with scored checks and recommendations |
tooltrace_tech_stack | Detect CMS, frameworks, analytics, CDN, hosting, and more |
tooltrace_sitemap | Inspect and parse XML sitemaps |
Hosted, for clients that take a connector URL. Nothing to install or update:
https://mcp.tooltrace.io/mcp
claude mcp add --transport http tooltrace https://mcp.tooltrace.io/mcp \
--header "Authorization: Bearer your-api-key"
Also listed on Smithery.
Local, over stdio, for clients that run a process. Use this when your client does not speak HTTP, or when you would rather your API key never left your own machine. That is the quick start below.
Both expose the same tools and bill the same credits.
Sign up at tooltrace.io/signup. The free plan includes 1,000 credits per month.
npm install -g @tooltrace/mcp-server
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"tooltrace": {
"command": "tooltrace-mcp",
"env": {
"TOOLTRACE_API_KEY": "your-api-key"
}
}
}
}
Claude Code:
claude mcp add tooltrace tooltrace-mcp -e TOOLTRACE_API_KEY=your-api-key
Cursor (.cursor/mcp.json):
{
"mcpServers": {
"tooltrace": {
"command": "tooltrace-mcp",
"env": {
"TOOLTRACE_API_KEY": "your-api-key"
}
}
}
}
VS Code (.vscode/mcp.json):
{
"servers": {
"tooltrace": {
"command": "tooltrace-mcp",
"env": {
"TOOLTRACE_API_KEY": "your-api-key"
}
}
}
}
Codex (~/.codex/config.toml):
[mcp_servers.tooltrace]
command = "tooltrace-mcp"
env = { TOOLTRACE_API_KEY = "your-api-key" }
Windsurf (mcp_config.json):
{
"mcpServers": {
"tooltrace": {
"command": "tooltrace-mcp",
"env": {
"TOOLTRACE_API_KEY": "your-api-key"
}
}
}
}
Any other MCP client: run tooltrace-mcp over stdio and set the
TOOLTRACE_API_KEY environment variable. Full per-client setup guide at
tooltrace.io/mcp.
TOOLTRACE_API_KEY=your-api-key npx @tooltrace/mcp-server
Once connected, your AI agent can:
All tools support a render parameter:
never: Fast static fetch, 1 credit. Best for server-rendered pages.