# DrUrls (remote · drurls.com)

Audit websites for SEO from your AI assistant: scores, issues with fixes, Google indexability

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `drurls.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-drurls-drurls/drurls.md), [page](https://verifymcp.io/servers/com-drurls-drurls/drurls)

## Channel facts

- Endpoint: `https://drurls.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1210 tokens (~110/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the DrUrls MCP server?

DrUrls is a hosted endpoint at https://drurls.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-drurls-drurls": {
      "url": "https://drurls.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-drurls-drurls": {
      "type": "http",
      "url": "https://drurls.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-drurls-drurls]
url = "https://drurls.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-drurls-drurls": {
      "type": "remote",
      "url": "https://drurls.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-drurls-drurls --url 'https://drurls.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-drurls-drurls:
    url: "https://drurls.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-drurls-drurls": {
      "Transport": "http",
      "Url": "https://drurls.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-drurls-drurls -t streamable-http -u 'https://drurls.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-drurls-drurls": {
      "type": "http",
      "url": "https://drurls.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 82, +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.

### 2026-10-27 (score 81, +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.

### 2026-10-25 (score 80, +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.

### 2026-10-23 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 78, 0)

- [security] Tool “free_page_check” rewrote its description, which is the text the model reads
- [security] Tool “check_google_visibility” rewrote its description, which is the text the model reads
- [security] Tool “find_issues” rewrote its description, which is the text the model reads
- [security] Tool “generate_report” rewrote its description, which is the text the model reads
- [security] Tool “get_improvement_plan” rewrote its description, which is the text the model reads
- [security] Tool “get_scan_status” rewrote its description, which is the text the model reads
- [security] Tool “get_site_report” rewrote its description, which is the text the model reads
- [security] Tool “hire_tester” rewrote its description, which is the text the model reads
- [security] Tool “list_sites” rewrote its description, which is the text the model reads
- [security] Tool “list_tester_offers” rewrote its description, which is the text the model reads
- [security] Tool “start_scan” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “hire_tester” reworded the description of “offer_id”

## MCP tools (11)

### `list_tester_offers` (~135 tokens)

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.

### `hire_tester` (~249 tokens)

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.

Input parameters:

- `brief` (string, required): What to test and what would count as a problem. At least 20 characters. Example: 'Check the mobile checkout on iPhone — I think the pay button falls below the fold.'
- `offer_id` (string, required): The offer's id, as listed in the tester catalogue
- `target_url` (string, required): Absolute http(s) URL of the page to test

### `list_sites` (~71 tokens)

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.

### `get_site_report` (~76 tokens)

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.

Input parameters:

- `domain` (string, required): The site's domain, e.g. example.com

### `find_issues` (~93 tokens)

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.

Input parameters:

- `domain` (string): Restrict to one site (optional)
- `severity` (string): Restrict to one severity (optional)

### `check_google_visibility` (~91 tokens)

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.

Input parameters:

- `domain` (string): Restrict to one site (optional)

### `get_improvement_plan` (~80 tokens)

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.

Input parameters:

- `domain` (string): Restrict to one site (optional)

### `start_scan` (~89 tokens)

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.

Input parameters:

- `url` (string, required): The website URL or domain to audit

### `get_scan_status` (~60 tokens)

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.

### `generate_report` (~101 tokens)

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.

Input parameters:

- `domain` (string): One site's domain; omit for the whole-organization report

### `free_page_check` (~99 tokens)

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.

Input parameters:

- `url` (string, required): The page to audit, e.g. https://example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-drurls-drurls/drurls#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 81
- 2026-10-27: 81
- 2026-10-26: 80
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78

## Common questions

### What is the DrUrls MCP server?

DrUrls is an MCP server listed in the public MCP registry as com.drurls/drurls. Audit websites for SEO from your AI assistant: scores, issues with fixes, Google indexability. This page covers its hosted endpoint (https://drurls.com/mcp).

### Is the DrUrls MCP server safe to use?

DrUrls scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DrUrls MCP server expose?

DrUrls exposes 11 tools: list_tester_offers, hire_tester, list_sites, get_site_report, find_issues, and 6 more. Their descriptions and schemas cost roughly 1,144 tokens of context every time the server is loaded.

### Does the DrUrls MCP server require authentication?

Yes. DrUrls asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the DrUrls MCP server still maintained?

DrUrls is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://drurls.com/mcp
- Repository: https://github.com/DrUrls/mcp
- Website: https://drurls.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-drurls-drurls/drurls.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-drurls-drurls/drurls.json
- HTML version of this page: https://verifymcp.io/servers/com-drurls-drurls/drurls