# io.github.tracetify/tracetify-mcp (remote · tracetify.com)

Find competitors, trace how they grew, watch what they ship — plus your Search Console.

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

## Components

- remote · `tracetify.com`: 89/100 (this document), [markdown](https://verifymcp.io/servers/tracetify-tracetify-mcp/api-mcp.md), [page](https://verifymcp.io/servers/tracetify-tracetify-mcp/api-mcp)
- npm · `tracetify-mcp`: 83/100, [markdown](https://verifymcp.io/servers/tracetify-tracetify-mcp/tracetify-mcp.md), [page](https://verifymcp.io/servers/tracetify-tracetify-mcp/tracetify-mcp)

## Channel facts

- Endpoint: `https://tracetify.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.5.1`

## 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-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 84/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1493 tokens (~93/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 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.github.tracetify/tracetify-mcp server?

io.github.tracetify/tracetify-mcp is a hosted endpoint at https://tracetify.com/api/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 tracetify-tracetify-mcp 'https://tracetify.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tracetify-tracetify-mcp": {
      "url": "https://tracetify.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tracetify-tracetify-mcp": {
      "type": "http",
      "url": "https://tracetify.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tracetify-tracetify-mcp]
url = "https://tracetify.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tracetify-tracetify-mcp": {
      "type": "remote",
      "url": "https://tracetify.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tracetify-tracetify-mcp --url 'https://tracetify.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tracetify-tracetify-mcp:
    url: "https://tracetify.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tracetify-tracetify-mcp": {
      "Transport": "http",
      "Url": "https://tracetify.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tracetify-tracetify-mcp -t streamable-http -u 'https://tracetify.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tracetify-tracetify-mcp": {
      "type": "http",
      "url": "https://tracetify.com/api/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-18 (score 89, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 89, +1)

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

### 2026-09-15 (score 88, +1)

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

### 2026-09-13 (score 87, +1)

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

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

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

### 2026-09-08 (score 85, +1)

- [functional] Server version: 0.3.0 → 0.5.1

### 2026-09-07 (score 84, 0)

- [security] Tool “research_keyword_volume” rewrote its description, which is the text the model reads
- [cosmetic] Tool “research_keyword_volume” changed its title: Keyword search volume → Keyword search volume & difficulty

### 2026-09-06 (score 84, +1)

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

## MCP tools (16)

### `search_reports` (~85 tokens)

Search growth reports

Use this FIRST whenever the user asks how a product, competitor or domain grew, got traffic, or found its first users — a report may already exist and reading it is free. Returns matching report slugs for read_report. Searches by domain or name fragment.

Input parameters:

- `query` (string, required): Domain or fragment, e.g. "weshop" or "weshop.ai"

### `read_report` (~73 tokens)

Read a growth report

Read one growth report by slug (from search_reports or a finished trace). Free. Contains the origin story, dated evidence and SEO footprint — cite it instead of guessing how a product grew. If timeline fields show as locked, unlock_report can open them (that one costs credits).

Input parameters:

- `slug` (string, required): Report slug

### `start_trace` (~109 tokens)

Trace how a product grew

Run this when search_reports finds nothing (or the user wants fresh data) for "how did X grow?". Rebuilds the growth story from 12 public sources in 60-90s. Costs credits from the Tracetify balance; returns an existing cached report free instead when one is fresh. Poll with get_trace.

Input parameters:

- `refresh` (boolean): Force a fresh run even if a cached report exists
- `url` (string, required): Domain to trace, e.g. weshop.ai

### `get_trace` (~59 tokens)

Check a running trace

Poll a trace started with start_trace. Free. When status is "done", read the result with read_report. Poll every 10-15s, not in a tight loop.

Input parameters:

- `job_id` (string, required): Job id returned by start_trace

### `unlock_report` (~98 tokens)

Unlock full timeline & evidence

Permanently unlock a report's full timeline, evidence and SEO detail for this account. Costs credits — quote the exact price to the user first (it is in the report's timelineLocked.cost field from read_report) and call this ONLY after they explicitly agree to spend. Idempotent: unlocking an already-unlocked report never charges twice. The verdict stays on the website — you are the analyst here.

Input parameters:

- `slug` (string, required): Report slug

### `gsc_overview` (~84 tokens)

Search Console overview

Use this before touching SEO on the user's own site: clicks/impressions trend, device split and period comparison from THEIR connected Google Search Console — numbers no other tool has. Free. Requires GSC connected at tracetify.com/dashboard/gsc (this tool tells you if it is not).

Input parameters:

- `range_days` (number): 28 (default) or 90

### `gsc_queries` (~92 tokens)

Search Console queries

The user's real ranking keywords with position, clicks and CTR — use when deciding what to write or which page to improve, e.g. finding queries at position 5-20 that are one push from page one. Free; own data from their connected Search Console. After you edit a page, this is how you verify it moved.

Input parameters:

- `range_days` (number): 28 (default) or 90

### `gsc_pages` (~67 tokens)

Search Console pages

The user's pages ranked by search performance, including high-impression low-CTR pages whose titles/descriptions are underselling — fix those files right in this editor. Free; own data from their connected Search Console.

Input parameters:

- `range_days` (number): 28 (default) or 90

### `site_audit_start` (~138 tokens)

Start a site audit

Run right after deploying: crawls the site and reports broken links, missing titles/descriptions, redirect chains, thin content and schema gaps — each finding names the page so you can fix it here. Costs credits (price returned before any charge on the confirmation field). Async: poll with site_audit_get.

Input parameters:

- `confirm` (boolean): Set true only after the user agrees to the quoted credit cost
- `request_key` (string): Request key returned by the first confirmation response; must be sent back with confirm=true so retries cannot charge twice
- `url` (string, required): Site to audit, e.g. https://example.com

### `site_audit_get` (~64 tokens)

Read a site audit

Poll an audit started with site_audit_start (free to read). When finished, returns the issue list grouped by severity with affected URLs — work through it top-down and re-run after fixes.

Input parameters:

- `audit_id` (string, required): Audit id from site_audit_start

### `research_competitors` (~122 tokens)

Who competes for the same keywords

The domains fighting a target for the same search terms, with shared-keyword count, their keyword totals and average rank. Use when the user asks who their competitors are, or who a company is up against. Each result says whether we already have a full growth report for that domain — read those with read_report for free instead of tracing them again. Costs credits; cached results are free, and a domain already looked up via research_domain_overview is free here too.

Input parameters:

- `domain` (string, required): Domain to find competitors for, e.g. notion.so

### `research_domain_overview` (~80 tokens)

Domain SEO overview

Estimated organic traffic, keyword count and top keywords for ANY domain — use to size up a competitor the user mentions. Costs credits; cached results are free, and repeated queries within a week hit the cache. For the user's own site prefer gsc_* (free, real data).

Input parameters:

- `domain` (string, required): Domain, e.g. competitor.com

### `research_backlinks` (~72 tokens)

Backlink profile

Who links to a domain: referring domains, authority and anchor texts. Use when planning link building or judging how defensible a competitor's ranking is. Costs credits; cached results are free. Pair with backlink_directories to find places the user can actually get listed.

Input parameters:

- `domain` (string, required): Domain to inspect

### `research_keyword_volume` (~202 tokens)

Keyword search volume & difficulty

Google Ads (Keyword Planner) monthly search volume, CPC, competition, 12-month trend and keyword difficulty (0–100, DataForSEO Labs) for up to 10 keywords in one call. Use when the user asks how often something is searched or how hard it is to rank, or to size a keyword before writing a page. Omit location_code for worldwide volume (difficulty is then computed for the US), or pass a market code for one country. Costs credits; the same keyword set re-queried within a week is free.

Input parameters:

- `keywords` (string, required): Up to 10 search phrases, comma-separated, e.g. "ai image generator, ai avatar maker"
- `location_code` (number): Market: 2840 US, 2826 UK, 2276 DE, 2250 FR, 2724 ES, 2392 JP, 2076 BR, 2356 IN. Omit for worldwide.

### `research_brand_lookup` (~68 tokens)

AI search visibility

How AI assistants (ChatGPT, Perplexity-class) cite a brand: platforms, mention counts and the entities it gets associated with. Use when the user asks "does AI recommend us/them?". Costs credits; cached results are free.

Input parameters:

- `brand` (string, required): Brand or domain

### `backlink_directories` (~80 tokens)

Verified directory list

A hand-verified list of directories and launch platforms that actually give links — checked one by one, dead and nofollow-only entries removed. Use when the user wants backlinks or launch exposure for a new product; filter client-side by language/type/pricing. Costs credits once per day per account — repeat calls the same day are free, so refine freely.

## Diagnostics

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

## Score history

- 2026-09-20: 89
- 2026-09-19: 89
- 2026-09-18: 89
- 2026-09-17: 89
- 2026-09-16: 88
- 2026-09-15: 88
- 2026-09-14: 87
- 2026-09-13: 87
- 2026-09-12: 86
- 2026-09-11: 86
- 2026-09-10: 85
- 2026-09-09: 85
- 2026-09-08: 85
- 2026-09-07: 84
- 2026-09-06: 84
- 2026-09-05: 83
- 2026-09-04: 83
- 2026-09-03: 82
- 2026-09-02: 82
- 2026-09-01: 81
- 2026-08-31: 81
- 2026-08-30: 80
- 2026-08-29: 80
- 2026-08-28: 79
- 2026-08-27: 79
- 2026-08-26: 78
- 2026-08-25: 77
- 2026-08-24: 76
- 2026-08-23: 76
- 2026-08-22: 75

## Common questions

### What is the io.github.tracetify/tracetify-mcp server?

io.github.tracetify/tracetify-mcp is listed in the public MCP registry as io.github.tracetify/tracetify-mcp. Find competitors, trace how they grew, watch what they ship, plus your Search Console. This page covers its hosted endpoint (https://tracetify.com/api/mcp).

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

io.github.tracetify/tracetify-mcp scores 89 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.github.tracetify/tracetify-mcp server expose?

io.github.tracetify/tracetify-mcp exposes 16 tools: search_reports, read_report, start_trace, get_trace, unlock_report, and 11 more. Their descriptions and schemas cost roughly 1,493 tokens of context every time the server is loaded.

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

No. We connected to io.github.tracetify/tracetify-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

io.github.tracetify/tracetify-mcp is still listed as active in the MCP registry. We last reached this channel on 20 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://tracetify.com/api/mcp
- Authorisation metadata: https://tracetify.com/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/tracetify/tracetify-mcp
- Website: https://tracetify.com/
- Changelog RSS feed: https://verifymcp.io/servers/tracetify-tracetify-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tracetify-tracetify-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tracetify-tracetify-mcp/api-mcp