VerifiedDR

io.github.VerifiedDRPublished by GitHub account VerifiedDRv1.0.0Updated Oct 25, 2026

Website authority and AI visibility tools for DR, TrueDR, keywords, backlinks, and partnerships.

The publisher's own server: verified.fyi

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that gives an assistant website authority and AI visibility tools for domain ratings, TrueDR, keywords, backlinks and partnerships.

What you can do
Look up website authority metrics such as DR and TrueDR for domains the assistant is asked about. Research keywords and backlink data tied to a site. Explore partnership information related to a domain. All of this is reached through a hosted endpoint rather than a local package.
When to use it
Useful when you want an assistant to check or compare domain authority, keyword and backlink signals, or partnership data while working on SEO or site visibility questions, without leaving the chat.
Requirements
A remote MCP endpoint reached over streamable HTTP. Authentication is required via OAuth, with an API key sent in the Authorization header, obtained from the provider's dashboard. No local runtime or packages are needed.
Before you install
The server requires an API key sent in the Authorization header; treat it as a secret and check how it is stored in your client. Queries about domains, keywords and backlinks are sent to a third-party service, so consider whether that data is sensitive. Review any usage limits or costs on the provider's site before relying on it.

Installation

In SourceWeft

  1. Open VerifiedDR in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.VerifiedDR%2Fverifieddr/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "verifieddr": {
      "type": "http",
      "url": "https://verifieddr.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Verified integrations