MCP.so
Sign In

DrUrls MCP ServerVerifiedFeatured

@DrUrls

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Developer Tools

Author

DrUrls

Submitted by

Gauthier Bros

About DrUrls MCP Server

DrUrls audits websites for SEO, and its MCP server lets Claude, ChatGPT, Claude Code, Cursor or VS Code work with those audits directly: list your sites with their latest score and grade, read each issue across SEO, performance, security and accessibility with the fix for each, check what blocks Google from indexing a site, get a ranked improvement plan, compile a report, and start a fresh audit of any public website. Connect: add https://drurls.com/mcp as a remote server and sign in to DrUrls with OAuth (dynamic client registration). Approval creates a key that only works on the MCP server and can be revoked from the DrUrls dashboard. One tool, free_page_check, audits a single public page with no account. Tools: list_sites, get_site_report, find_issues, check_google_visibility, get_scan_status, list_tester_offers, free_page_check (free) - start_scan, get_improvement_plan, generate_report, hire_tester (paid in DrUrls credits; each states its price). Install steps for every client: https://drurls.com/assistants

Connection details

https://drurls.com/mcp

Setup

claude mcp add drurls --transport http https://drurls.com/mcp

DrUrls MCP Server tools

11

Browse the catalogue of tests a real person will run on a real device: mobile UX on a handset, end-to-end checkout, a screen-reader pass by somebody who uses one daily, native-speaker translation review, and more. These cover what reading a page cannot answer — how something feels on a handset, what a screen reader announces, whether a checkout completes on a real phone: what an automated audit cannot measure. Returns each offer with its price in credits, turnaround, and exactly what gets delivered. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.

Places an order for one test from the tester catalogue. A person performs it and returns a recorded walkthrough with a screenshot and the console output of every step, plus their written findings. It suits a specific doubt only a person can resolve; a brief that says what is suspected produces a sharper report. Charges the offer's price at purchase and releases it if no tester accepts within 72 hours. offer_id identifies an offer in the tester catalogue. Cost: set by the offer you choose — the tester catalogue states each offer's price in credits, its turnaround, and exactly what is delivered. Charged when the order is placed and released if no tester accepts within 72 hours, or if the tester who accepted misses the offer's turnaround. Rate limit: 100 requests/minute per API key.

List every site in the user's organization with its latest completed audit: SEO score, grade, issues found, pages crawled, when it was last scanned, and whether a scan is running right now. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.

Deep-dive one site: latest audit score, issue counts by severity, the most frequent issue types with counts, and social-network presence. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.

Search open issues across all sites (or one site). Returns issue groups: site, issue type, severity, how many pages are affected, and an example page. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.

Check Google indexability for all sites (or one): noindex tags, robots blocks, sitemap errors, canonical problems, redirect chains and broken internal links found in the last crawl. Explains per site whether anything blocks indexing. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.

The highest-impact actions to improve quality right now, ranked by severity and how many pages each fix touches, with concrete how-to-fix guidance. Cost: 2 credits per call, charged only if the call succeeds. Rate limit: 100 requests/minute per API key.

Launch a fresh audit of a website. Creates the site in the org if it doesn't exist yet. Enforces the user's plan quota — if the quota is used up it explains that instead of scanning. Cost: 1 credit per call, charged only if the call succeeds. Rate limit: 100 requests/minute per API key.

What is running right now and what finished recently: every in-flight scan plus the last 10 completed/failed ones with scores and errors. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.

Compile a full SEO report — for one site (score, issues by severity, top issue types, Google visibility, social presence, ranked fix plan) or the whole organization (per-site scores, visibility verdicts, top cross-site actions). Cost: 2 credits per call, charged only if the call succeeds. Rate limit: 100 requests/minute per API key.

Free single-page SEO/health audit of any public URL — no API key, no account. Returns the same score, grade, categories and issues as the product's free check, plus an `upgrade` field describing what the authenticated tools add. Rate limited per caller (3/day). Whole-site crawls, history and tasks need a DrUrls account.

Overview

What is DrUrls?

DrUrls is an SEO audit tool. Paste any URL into the free check at https://drurls.com/check and get a health score, a grade, and every issue it found across SEO, performance, security and accessibility, each with the fix, plus a Google search preview. A free account audits the rest of a site, keeps every audit so runs can be compared, and ranks issues by how many pages each fix touches.

What the MCP server does

Connect https://drurls.com/mcp and your assistant can:

  • list your sites with their latest score and grade (list_sites)
  • read one site's audit: issues by severity, top issue types (get_site_report)
  • find open issues across sites, by severity, with an example page (find_issues)
  • check what blocks Google from indexing a site (check_google_visibility)
  • get the highest-impact fixes, ranked by pages touched (get_improvement_plan)
  • compile a full report for one site or the whole organization (generate_report)
  • start a fresh audit and follow its progress (start_scan, get_scan_status)
  • audit a single public page without an account (free_page_check)
  • order a human test on a real device (list_tester_offers, hire_tester)

Reading your data is free; paid tools are billed in DrUrls credits and each states its price in its description.

Connect

ClientHow
Claude (claude.ai, Desktop)Settings → Connectors → Add custom connector → https://drurls.com/mcp
Claude Codeclaude mcp add --transport http drurls https://drurls.com/mcp, then /mcp to sign in
Cursor{ "mcpServers": { "drurls": { "url": "https://drurls.com/mcp" } } }
VS Code{ "servers": { "drurls": { "type": "http", "url": "https://drurls.com/mcp" } } }

Authentication is OAuth 2.1 with dynamic client registration: the client opens DrUrls, you sign in (Google or GitHub) and approve. Approval creates a key that only works on the MCP server, with no team or billing rights, revocable any time. An API key in an Authorization: Bearer header also works.

Full steps: https://drurls.com/assistants

Frequently asked questions

1

What is the DrUrls remote MCP server?

The DrUrls remote MCP server is a hosted Model Context Protocol endpoint at https://drurls.com/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the DrUrls MCP server?

Add the endpoint https://drurls.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the DrUrls MCP server require authentication?

Yes. DrUrls uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the DrUrls MCP server use?

DrUrls exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments