com.traffalyzerPublished by traffalyzer.comOfficial publisherv1.0.0Updated Oct 29, 2026
SEO & UX audits for your websites: findings, Search Console data, growth plan and site scans.
A remote MCP endpoint from Traffalyzer that gives an assistant access to SEO and UX audits for websites, including findings, Search Console data, growth plans,
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.traffalyzer%2Ftraffalyzer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"traffalyzer": {
"type": "http",
"url": "https://traffalyzer.com/api/mcp"
}
}
}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 id from this list.
Takes no parameters.
What to work on next
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.
limitdomainIdRun 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 of starting a duplicate.
domainIdrequiredScan 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.
domainIdrequiredSearch Console keywords
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).
limitintentwindowdomainIdrequiredKeyword 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 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).
queryrequiredmonthsdomainIdrequiredSearch 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 language (German by default).
limitwindowdomainIdrequiredPage 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 default).
pathrequireddomainIdrequiredTraffic 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 same buckets where the integration is connected. Responses follow the account language (German by default).
pathwindowdomainIdrequiredgranularityTimeline 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 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).
pathkindswindowdomainIdrequiredLog 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, 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.
datenotepagestitlerequiredcategorydomainIdrequiredGrowth 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 free domains some step details are locked. Responses follow the account language (German by default).
stepKeydomainIdrequiredQuests 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 single entry. Responses follow the account language (German by default).
idkindrequiredlimitstatusdomainIdrequiredComplete 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 kind=quest. Never call this without an explicit user request.
questIdrequiredComplete 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 domains — the free preview is read-only. Never call this without an explicit user request.
donestepKeyrequireddomainIdrequired72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Publish an icon in the registry entry.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
