Tracetify MCP

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 컴퓨터 또는 클라우드
• 전송 방식: stdio, Streamable HTTP
• 카테고리: 검색 및 AI 기억
• 입력해야 할 값: TRACETIFY_API_KEY, Authorization

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요
• npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

{
  "mcpServers": {
    "tracetify": {
      "command": "npx",
      "args": [
        "-y",
        "tracetify-mcp"
      ],
      "env": {
        "TRACETIFY_API_KEY": "your-value"
      }
    }
  }
}

claude mcp add --transport http tracetify https://tracetify.com/api/mcp --header 'Authorization: your-value'

claude mcp add tracetify --env TRACETIFY_API_KEY=your-value -- npx -y tracetify-mcp

{
  "mcpServers": {
    "tracetify": {
      "url": "https://tracetify.com/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "mcpServers": {
    "tracetify": {
      "command": "npx",
      "args": [
        "-y",
        "tracetify-mcp"
      ],
      "env": {
        "TRACETIFY_API_KEY": "your-value"
      }
    }
  }
}

{
  "servers": {
    "tracetify": {
      "type": "http",
      "url": "https://tracetify.com/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "tracetify": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "tracetify-mcp"
      ],
      "env": {
        "TRACETIFY_API_KEY": "your-value"
      }
    }
  }
}

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

• TRACETIFY_API_KEY 비밀 필수 env
  Tracetify API key — create one at https://tracetify.com/dashboard (AI & MCP page)
• Authorization 비밀 필수 HTTP header
  Bearer — create one at https://tracetify.com/dashboard/ai

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 8일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

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

• 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).

• 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_t

• 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_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: u

• 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_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

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

• 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:

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

• 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 doma

• 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_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_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 wr

• 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 whic

• 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

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

• 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

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 GitHub 계정 tracetify 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  349ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 18개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

검색 및 AI 기억 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 5676개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 5676개 중 61%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 5676개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

claude mcp add tracetify -e TRACETIFY_API_KEY=ttfy_... -- npx -y tracetify-mcp

claude mcp add --transport http tracetify https://tracetify.com/api/mcp --header "Authorization: Bearer ttfy_..."

{

[mcp_servers.tracetify]