io.github.im-ff/crawlinx-mcp
REMOTE · CRAWLINX.COM
Free technical-SEO audit MCP: crawl a site, run checks, return an LLM-ready shareable report.
Available components
Last scanned (6 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 22 Oct 2026.
Category Marketing and SEO
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 29 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Oct 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 27 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Oct 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HTTPS: fail → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 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 18
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 29 Oct 2026 · Probed https://crawlinx.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of crawlinx.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| crawlinx.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://crawlinx.com/mcp | Unreachable | ||
| http (plaintext) | http://crawlinx.com/mcp | HTTPS enforced |
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 →
diff_scan ~74
Diff a scan against the previous scan of the same domain: health movement plus the issue codes that were fixed or newly appeared/regressed. Use this when auditing in a loop to verify fixes landed and nothing regressed.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | The current scan id; the previous scan of the same domain is found automatically. |
No output schema declared.
No examples provided.
get_issue_detail ~99
Drill into one issue code: every affected URL plus step-by-step remediation (what to change, why, and when it's a false alarm). Call this after get_report_markdown to expand a code from the collapsed table before applying fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The issue code to expand, e.g. "links.broken_internal" or "title.too_long". |
| scan_id | string | yes | The scan id returned by scan_url. |
No output schema declared.
No examples provided.
get_report ~65
PREFERRED for reasoning about what to fix. Fetch a finished report as structured JSON (health score, category subscores, all issues with URLs, stats). Use this when you need to decide which problems matter.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | The scan id returned by scan_url. |
No output schema declared.
No examples provided.
get_report_markdown ~138
Fetch a finished report as compact, agent-ready Markdown: health, a prioritized fix plan with remediation, and issues collapsed to one row per code (code | severity | count | example URLs) — small enough to keep in context on a real site. Set full=true for the complete human report (large). Use get_issue_detail to expand any single code.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional domain label for the report heading. |
| full | boolean | – | When true, return the full human report (all occurrences, checks coverage). Default false = compact agent view. |
| scan_id | string | yes | The scan id returned by scan_url. |
No output schema declared.
No examples provided.
scan_url ~133
Submit a URL to Crawlinx for an SEO audit. Crawls up to max_pages pages (default 50, max 200), runs the technical-SEO checks, and returns a scan id; poll get_report / get_report_markdown until the crawl finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| max_pages | integer | – | How many pages to crawl. Default 50; maximum 200. Ignored for mode=instant. |
| mode | string | – | Scan mode: "free" (default, multi-page) or "instant" (single-page quick check). |
| url | string | yes | The absolute http(s) URL to audit. |
No output schema declared.
No examples provided.
How do I install the io.github.im-ff/crawlinx-mcp server?
io.github.im-ff/crawlinx-mcp is a hosted endpoint at https://crawlinx.com/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 · crawlinx.com
claude mcp add --transport http im-ff-crawlinx-mcp 'https://crawlinx.com/mcp'
What is the io.github.im-ff/crawlinx-mcp server?
io.github.im-ff/crawlinx-mcp is listed in the public MCP registry as io.github.im-ff/crawlinx-mcp. Free technical-SEO audit MCP: crawl a site, run checks, return an LLM-ready shareable report. This page covers its hosted endpoint (https://crawlinx.com/mcp).
Is the io.github.im-ff/crawlinx-mcp server safe to use?
io.github.im-ff/crawlinx-mcp scores 0 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 io.github.im-ff/crawlinx-mcp server expose?
io.github.im-ff/crawlinx-mcp exposes 5 tools: scan_url, get_report, get_report_markdown, get_issue_detail, diff_scan. Their descriptions and schemas cost roughly 509 tokens of context every time the server is loaded.
Does the io.github.im-ff/crawlinx-mcp server require authentication?
Its publisher declares no required credentials for io.github.im-ff/crawlinx-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.im-ff/crawlinx-mcp server still maintained?
io.github.im-ff/crawlinx-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.