_ registry / mcp http-sse · checked 25h ago

traffalyzer

https://traffalyzer.com

Registry code: 8fe3438bb8735701

api record

SEO & UX audits for your websites: findings, Search Console data, growth plan and site scans.

from a public catalogue that lists it, not from the operator

endpoint
https://traffalyzer.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
bearer
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is traffalyzer live?
Yes — it answered the hub's last check (checked 25h ago). It answered 12% of checks over the last 30 days.
Is traffalyzer free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does traffalyzer have?
15 tools: keyword_history, page_report, traffic_trend, timeline_events, log_measure, growth_plan, complete_quest, complete_plan_step, ….
Is traffalyzer safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
11.8%

90 days 55.3%· all time 55.3%

latency
90ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 38 checks · signed record
  • retired → live
  • degraded → retired· HTTP 500
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
15 auth-required 15 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • keyword_history auth-required never probed

    Month-by-month history of a single keyword from Google Search Console (clicks, impressions, impression-weighted position) plus the pages ranking for it. Use it to see how a query developed, whether it is seasonal, or which page Google shows for it. Pass the query exactly as Search Console lists it. 16 months for paid domains, 3 months otherwise. Requires the user to have connected Search Console. Responses follow the account language (German by default).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId",
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "The exact search query, e.g. 'seo tool kostenlos'."
    },
    "months": {
      "anyOf": [
        {
          "type": "number",
          "const": 3
        },
        {
          "type": "number",
          "const": 16
        }
      ],
      "description": "History length in months, defaults to 16 (paid domains only; free gets 3)."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 33 lines
  • page_report auth-required never probed

    A full report for a single page of the domain: search performance, analytics behavior (sessions, bounce rate, engagement time where connected), page classification and its top search queries. Responses follow the account language (German by default).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId",
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Path of the page, e.g. '/pricing'."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 18 lines
  • traffic_trend auth-required never probed

    Search performance over time for the whole site or a single page — is it getting better or worse, did a change have an effect. Weekly by default, daily with granularity=day when an exact date matters. Includes Plausible visitor data for the same buckets where the integration is connected. Responses follow the account language (German by default).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Path of a single page. Omit for the whole site."
    },
    "window": {
      "enum": [
        "28d",
        "90d",
        "180d"
      ],
      "type": "string",
      "description": "Reporting window, defaults to 90d."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    },
    "granularity": {
      "enum": [
        "week",
        "day"
      ],
      "type": "string",
      "description": "Resolution of the series, defaults to week."
    }
  }
}
    arguments 34 lines
  • timeline_events auth-required never probed

    Dated events on the site's history timeline: measures the user logged themselves, completed quests, fixed issues, ticked plan steps, CMS edits, detected wins, scans and Google ranking updates (core, spam …) with their rollout dates. Use it to explain why a curve moved, what was changed when, or whether a measure worked; pair it with traffic_trend. Free domains only get the last 28 days. Responses follow the account language (German by default).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Only events of this page (plus site-wide ones)."
    },
    "kinds": {
      "type": "array",
      "items": {
        "enum": [
          "MANUAL",
          "QUEST",
          "ISSUE",
          "PLAN_STEP",
          "CMS_EDIT",
          "WIN",
          "SCAN",
          "GOOGLE_UPDATE"
        ],
        "type": "string"
      },
      "description": "Only these kinds. Omit for all except scans."
    },
    "window": {
      "enum": [
        "28d",
        "90d",
        "180d",
        "16m"
      ],
      "type": "string",
      "description": "Window, defaults to 90d."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 44 lines
  • log_measure auth-required never probed

    Log a change the user made to their website themselves (e.g. 'added internal links to /blog/x', 'new images in the guide') on the history timeline. Traffalyzer then measures its effect automatically: 28 days before vs. 28 days after, adjusted for the rest of the site. Backdating is allowed up to 16 months; old enough entries are measured right away. Free domains can have 3 active measures. Never call this without an explicit user request.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId",
    "title"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD, defaults to today. Not in the future."
    },
    "note": {
      "type": "string",
      "maxLength": 2000
    },
    "pages": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 10,
      "description": "Affected paths; omit for the whole site."
    },
    "title": {
      "type": "string",
      "maxLength": 200,
      "description": "What was done, short, in the user's language."
    },
    "category": {
      "enum": [
        "INTERNAL_LINKS",
        "CONTENT_UPDATE",
        "NEW_CONTENT",
        "TITLE_META",
        "MEDIA",
        "TECHNICAL",
        "STRUCTURED_DATA",
        "REDIRECT",
        "OFFPAGE",
        "RELAUNCH",
        "OTHER"
      ],
      "type": "string"
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 51 lines
  • growth_plan auth-required 25h ago

    The domain's current growth plan: diagnosis, bottleneck, phases and steps. Without a stepKey the structure with all step keys is returned; with a stepKey the full step including rationale, implementation guidance and verification status. On free domains some step details are locked. Responses follow the account language (German by default).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId"
  ],
  "properties": {
    "stepKey": {
      "type": "string",
      "description": "Key of a single step from the plan structure."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 17 lines
  • complete_quest auth-required never probed

    Mark one of the user's quests as implemented after the recommended change has actually been made. Awards the quest's XP and starts result verification. Only quests with status OPEN can be completed; get quest ids from quests_and_issues with kind=quest. Never call this without an explicit user request.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "questId"
  ],
  "properties": {
    "questId": {
      "type": "string",
      "description": "Quest id from quests_and_issues (kind=quest)."
    }
  }
}
    arguments 13 lines
  • complete_plan_step auth-required never probed

    Tick off (or un-tick with done=false) a step of the domain's growth plan after the work has actually been done. Awards XP on first completion and starts result verification. Step keys come from the growth_plan tool. Only available on paid domains — the free preview is read-only. Never call this without an explicit user request.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId",
    "stepKey"
  ],
  "properties": {
    "done": {
      "type": "boolean",
      "description": "false un-ticks the step. Defaults to true."
    },
    "stepKey": {
      "type": "string",
      "description": "Step key from the growth_plan structure."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 22 lines
  • search_console_pages auth-required never probed

    Page-level Search Console performance for one domain: which pages get clicks and impressions, at which average position. Useful to find the pages that carry the organic traffic and the ones that underperform. Responses follow the account language (German by default).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Row count, defaults to 15."
    },
    "window": {
      "enum": [
        "7d",
        "28d",
        "90d"
      ],
      "type": "string",
      "description": "Reporting window, defaults to 28d."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 28 lines
  • run_scan auth-required never probed

    Start a new SEO/UX scan (crawl) for one of the user's domains. Scans run asynchronously and usually take a few minutes; poll get_scan_status for progress and the resulting scores. If a scan is already in progress, its id is returned instead of starting a duplicate.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId"
  ],
  "properties": {
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 13 lines
  • search_console_queries auth-required never probed

    Keyword data from Google Search Console for one domain. intent=top returns the strongest keywords, intent=opportunities keywords ranking on positions 5-20 with potential, intent=movers the biggest winners and losers versus the previous period of equal length. Requires the user to have connected Search Console. Responses follow the account language (German by default).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Row count, defaults to 15."
    },
    "intent": {
      "enum": [
        "top",
        "opportunities",
        "movers"
      ],
      "type": "string",
      "description": "Which report. Defaults to top."
    },
    "window": {
      "enum": [
        "7d",
        "28d",
        "90d"
      ],
      "type": "string",
      "description": "Reporting window, defaults to 28d."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 37 lines
  • quests_and_issues auth-required never probed

    The domain's task list: quests (concrete recommendations with implementation guidance and XP rewards) and issues (technical findings from the latest crawl with affected URLs). Use kind=quest or kind=issue; pass an id for full details of a single entry. Responses follow the account language (German by default).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId",
    "kind"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Id of a single entry for full details."
    },
    "kind": {
      "enum": [
        "quest",
        "issue"
      ],
      "type": "string",
      "description": "Which list to query."
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Entry count, defaults to 10."
    },
    "status": {
      "type": "string",
      "description": "Only for kind=quest: OPEN, IMPLEMENTED, VERIFIED_SUCCESS, VERIFIED_PARTIAL, VERIFIED_NO_CHANGE, DISMISSED."
    },
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 36 lines
  • get_scan_status auth-required 2d ago

    Status and results of the most recent scan of a domain: whether it is pending, running, completed or failed, the overall score and its sub-scores (technical, on-page, engagement, AI visibility), pages crawled and the number of issues found.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domainId"
  ],
  "properties": {
    "domainId": {
      "type": "string",
      "description": "Domain id of one of the user's projects, as returned by list_domains."
    }
  }
}
    arguments 13 lines
  • list_domains auth-required 25h ago

    List all website projects (domains) in the user's Traffalyzer account, including their domain id, URL, plan status (free or paid) and the latest scan result with its overall score. Call this first — every domain-scoped tool needs a domain id from this list.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • next_actions auth-required 25h ago

    The prioritised to-do list across ALL of the user's domains in a single call: critical and high-severity issues, open quests, the next unfinished growth-plan step, projects with a missing or stale scan, and missing integrations. Start here when the user asks what to improve, what to do next, or to 'optimise the site' without naming a specific domain — it saves querying every project separately. Each entry names the domain, an id or key to work with, and which tool to call next.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Maximum entries, defaults to 15."
    },
    "domainId": {
      "type": "string",
      "description": "Restrict to a single project. Omit to cover all of them."
    }
  }
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8fe3438bb8735701.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8fe3438bb8735701/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8fe3438bb8735701/badge.svg)](https://brick.blue/agent/8fe3438bb8735701?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.