mcpbeat Sign in

Tracetify MCP Server

by tracetify Your server? Claim it
not responding

Tracetify MCP is listed as active in the registry but did not answer our last check. 36 installs a week from npm. It exposes 18 tools. Last commit 8 Oct 2026.

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

Installs per day peak 165 · avg 17 · +177% w/w
a month agotoday
Uptime history 67 days of history · worst day 0%
67 days agonow
2.2%
Uptime 24h
2 of 91 checks
18
Tools
read from the server
377 ms
Response time
average over 24h
36
Installs / week
npm and PyPI

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 August 2026. No other catalogue keeps this.

8 Oct a tool appeared research_serp_breakdown
3 Oct a tool appeared research_competitor_ads
7 Sep a tool description was rewritten research_keyword_volume
7 Sep a tool changed version
4 Sep a tool appeared research_keyword_volume
20 Aug a tool appeared research_competitors

Tracetify MCP does not always answer

Over the last week it answered 9.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add tracetify-mcp --transport http https://tracetify.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "tracetify-mcp": {
      "type": "http",
      "url": "https://tracetify.com/api/mcp"
    }
  }
}

Available tools 18

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_competitor_ads
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.
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).
research_keyword_volume
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.
research_serp_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.
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

URLTransportStateLatencyChecked
https://tracetify.com/api/mcp streamable-http answering 114 ms 9 min ago

Alternatives to Tracetify MCP

same job, measured the same way
1lev1
by avi-adam

Track partnership work, log mission hours, and see what needs your approval on 1lev1.com.

60 tools answering
Competitortracker
by competitortracker

Track competitors from your AI assistant: change feed, page snapshots, labels and alerts.

1 tools answering
MCP Public Award Monitor
by mambabuilt

Find the companies that won US or UK public contracts, grants or SBIR awards in a window.

240 installs/wk local only
MCP Competitor Price Stock Changelog Monitor
by mambabuilt

Competitor price, stock, plan, and changelog changes since your last run.

43 installs/wk local only
Eutexa CRM
by eutexa

Search contacts, track deals, create tasks and log notes in your Eutexa CRM workspace.

answering
Semantica AI — AI Search Visibility
by ai-semantica

Monitor brand visibility, citations, competitors, sentiment, and GEO performance in AI search.

94 tools answering
Hypathesis
by predme

Variable relationships from research papers with causal direction and source traceback.

4 tools answering
Realestateapi
by pipeworx-io

RealEstateAPI MCP — property search, detail, and skip-trace (realestateapi.com)

44 tools answering

Tracetify MCP — questions

Answers built from our own checks of this server.

What can Tracetify MCP do?
It exposes 18 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 12 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 2 of 91 checks got a reply (2.2%), average response time 377 ms. The bar chart above shows every period we have measured.
The registry lists Tracetify MCP as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
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 in the form 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 18 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 377 ms on average, which is faster than 35% 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 36 times in the last week. Week over week that is +177%. 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?
The code is open source: it is published under the MIT licence, written in JavaScript and 1 stars on GitHub. The licence covers the code in the repository, not the hosted service at tracetify.com, which runs on its operator's own terms.