← crawlinx.com

INDIVIDUAL MCP TOOL

get_report

PREFERRED for reasoning about what to fix.

crawlinx.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://crawlinx.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_report and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

crawlinx.com

CONNECT 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.

Related tools

  • scan_url — Submit a URL to Crawlinx for an SEO audit.
  • get_report_markdown — 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.
  • get_issue_detail — Drill into one issue code: every affected URL plus step-by-step remediation (what to change, why, and when it's a false alarm).
  • diff_scan — Diff a scan against the previous scan of the same domain: health movement plus the issue codes that were fixed or newly appeared/regressed.