# io.tooltrace/mcp-server (remote · mcp.tooltrace.io)

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

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.tooltrace.io`: 83/100 (this document), [markdown](https://verifymcp.io/servers/io-tooltrace-mcp-server/mcp.md), [page](https://verifymcp.io/servers/io-tooltrace-mcp-server/mcp)
- npm · `@tooltrace/mcp-server`: 77/100, [markdown](https://verifymcp.io/servers/io-tooltrace-mcp-server/tooltrace-mcp-server.md), [page](https://verifymcp.io/servers/io-tooltrace-mcp-server/tooltrace-mcp-server)

## Channel facts

- Endpoint: `https://mcp.tooltrace.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 954 tokens (~136/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.tooltrace/mcp-server server?

io.tooltrace/mcp-server is a hosted endpoint at https://mcp.tooltrace.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-tooltrace-mcp-server 'https://mcp.tooltrace.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.io-tooltrace-mcp-server]
url = "https://mcp.tooltrace.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-tooltrace-mcp-server": {
      "type": "remote",
      "url": "https://mcp.tooltrace.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-tooltrace-mcp-server --url 'https://mcp.tooltrace.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-tooltrace-mcp-server:
    url: "https://mcp.tooltrace.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-tooltrace-mcp-server": {
      "Transport": "http",
      "Url": "https://mcp.tooltrace.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-tooltrace-mcp-server -t streamable-http -u 'https://mcp.tooltrace.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-tooltrace-mcp-server": {
      "type": "http",
      "url": "https://mcp.tooltrace.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 78, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 77)

First indexed and scored.

## MCP tools (7)

### `tooltrace_extract` (~174 tokens)

Extract webpage content

Extract clean content from a webpage. Returns Markdown, plain text, metadata, links, JSON-LD schema, and content sections. Use this for scraping, RAG ingestion, or content analysis.

Input parameters:

- `include` (array): Which fields to include in the response.
- `mode` (string): 'structured' for parsed data, 'raw' for HTML, 'both' for everything.
- `render` (string): Rendering mode. 'never' = fast static fetch (1 credit). 'auto' = static first, browser if needed. 'always' = browser rendering (5 credits).
- `url` (string, required): Public webpage URL to extract
- `wait_for_selector` (string): CSS selector to wait for on rendered pages.
- `wait_until` (string): Browser navigation milestone. Only used with browser rendering.

Output parameters:

- `content_hash` (string)
- `fetch` (object)
- `links` (array)
- `markdown` (string)
- `metadata` (object)
- `mode` (string)
- `raw_html` (string)
- `schema` (array)
- `sections` (array)
- `text` (string)
- `word_count` (integer)

### `tooltrace_metadata` (~126 tokens)

Read page metadata

Extract page metadata: title, description, canonical URL, author, publication date, favicon, Open Graph, and Twitter card fields. Lightweight alternative to full extraction.

Input parameters:

- `render` (string): Rendering mode. 'never' = fast static fetch (1 credit). 'auto' = static first, browser if needed. 'always' = browser rendering (5 credits).
- `url` (string, required): Public webpage URL
- `wait_for_selector` (string): CSS selector to wait for on rendered pages.
- `wait_until` (string): Browser navigation milestone. Only used with browser rendering.

Output parameters:

- `fetch` (object)
- `metadata` (object)

### `tooltrace_links` (~135 tokens)

Extract page links

Extract all links from a webpage with anchor text, internal/external classification, and normalized URLs.

Input parameters:

- `mode` (string): 'normalized' deduplicates and cleans URLs. 'raw' preserves originals.
- `render` (string): Rendering mode. 'never' = fast static fetch (1 credit). 'auto' = static first, browser if needed. 'always' = browser rendering (5 credits).
- `url` (string, required): Public webpage URL
- `wait_for_selector` (string): CSS selector to wait for on rendered pages.
- `wait_until` (string): Browser navigation milestone. Only used with browser rendering.

Output parameters:

- `count` (integer)
- `fetch` (object)
- `links` (array)
- `mode` (string)

### `tooltrace_schema` (~146 tokens)

Extract JSON-LD structured data

Extract JSON-LD structured data from a webpage. Returns schema.org entities like Article, Product, Organization, FAQ, BreadcrumbList, etc.

Input parameters:

- `mode` (string): 'normalized' deduplicates entities. 'raw' preserves original JSON-LD blocks.
- `render` (string): Rendering mode. 'never' = fast static fetch (1 credit). 'auto' = static first, browser if needed. 'always' = browser rendering (5 credits).
- `url` (string, required): Public webpage URL
- `wait_for_selector` (string): CSS selector to wait for on rendered pages.
- `wait_until` (string): Browser navigation milestone. Only used with browser rendering.

Output parameters:

- `count` (integer)
- `fetch` (object)
- `mode` (string)
- `schema` (array)

### `tooltrace_seo_audit` (~144 tokens)

Audit on-page SEO

Run an SEO audit on a webpage. Returns a score (0-100), weighted checks for metadata, headings, images, canonical signals, robots directives, social tags, schema, and content length, with evidence and recommendations.

Input parameters:

- `render` (string): Rendering mode. 'never' = fast static fetch (1 credit). 'auto' = static first, browser if needed. 'always' = browser rendering (5 credits).
- `url` (string, required): Public webpage URL to audit
- `wait_for_selector` (string): CSS selector to wait for on rendered pages.
- `wait_until` (string): Browser navigation milestone. Only used with browser rendering.

Output parameters:

- `checks` (array)
- `fetch` (object)
- `metadata` (object)
- `score` (integer)

### `tooltrace_tech_stack` (~136 tokens)

Detect the tech stack behind a site

Detect the technology stack of a website: CMS, frameworks, JavaScript libraries, analytics, CDN, hosting, fonts, security tools, and more. Returns categorized detections with confidence levels.

Input parameters:

- `render` (string): Rendering mode. 'never' = fast static fetch (1 credit). 'auto' = static first, browser if needed. 'always' = browser rendering (5 credits).
- `url` (string, required): Public webpage URL to analyze
- `wait_for_selector` (string): CSS selector to wait for on rendered pages.
- `wait_until` (string): Browser navigation milestone. Only used with browser rendering.

Output parameters:

- `categories` (object)
- `domain` (string)
- `fetch` (object)
- `technologies_detected` (integer)
- `url` (string)

### `tooltrace_sitemap` (~93 tokens)

Check an XML sitemap

Inspect a website's sitemap. Discovers sitemap URLs, parses sitemap XML, and returns listed page URLs with last-modified dates and change frequencies.

Input parameters:

- `render` (string): Rendering mode. 'never' = fast static fetch (1 credit). 'auto' = static first, browser if needed. 'always' = browser rendering (5 credits).
- `url` (string, required): Website URL or direct sitemap URL

Output parameters:

- `discovered_urls` (integer)
- `discovery_method` (string)
- `documents` (array)
- `findings` (array)
- `inspected_urls` (integer)
- `inspection_complete` (boolean)
- `limit_reason` (string)
- `requested_url` (string)
- `summary` (object)
- `urls` (array)
- `urls_included` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-tooltrace-mcp-server/mcp#diagnostics

## Score history

- 2026-09-21: 83
- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77

## Common questions

### What is the io.tooltrace/mcp-server server?

io.tooltrace/mcp-server is listed in the public MCP registry as io.tooltrace/mcp-server. Web tools for AI agents: scrape pages to Markdown, audit SEO, detect tech stacks, check sitemaps. This page covers its hosted endpoint (https://mcp.tooltrace.io/mcp).

### Is the io.tooltrace/mcp-server server safe to use?

io.tooltrace/mcp-server scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.tooltrace/mcp-server server expose?

io.tooltrace/mcp-server exposes 7 tools: tooltrace_extract, tooltrace_metadata, tooltrace_links, tooltrace_schema, tooltrace_seo_audit, and 2 more. Their descriptions and schemas cost roughly 954 tokens of context every time the server is loaded.

### Does the io.tooltrace/mcp-server server require authentication?

Yes. io.tooltrace/mcp-server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.tooltrace/mcp-server server still maintained?

io.tooltrace/mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.tooltrace.io/mcp
- Authorisation metadata: https://mcp.tooltrace.io/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/ToolTrace-io/mcp-server
- Website: https://tooltrace.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-tooltrace-mcp-server/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-tooltrace-mcp-server/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-tooltrace-mcp-server/mcp