VerifiedDR
REMOTE · VERIFIEDDR.COM · SCANNED SEP 20
Website authority and AI visibility tools for DR, TrueDR, keywords, backlinks, and partnerships.
Available components
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the VerifiedDR MCP server?
VerifiedDR is a hosted endpoint at https://verifieddr.com/api/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.
remote · verifieddr.com
claude mcp add --transport http verifieddr-verifieddr 'https://verifieddr.com/api/mcp'
{
"mcpServers": {
"verifieddr-verifieddr": {
"url": "https://verifieddr.com/api/mcp"
}
}
} {
"servers": {
"verifieddr-verifieddr": {
"type": "http",
"url": "https://verifieddr.com/api/mcp"
}
}
} [mcp_servers.verifieddr-verifieddr] url = "https://verifieddr.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"verifieddr-verifieddr": {
"type": "remote",
"url": "https://verifieddr.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add verifieddr-verifieddr --url 'https://verifieddr.com/api/mcp' --transport streamable-http
mcp_servers:
verifieddr-verifieddr:
url: "https://verifieddr.com/api/mcp" {
"McpServers": {
"verifieddr-verifieddr": {
"Transport": "http",
"Url": "https://verifieddr.com/api/mcp"
}
}
} assistant mcp add verifieddr-verifieddr -t streamable-http -u 'https://verifieddr.com/api/mcp'
{
"mcpServers": {
"verifieddr-verifieddr": {
"type": "http",
"url": "https://verifieddr.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Sept 26 +13
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Transport: fail → unverified ▼ security
- Authorization: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 3 Sept 26 −13
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 19 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “account_usage” rewrote its description, which is the text the model reads security
- Tool “run_ai_visibility_scan” rewrote its description, which is the text the model reads security
- 18 Aug 26 0
- “propose_link_exchange” added an optional parameter “destinationUrl” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 14 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “find_link_exchanges” reworded the description of “minDr” cosmetic
- “find_sites” reworded the description of “minDr” cosmetic
- 13 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_ai_visibility” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://verifieddr.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=verifieddr.com | CN=WE1,O=Google Trust Services,C=US | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2fcfb21203f65a381315ba2c38041c06 |
| SANs: verifieddr.com, *.verifieddr.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of verifieddr.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| verifieddr.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://verifieddr.com/.well-known/oauth-protected-resource/api/mcp", scope="verifieddr"
Bearer resource_metadata="https://verifieddr.com/.well-known/oauth-protected-resource/api/mcp", scope="verifieddr"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self'; object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer resource_metadata="https://verifieddr.com/.well-known/oauth-protected-resource/api/mcp", scope="verifieddr" |
Protected resource metadata
| Document | https://verifieddr.com/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://verifieddr.com/api/mcp |
| Authorisation server | https://verifieddr.com/api/auth |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verifieddr.com/api/mcp | Auth required | 401 | |
| http (plaintext) | http://verifieddr.com/api/mcp | HTTPS enforced | 301 | https://verifieddr.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
monitor_sites Monitor your sites ~76
Authority watch across your sites: weekly (or daily) change digest with traffic validation and spam/trust alerts. Optionally restrict to one site.
| Name | Type | Req | Description |
|---|---|---|---|
| daily | boolean | – | Use the daily cadence instead of weekly. |
| site | string | – | One of your websites, as a slug or hostname (e.g. example.com). Optional. |
No output schema declared.
No examples provided.
propose_link_exchange Propose a link exchange ~163
Preview or send a one-link-each editorial exchange proposal as the account owner. SENDS REAL EMAIL when dryRun is false. Always preview first and get the user's approval before sending. A dry run can generate the standard proposal when subject and message are omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| destinationUrl | string | – | Page on your verified site that the partner should link to. Required when sending; optional for a dry run. |
| dryRun | boolean | – | Preview without sending. Default false. |
| message | string | – | Email body. |
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
| subject | string | – | Email subject. |
| target | string | yes | The candidate's slug or domain from find_link_exchanges. |
No output schema declared.
No examples provided.
refresh_tracked_keyword Refresh a keyword ~57
Re-snapshot a saved keyword target's difficulty.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Target id from list_tracked_keywords. |
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
remove_ai_visibility_prompt Remove a tracked question ~56
Delete one tracked question by its prompt id.
| Name | Type | Req | Description |
|---|---|---|---|
| promptId | string | yes | Prompt id from get_ai_visibility. |
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
remove_tracked_keyword Untrack a keyword ~53
Remove a tracked keyword target.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Target id from list_tracked_keywords. |
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
reorder_ai_visibility_prompts Reorder tracked questions ~65
Reorder the tracked questions; pass every prompt id in the new order.
| Name | Type | Req | Description |
|---|---|---|---|
| promptIds | array | yes | All prompt ids, in the new order. |
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
reset_ai_visibility_prompts Reset tracked questions ~61
Throw away the current question set and reseed from the site's keywords. Paid plans only. Destructive: the old questions are gone.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
run_ai_visibility_scan Run a visibility scan ~74
Ask the tracked questions across AI engines now. Paid plans use one account-wide monthly search budget, with at most one run per site per week. This spends real vendor budget, so check account_usage first.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
run_growth_plan Generate growth plan ~59
Generate a fresh growth plan. Paid plans only. Progress on unchanged tasks carries over, so a re-run never reopens finished work.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
run_gsc_audit Run GSC index audit ~56
Run a fresh index audit. Spends real GSC URL Inspection quota; 12h cooldown between runs.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
set_ai_visibility_prompt_location Re-target a question ~98
Pin one tracked question to a country market. Paid plans only.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | Target market for the question: "global" (default) or a 2-letter ISO country code like us, gb, de, nl, fr. |
| promptId | string | yes | Prompt id from get_ai_visibility. |
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
submit_site Submit a site ~214
List a new website on VerifiedDR, owned by your account. Use the primary domain (example.com, not blog.example.com). Owned submits count against the free-tier unverified-site cap.
| Name | Type | Req | Description |
|---|---|---|---|
| anonymous | boolean | – | List the site without tying it to your account: it never shows up in your dashboard and you get no owner emails about it. Use it for sites you research or list on someone else's behalf. Anonymous sub… |
| categories | array | – | Up to 3 values from list_categories. |
| description | string | – | Short description, max 240 chars. |
| siteCheck | boolean | – | Also run the site reality check (shell/PBN/spam heuristics) at submit time; fetch the stored report later with check_site. |
| title | string | – | Display title, 1-40 chars. |
| url | string | yes | The site's primary domain or URL, e.g. example.com. |
| xHandle | string | – | X/Twitter handle, e.g. @acme. |
No output schema declared.
No examples provided.
update_growth_task Update growth task ~65
Move one growth task's status after executing it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task id from get_growth_plan. |
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
| status | string | yes | The new status. |
No output schema declared.
No examples provided.
verify_site Verify badge ~60
Fetch one of your sites and check the VerifiedDR badge is embedded. Side effect: marks the site verified or unverified based on the result.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | One of your websites, as a slug or hostname (e.g. example.com). |
No output schema declared.
No examples provided.
What is the VerifiedDR MCP server?
VerifiedDR is an MCP server listed in the public MCP registry as io.github.VerifiedDR/verifieddr. Website authority and AI visibility tools for DR, TrueDR, keywords, backlinks, and partnerships. This page covers its hosted endpoint (https://verifieddr.com/api/mcp).
Is the VerifiedDR MCP server safe to use?
VerifiedDR scores 38 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 VerifiedDR MCP server expose?
VerifiedDR exposes 64 tools: account_usage, list_categories, list_sites, submit_site, get_site, and 59 more. Their descriptions and schemas cost roughly 4,466 tokens of context every time the server is loaded.
Does the VerifiedDR MCP server require authentication?
Yes. VerifiedDR 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 VerifiedDR MCP server still maintained?
VerifiedDR is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.