Analytics

tracetify.com

Provides growth reports and trace analysis to understand how products, competitors, or domains acquired users and traffic.

1 endpoint14 known toolsFirst detected August 17, 2026Last detected August 17, 2026

ENDPOINT 1

https://tracetify.com/api/mcp

No auth detected

MCP server metadata

Name: tracetify
Version: 0.3.0

Capabilities

tools.listChanged

Known tools 14

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

Inferred read-only

read_report

Read one growth report by slug (from search_reports or a finished trace).

Inferred read-only

start_trace

Run this when search_reports finds nothing (or the user wants fresh data) for "how did X grow?

Inferred read-only

get_trace

Poll a trace started with start_trace.

Inferred read-only

unlock_report

Permanently unlock a report's full timeline, evidence and SEO detail for this account.

Inferred read-only

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

Inferred read-only

gsc_queries

The user's real ranking keywords with position, clicks and CTR — use when deciding what to write or which page to improve, e.

Potential side effects

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

Inferred read-only

site_audit_start

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.

Inferred read-only

site_audit_get

Poll an audit started with site_audit_start (free to read).

Inferred read-only

research_domain_overview

Estimated organic traffic, keyword count and top keywords for ANY domain — use to size up a competitor the user mentions.

Inferred read-only

research_backlinks

Who links to a domain: referring domains, authority and anchor texts.

Inferred read-only

research_brand_lookup

How AI assistants (ChatGPT, Perplexity-class) cite a brand: platforms, mention counts and the entities it gets associated with.

Inferred read-only

backlink_directories

A hand-verified list of directories and launch platforms that actually give links — checked one by one, dead and nofollow-only entries removed.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tracetify]
url = "https://tracetify.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tracetify": {
      "type": "http",
      "url": "https://tracetify.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tracetify
Remote MCP URL: https://tracetify.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "tracetify",
  "transport": "streamable-http",
  "url": "https://tracetify.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.