Analytics
crawlinx.com
Provides SEO auditing and analysis tools to scan URLs, generate detailed reports, and track fixes.
ENDPOINT 1
https://crawlinx.com/mcp
MCP server metadata
- Name
- crawlwise-mcp
- Version
- 1.0.0
Crawlinx SEO auditing. Workflow: (1) scan_url to start an audit — call it when the user ships/deploys a site, changes meta/routing, or asks whether SEO/indexing is OK. It crawls 50 pages by default; pass max_pages (up to 200) for a deeper crawl of larger sites. (2) Poll get_report_markdown (compact: health + a prioritized fix plan with remediation + issues collapsed by code) or get_report (JSON) until ready. (3) get_issue_detail(scan_id, code) to expand one code (all URLs + step-by-step fix) before applying changes. (4) After re-scanning, diff_scan(scan_id) to confirm fixes landed and nothing regressed. Fix top-priority items first; the compact report already ranks them.
Known tools 5
get_report_markdownFetch 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.
Inferred read-onlyget_issue_detailDrill into one issue code: every affected URL plus step-by-step remediation (what to change, why, and when it's a false alarm).
Inferred read-onlydiff_scanDiff a scan against the previous scan of the same domain: health movement plus the issue codes that were fixed or newly appeared/regressed.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.crawlwise-mcp]
url = "https://crawlinx.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"crawlwise-mcp": {
"type": "http",
"url": "https://crawlinx.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: crawlwise-mcp
Remote MCP URL: https://crawlinx.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"crawlwise-mcp": {
"url": "https://crawlinx.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"crawlwise-mcp": {
"type": "http",
"url": "https://crawlinx.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "crawlwise-mcp",
"transport": "streamable-http",
"url": "https://crawlinx.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for crawlinx.com was fetched 2026-08-24T07:19:59.662Z.
crawlinx.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.