Wrendex
Server Details
Technical SEO audit tools over MCP. Wrendex crawls a site with 140+ checks (broken links, redirects, canonicals, hreflang, sitemaps, structured data, duplicate trackers, render-blocking resources, Core Web Vitals page weight) and exposes crawl runs, issues and fix lists as tools so coding agents like Claude Code, Cursor and Codex can audit and fix a site. Stateless Streamable HTTP; authenticate with a Wrendex bearer token from https://wrendex.com/docs.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes (crawl lifecycle, alerts, ignoring, tenant/site listing, billing). However, get_crawl_alerts, get_crawl_issues, and get_crawl_issue_summary form a cluster of three similarly-named tools that all surface crawl findings; the descriptions do explain the differences, but an agent could still misselect among them.
Nearly every tool follows a clean snake_case verb_noun pattern (cancel_crawl, enqueue_crawl, get_crawl, list_sites, ignore_alert, unignore_alert). The get_/list_ split is used consistently for single vs. collection retrieval, with only minor specialized names like create_checkout_session and get_duplicate_code_regions.
17 tools is on the heavier side but earns its place across a genuinely broad domain: crawl lifecycle, alert triage, ignore rules, health scoring, tenant/site navigation, search, and billing. No obvious redundant or filler tools, though it leans slightly large.
The core crawl-audit workflow is well covered end-to-end: enqueue, monitor, analyze alerts/issues, ignore, recrawl to verify, and track health scores, plus tenant/site discovery and billing checkout. Gaps remain around write/management operations for sites and plans (only get/list for sites, no create/update/delete), which agents would need to work around.
Available Tools
17 toolscancel_crawlAInspect
Stop an in-flight crawl run. Pages already crawled are kept and scored; the run finishes in status "cancelled". Returns 409 if the run has already finished crawling. Requires a WRITE-scoped token and EDITOR, ADMIN or OWNER role.
Inputs: crawlId (required).
create_checkout_sessionAInspect
Create a Stripe Checkout link that subscribes the workspace to a plan. Returns {url, sessionId}. Nothing is charged until a person opens the url and completes payment, so hand it to whoever owns the workspace. Every workspace gets 5,000 free credits a month (reset on the 1st) and can crawl on those without a plan; a plan adds a larger monthly allowance and storage. The caller must be an OWNER or ADMIN of the tenant. An agent-created workspace must be claimed by a person first: until then this returns 409 WORKSPACE_UNCLAIMED with the claimUrl to send them. Plan prices and monthly credits: GET /api/pricing (no token needed).
Inputs: tenantId (required), priceTier (required), returnUrl.
enqueue_crawlAInspect
Enqueue a new recursive crawl run for a site. Returns the queued CrawlRun, or the already-active run if one is queued or running. Re-crawls are incremental by default: after the first completed crawl, pages whose sitemap lastmod has not moved or that the server answers 304 Not Modified are carried forward at no credit cost. Pass mode="full" to re-fetch every page. Requires a WRITE-scoped token and EDITOR, ADMIN or OWNER role, and consumes crawl credits for pages downloaded.
Inputs: siteId (required), mode.
get_crawlBInspect
Get a single crawl run by id, including its status and progress.
Inputs: crawlId (required).
get_crawl_alertsAInspect
List individual alerts for a crawl run, each with its pageUrl, message, detail, and affectedUrls. Checks that report per target (broken links, images, stylesheets, scripts, mixed content) file one alert per target, so affectedUrls holds that single URL and the HTTP status is in the message; for HTTP_404 the pageUrl itself is the failing URL. Pass type to drill into one issue type (e.g. LINKS_TO_BROKEN, HTTP_404, DUPLICATE_H1). Pass a filter or pagination param so the response is the filtered, paginated result.
Inputs: crawlId (required), page, size, type, +3 more.
get_crawl_issuesBInspect
Summarize the SEO and quality issues found in a crawl run, grouped by type and severity (ignored alerts excluded).
Inputs: crawlId (required).
get_crawl_issue_summaryAInspect
Roll a crawl's alerts up into unique issues to fix, ranked by reach. The checks emit one alert PER PAGE, so a single dead external URL linked from 400 pages looks like 400 findings in get_crawl_alerts; here it is ONE item with target=the dead URL and pageCount=400. Prefer this over get_crawl_alerts when answering 'what should I fix first' or 'which broken links does this site have'. Items are grouped by (type, affected URL); checks about the page's own text group by that text instead, so TITLE_TOO_LONG yields one item per offending title with target=the title and targetIsSubject=true. Checks naming neither (e.g. TITLE_MISSING) yield one item per type with target=null. Narrow with category (e.g. 'External Links') or type. Ignored alerts are excluded unless includeIgnored=true. Each item's pageUrls list is capped - trust pageCount for reach and use get_crawl_alerts for the full page list.
Inputs: crawlId (required), page, size, type, +4 more.
get_duplicate_code_regionsAInspect
Page through the duplicated code regions of one DUPLICATE_JS_CODE or DUPLICATE_CSS_CODE alert, each with the two source locations, the measured shared bytes, and the code snippet. Use this to read the actual duplicated code: the crawl-wide duplicate-code report carries no snippets at all, because it returns every finding in the crawl at once.
Inputs: alertId (required), page, size.
get_health_scoreBInspect
Get a site's health-score history (one point per crawl).
Inputs: siteId (required).
get_siteCInspect
Get a single site's configuration and metadata within a tenant.
Inputs: siteId (required), tenantId (required).
ignore_alertAInspect
Ignore an alert with a required scope. ALWAYS ask the user which scope they want before calling: current_page (only this URL), all_pages (this issue type across the whole site), route_pattern (pages matching a glob like /blog/*), or target_pattern (every URL the issue is ABOUT that matches a glob - broken links, images - wherever they are linked from). Creates a persistent ignore rule so future crawls keep the issue suppressed.
Inputs: scope (required), alertId (required), routePattern, targetPattern.
list_crawlsBInspect
List crawl runs for a site, newest first.
Inputs: siteId (required).
list_sitesBInspect
List all sites belonging to a tenant.
Inputs: tenantId (required).
list_tenantsAInspect
List the workspaces (tenants) your token can access, with their ids. Call this FIRST - the returned tenant id is the tenantId argument the other tools (list_sites, search, ...) need. Takes no arguments.
Inputs: no named parameters.
recrawl_pagesAInspect
Re-crawl only the pages affected by one finding in a site's most recent completed crawl, then re-run that crawl's analysis and update its health score in place. Use after fixing an issue to verify the fix without paying for a full re-crawl. Name the finding with a selector rather than a URL list where possible: a summary row can cover far more pages than it lists. Requires a WRITE-scoped token and ADMIN or OWNER role, and consumes one crawl credit per page.
Inputs: crawlId (required), selector (required), url, lang, +5 more.
searchAInspect
Search a tenant's sites, pages, and alerts. Returns up to limit ranked results. The caller must be a member of the given tenant.
Inputs: q (required), tenantId (required), limit, activeSiteId.
unignore_alertAInspect
Reopen an ignored alert. Also deletes every ignore rule covering it (page, site-wide, or route-pattern) so the next crawl does not silently re-ignore the issue.
Inputs: alertId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs117 npm46 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.