Traffalyzer is an MCP server with 15 tools an agent can call, among them complete_plan_step, complete_quest, get_scan_status. It answers at https://traffalyzer.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 6 November 2026, succeeded.
SEO & UX audits for your websites: findings, Search Console data, growth plan and site scans.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
complete_plan_step | 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 d Inputs: domainId, stepKey, done |
complete_quest | 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 Inputs: questId |
get_scan_status | 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. Inputs: domainId |
growth_plan | 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 Inputs: domainId, stepKey |
keyword_history | 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 Inputs: domainId, query, months |
list_domains | 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 i |
log_measure | 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, adjust Inputs: domainId, title, date, category, pages, note |
next_actions | 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 Inputs: limit, domainId |
page_report | 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 Inputs: domainId, path |
quests_and_issues | 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 s Inputs: domainId, kind, id, status, limit |
run_scan | 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 Inputs: domainId |
search_console_pages | 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 la Inputs: domainId, window, limit |
search_console_queries | 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 peri Inputs: domainId, window, intent, limit |
timeline_events | 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 Inputs: domainId, window, path, kinds |
traffic_trend | 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 Inputs: domainId, window, granularity, path |
Every block below points at https://traffalyzer.com/api/mcp. Pick your client and copy.
claude mcp add --transport http traffalyzer https://traffalyzer.com/api/mcp
{
"mcpServers": {
"traffalyzer": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://traffalyzer.com/api/mcp"]
}
}
}{
"mcpServers": {
"traffalyzer": {
"url": "https://traffalyzer.com/api/mcp"
}
}
}{
"servers": {
"traffalyzer": {
"type": "http",
"url": "https://traffalyzer.com/api/mcp"
}
}
}{
"context_servers": {
"traffalyzer": {
"url": "https://traffalyzer.com/api/mcp"
}
}
}{
"mcpServers": {
"traffalyzer": {
"serverUrl": "https://traffalyzer.com/api/mcp"
}
}
}{
"mcpServers": {
"traffalyzer": {
"url": "https://traffalyzer.com/api/mcp"
}
}
}name: Traffalyzer
version: 0.0.1
schema: v1
mcpServers:
- name: Traffalyzer
type: streamable-http
url: https://traffalyzer.com/api/mcp{
"mcpServers": {
"traffalyzer": {
"httpUrl": "https://traffalyzer.com/api/mcp"
}
}
}{
"mcpServers": {
"traffalyzer": {
"type": "http",
"url": "https://traffalyzer.com/api/mcp"
}
}
}{
"mcpServers": {
"traffalyzer": {
"url": "https://traffalyzer.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Ftraffalyzer.com%2Fapi%2Fmcp&type=streamable_http&id=traffalyzer&name=Traffalyzer
It answered our last check on 6 November 2026 in 158 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by traffalyzer.com and served from traffalyzer.com, the vendor's own domain: https://traffalyzer.com/api/mcp.
15, as returned by the server's own tools/list on 11 November 2026: complete_plan_step, complete_quest, get_scan_status, growth_plan, keyword_history, list_domains, log_measure, next_actions, and 7 more.
It answered our last check on 6 November 2026 in 158 ms. Over 4 checks since 23 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://traffalyzer.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.traffalyzer. Endpoint host: traffalyzer.com. ARD identifier: urn:air:com.traffalyzer:mcp:traffalyzer.
First indexed 19 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.