io.github.im-ff/crawlinx-mcp
REMOTE · CRAWLINX.COM · SCANNED AUG 3
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 →
Endpoint Security63
- 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 call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 680 tokens (~136/item across 5 items; 5 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · crawlinx.com
claude mcp add --transport http im-ff-crawlinx-mcp 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 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.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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.
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 65
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 3 Aug 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=WE1,O=Google Trust Services,C=US | 10 Jul 2026 | 8 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | a732330f5400d3280ea6da9f5439d64f |
| SANs: crawlinx.com, *.crawlinx.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
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 | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; frame-ancestors 'self'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://crawlinx.com/mcp | Verified | 200 | |
| http (plaintext) | http://crawlinx.com/mcp | HTTPS enforced | 301 | https://crawlinx.com/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.
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.