INDIVIDUAL MCP TOOL

unlock_report

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

tracetify.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://tracetify.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for unlock_report and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

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.

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.
read_report — Read one growth report by slug (from search_reports or a finished trace).
start_trace — Run this when search_reports finds nothing (or the user wants fresh data) for "how did X grow?
get_trace — Poll a trace started with start_trace.
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.
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.
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.
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.