io.github.im-ff/crawlinx-mcp
REMOTE · CRAWLINX.COM · SCANNED SEP 20
Free technical-SEO audit MCP: crawl a site, run checks, return an LLM-ready shareable report.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 405. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.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.
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'
{
"mcpServers": {
"im-ff-crawlinx-mcp": {
"url": "https://crawlinx.com/mcp"
}
}
} {
"servers": {
"im-ff-crawlinx-mcp": {
"type": "http",
"url": "https://crawlinx.com/mcp"
}
}
} [mcp_servers.im-ff-crawlinx-mcp] url = "https://crawlinx.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"im-ff-crawlinx-mcp": {
"type": "remote",
"url": "https://crawlinx.com/mcp",
"enabled": true
}
}
} openclaw mcp add im-ff-crawlinx-mcp --url 'https://crawlinx.com/mcp' --transport streamable-http
mcp_servers:
im-ff-crawlinx-mcp:
url: "https://crawlinx.com/mcp" {
"McpServers": {
"im-ff-crawlinx-mcp": {
"Transport": "http",
"Url": "https://crawlinx.com/mcp"
}
}
} assistant mcp add im-ff-crawlinx-mcp -t streamable-http -u 'https://crawlinx.com/mcp'
{
"mcpServers": {
"im-ff-crawlinx-mcp": {
"type": "http",
"url": "https://crawlinx.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Aug 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 Jul 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
- 27 Jul 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
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://crawlinx.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=crawlinx.com | CN=GoDaddy TLS Intermediate CA DV - R1v1,O=GoDaddy.com,C=US | 28 Aug 2026 | 14 Mar 2027 | RSA 2048 | SHA256-RSA | 27f84d17327b2da1 |
| SANs: crawlinx.com | ||||||
| CN=GoDaddy TLS Intermediate CA DV - R1v1,O=GoDaddy.com,C=US (CA) | CN=GoDaddy TLS Root CA - R1,O=GoDaddy.com,C=US | 28 Aug 2025 | 24 Aug 2040 | RSA 4096 | SHA256-RSA | 8aaa80515c0bc688c7955d70f27758ac |
| CN=GoDaddy TLS Root CA - R1,O=GoDaddy.com,C=US (CA) | CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US | 24 Sept 2025 | 31 Dec 2037 | RSA 4096 | SHA256-RSA | 90de6c7fb3b50b3c0617724fc13402ad |
| CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US (CA) | CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US | 1 Sept 2009 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 0 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of crawlinx.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| crawlinx.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 405 |
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 | HTTP error | 405 | |
| http (plaintext) | http://crawlinx.com/mcp | Served over HTTP | 200 |
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.
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 18 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?
No. We connected to io.github.im-ff/crawlinx-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.im-ff/crawlinx-mcp server still maintained?
io.github.im-ff/crawlinx-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.