npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@tooltrace/mcp-server

v0.1.2

Published

Web tools for AI agents: scrape pages to Markdown, audit SEO, detect tech stacks, check sitemaps

Readme

ToolTrace MCP Server

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

Tools

| 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 |

Quick start

1. Get a free API key

Sign up at tooltrace.io/signup. The free plan includes 1,000 credits per month.

2. Install

npm install -g @tooltrace/mcp-server

3. Configure your MCP client

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.

Run with npx (no install)

TOOLTRACE_API_KEY=your-api-key npx @tooltrace/mcp-server

Usage examples

Once connected, your AI agent can:

  • "Extract the main content from this blog post as Markdown"
  • "What technologies does competitor.com use?"
  • "Run an SEO audit on our landing page"
  • "Get all the links from this documentation page"
  • "Extract the JSON-LD schema from this product page"
  • "Check the sitemap for this website"

Rendering modes

All tools support a render parameter:

  • never: Fast static fetch, 1 credit. Best for server-rendered pages.
  • auto (default): Starts static, renders in browser if needed. 1 or 5 credits.
  • always: Full browser rendering, 5 credits. For JavaScript-heavy SPAs.

Development

git clone https://github.com/ToolTrace-io/mcp-server.git
cd mcp-server
npm install
npm run build
TOOLTRACE_API_KEY=your-key node dist/index.js

License

MIT