Tracetify MCP is answering right now. Last checked 7 min ago. 100 installs a week from npm. It exposes 15 tools. Last commit 21 Aug 2026.
Find competitors, trace how they grew, watch what they ship — plus your Search Console.
Installs per day
peak 831 · avg 28
a month agotoday
Uptime history
13 days of history
13 days agonow
100.0%
Uptime 24h
91 of 91 checks
15
Tools
read from the server
331 ms
Response time
average over 24h
100
Installs / week
npm and PyPI
Nothing serious here today
Today is the operative word: we check Tracetify MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add tracetify-mcp --transport http https://tracetify.com/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"tracetify-mcp": {
"url": "https://tracetify.com/api/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.tracetify-mcp]
url = "https://tracetify.com/api/mcp".cursor/mcp.json
{
"mcpServers": {
"tracetify-mcp": {
"url": "https://tracetify.com/api/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"tracetify-mcp": {
"url": "https://tracetify.com/api/mcp"
}
}
}Available tools 15
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
research
research_backlinks
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.
research_brand_lookup
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.
research_competitors
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.
research_domain_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).
gsc
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. Free. Requires GSC connected at tracetify.com/dashboard/gsc (this tool tells you if it is not).
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. Free; own data from their connected Search Console.
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.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.
site
site_audit_get
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.
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. Costs credits (price returned before any charge on the confirmation field). Async: poll with site_audit_get.
backlink
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. 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.
report
read_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).
reports
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. Returns matching report slugs for read_report. Searches by domain or name fragment.
start
start_trace
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.
trace
get_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.
unlock
unlock_report
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://tracetify.com/api/mcp | streamable-http | answering | 289 ms | 7 min ago |
Alternatives to Tracetify MCP
same job, measured the same wayCompetitortracker
by competitortracker
Track competitors from your AI assistant: change feed, page snapshots, labels and alerts.
MCP Public Award Monitor
by mambabuilt
Find the companies that won US or UK public contracts, grants or SBIR awards in a window.
CLI
by noticedso
Search your developer network and trace connection paths via GitHub & LinkedIn.
A
ProductNow
by productnow
Turn prototype feedback into product decisions that your whole team can trace.
Eutexa CRM
by eutexa
Search contacts, track deals, create tasks and log notes in your Eutexa CRM workspace.
Semantica AI — AI Search Visibility
by ai-semantica
Monitor brand visibility, citations, competitors, sentiment, and GEO performance in AI search.
Hypathesis
by predme
Variable relationships from research papers with causal direction and source traceback.
Realestateapi
by pipeworx-io
RealEstateAPI MCP — property search, detail, and skip-trace (realestateapi.com)
Tracetify MCP — questions
Answers built from our own checks of this server.
What can Tracetify MCP do?
It exposes 15 tools, read directly from the server on our last check. Among them: backlink_directories, get_trace, gsc_overview, gsc_pages, gsc_queries, read_report and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Tracetify MCP mostly used for?
Its tools cluster around research, gsc and site. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Tracetify MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 331 ms. The bar chart above shows every period we have measured.
How do I connect Tracetify MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tracetify MCP need an API key?
No. Tracetify MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tracetify MCP?
It answers our handshake in 331 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Tracetify MCP?
The npm package tracetify-mcp was installed 100 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Tracetify MCP open source?
Yes — it is published under the MIT licence, written in JavaScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.