Traffalyzer
REMOTE · TRAFFALYZER.COM
SEO & UX audits for your websites: findings, Search Console data, growth plan and site scans.
Available components
Last scanned (2 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1898 tokens (~126/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 +52
- HSTS header: pass → fail ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 95 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Authorization: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://traffalyzer.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=traffalyzer.com | CN=YR2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | RSA 4096 | SHA256-RSA | 563948bf49020f40dd4b4a96036181c92e9 |
| SANs: traffalyzer.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of traffalyzer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| traffalyzer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://traffalyzer.com/.well-known/oauth-protected-resource/api/mcp"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://traffalyzer.com/.well-known/oauth-protected-resource/api/mcp"Protected resource metadata
| Document | https://traffalyzer.com/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://traffalyzer.com/api/mcp |
| Authorisation server | https://rmelbbzikljxtnbhqkmu.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://traffalyzer.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://traffalyzer.com/api/mcp | HTTPS enforced | 301 | https://traffalyzer.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
complete_plan_step Complete plan step ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| done | boolean | – | false un-ticks the step. Defaults to true. |
| stepKey | string | yes | Step key from the growth_plan structure. |
No output schema declared.
No examples provided.
complete_quest Complete quest ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| questId | string | yes | Quest id from quests_and_issues (kind=quest). |
No output schema declared.
No examples provided.
get_scan_status Scan status ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
No output schema declared.
No examples provided.
growth_plan Growth plan ~111
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| stepKey | string | – | Key of a single step from the plan structure. |
No output schema declared.
No examples provided.
keyword_history Keyword history ~165
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| months | – | – | History length in months, defaults to 16 (paid domains only; free gets 3). |
| query | string | yes | The exact search query, e.g. 'seo tool kostenlos'. |
No output schema declared.
No examples provided.
list_domains List domains ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_measure Log measure ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| date | string | – | YYYY-MM-DD, defaults to today. Not in the future. |
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| note | string | – | – |
| pages | array | – | Affected paths; omit for the whole site. |
| title | string | yes | What was done, short, in the user's language. |
No output schema declared.
No examples provided.
next_actions What to work on next ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | – | Restrict to a single project. Omit to cover all of them. |
| limit | integer | – | Maximum entries, defaults to 15. |
No output schema declared.
No examples provided.
page_report Page report ~92
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| path | string | yes | Path of the page, e.g. '/pricing'. |
No output schema declared.
No examples provided.
quests_and_issues Quests and issues ~165
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| id | string | – | Id of a single entry for full details. |
| kind | string | yes | Which list to query. |
| limit | integer | – | Entry count, defaults to 10. |
| status | string | – | Only for kind=quest: OPEN, IMPLEMENTED, VERIFIED_SUCCESS, VERIFIED_PARTIAL, VERIFIED_NO_CHANGE, DISMISSED. |
No output schema declared.
No examples provided.
run_scan Run scan ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
No output schema declared.
No examples provided.
search_console_pages Search Console pages ~108
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| limit | integer | – | Row count, defaults to 15. |
| window | string | – | Reporting window, defaults to 28d. |
No output schema declared.
No examples provided.
search_console_queries Search Console keywords ~141
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| intent | string | – | Which report. Defaults to top. |
| limit | integer | – | Row count, defaults to 15. |
| window | string | – | Reporting window, defaults to 28d. |
No output schema declared.
No examples provided.
timeline_events Timeline events ~173
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| kinds | array | – | Only these kinds. Omit for all except scans. |
| path | string | – | Only events of this page (plus site-wide ones). |
| window | string | – | Window, defaults to 90d. |
No output schema declared.
No examples provided.
traffic_trend Traffic trend ~150
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).
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain id of one of the user's projects, as returned by list_domains. |
| granularity | string | – | Resolution of the series, defaults to week. |
| path | string | – | Path of a single page. Omit for the whole site. |
| window | string | – | Reporting window, defaults to 90d. |
No output schema declared.
No examples provided.
How do I install the Traffalyzer MCP server?
Traffalyzer is a hosted endpoint at https://traffalyzer.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · traffalyzer.com
claude mcp add --transport http com-traffalyzer-traffalyzer 'https://traffalyzer.com/api/mcp'
What is the Traffalyzer MCP server?
Traffalyzer is an MCP server listed in the public MCP registry as com.traffalyzer/traffalyzer. SEO & UX audits for your websites: findings, Search Console data, growth plan and site scans. This page covers its hosted endpoint (https://traffalyzer.com/api/mcp).
Is the Traffalyzer MCP server safe to use?
Traffalyzer scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Traffalyzer MCP server expose?
Traffalyzer exposes 15 tools: list_domains, next_actions, run_scan, get_scan_status, search_console_queries, and 10 more. Their descriptions and schemas cost roughly 1,898 tokens of context every time the server is loaded.
Does the Traffalyzer MCP server require authentication?
Yes. Traffalyzer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Traffalyzer MCP server still maintained?
Traffalyzer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.