ToolTrace MCP MCP server

An official MCP server by ToolTrace that provides AI agents with a comprehensive toolkit for web intelligence. It enables agents to scrape web pages into clean Markdown, extract metadata and structured data (JSON-LD), perform on-page SEO audits, detect technology stacks, and validate XML sitemaps. The server returns structured JSON with fetch evidence, allowing agents to cite specific sources and URLs, ensuring accurate and verifiable web research capabilities.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by ToolTrace

MCP endpoint (Streamable HTTP)

https://mcp.tooltrace.io/mcp

Vendor documentation

What you can do with it

Scrape web pages into clean Markdown for content analysis
Run on-page SEO audits with severity checks and recommendations
Detect the CMS, frameworks, and hosting technologies of a site
Validate XML sitemaps and check URL indexability

Tools advertised by the last live check:

tooltrace_extract
tooltrace_metadata
tooltrace_links
tooltrace_schema
tooltrace_seo_audit
tooltrace_tech_stack
tooltrace_sitemap

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http tooltrace-mcp https://mcp.tooltrace.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add tooltrace-mcp --url https://mcp.tooltrace.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tooltrace-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "tooltrace-mcp": {
      "url": "https://mcp.tooltrace.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "tooltrace-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.tooltrace.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tooltrace-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "tooltrace-mcp": {
      "type": "http",
      "url": "https://mcp.tooltrace.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http tooltrace-mcp https://mcp.tooltrace.io/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "tooltrace-mcp": {
      "url": "https://mcp.tooltrace.io/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "tooltrace-mcp": {
      "serverUrl": "https://mcp.tooltrace.io/mcp"
    }
  }
}

See all 957

Do you run ToolTrace MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing