io.github.tracetifyPublished by GitHub account tracetifyv0.7.0Updated Oct 24, 2026
Find competitors, trace how they grew, watch what they ship — plus your Search Console.
Tracetify MCP lets an assistant research competitor growth, SEO, backlinks and ads, and read the user's own Search Console data.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.tracetify%2Ftracetify-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"tracetify": {
"type": "http",
"url": "https://tracetify.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}MCP server for Tracetify — trace how any product actually grew, read your own Search Console, and audit a site, without leaving Claude Code or Cursor.
Most competitive tools tell you where a product stands today. Tracetify reconstructs how it got there: the first mention, the quiet weeks, the directory wave, the launch spike. Twelve sources per trace, every claim linked to the page it came from.
Full setup guide and example questions: tracetify.com/mcp
Start with Competitor Research and GSC SEO Optimizer for sourced competitor briefs and prioritized Search Console work. These free, MIT-licensed workflows use public sources or your own exports and do not require a Tracetify account. Browse the skill source. Connect this MCP server when you want additional Tracetify tools and data; authentication and applicable credit charges still apply.
Create an API key in the dashboard, then pick one of the two transports.
Claude Code — one command:
Or skip the install entirely — nothing to install, not even Node:
Same tools, same balance; the server runs on our side.
Claude Desktop / Cursor take the same JSON (Cursor reads
~/.cursor/mcp.json):
Codex uses TOML in ~/.codex/config.toml — note the snake_case table name:
Your agent picks the right tool on its own — these are real questions, not placeholders:
If your agent ever reaches for the wrong tool, say trace <domain> and it will
come straight here.
Tools that cost credits quote the price first and wait for you to say yes. Reading existing reports never costs anything.
Everything draws from your Tracetify credit balance — the same balance the website uses. No seats, no per-tool add-ons. Top up at tracetify.com/pricing.
It is a thin protocol adapter: MCP tool calls in, Tracetify HTTP API calls out.
No business logic, no data of its own — your API key never leaves your machine
except as an Authorization header to tracetify.com.
MIT
Source: README.md at commit af45dad
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.
queryrequiredRead 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).
slugrequiredTrace 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.
urlrequiredrefreshCheck 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.
job_idrequiredUnlock 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.
slugrequiredSearch 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).
range_daysSearch 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.
range_daysSearch 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.
range_daysStart 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.
urlrequiredconfirmrequest_keyRead 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.
audit_idrequiredWho 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.
domainrequiredDomain 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).
domainrequiredBacklink 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.
domainrequiredKeyword 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.
keywordsrequiredlocation_codeSERP top-10 breakdown
Who holds the Google top 10 for one keyword in one market: per position the domain, URL, whether it is a homepage or an inner page, domain rating (0–1000) and estimated monthly organic traffic. Use when the user asks who ranks for a keyword, whether a keyword is winnable, or which slot is the weakest to go after. Pair with research_keyword_volume for volume and difficulty. Costs credits; the same keyword+market re-queried within a week is free.
keywordrequiredlocation_codeCompetitor ads (Meta + Google)
The ads a domain is running right now on Facebook/Instagram (Meta Ad Library) and Google (Ads Transparency Center): headline, body copy, CTA, landing page URL, creative/video URL, platforms and start dates. Use when the user asks what a competitor is advertising, whether they run paid ads, how long an ad has been live, or wants hooks and angles to model. Costs credits; the same domain re-queried within a week is free. Each source reports separately — null means that source could not be checked, an empty list means it was checked and found nothing.
domainrequiredAI 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.
brandrequiredVerified 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.
Takes no parameters.
100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
claude mcp add tracetify -e TRACETIFY_API_KEY=ttfy_... -- npx -y tracetify-mcpclaude mcp add --transport http tracetify https://tracetify.com/api/mcp --header "Authorization: Bearer ttfy_..."{ "mcpServers": { "tracetify": { "command": "npx", "args": ["-y", "tracetify-mcp"], "env": { "TRACETIFY_API_KEY": "ttfy_..." } } }}[mcp_servers.tracetify]command = "npx"args = ["-y", "tracetify-mcp"]env = { TRACETIFY_API_KEY = "ttfy_..." }