Get a New Website Verified

This workflow takes a website from unlisted to verified in one pass. The agent picks the categories that make it discoverable, submits the listing, hands you the badge snippet to embed, verifies the embed, and reads the first DR, TrueDR, and trust evidence so you have a baseline to measure every later change against. Prefer to keep the badge off the page? Use a DNS TXT record or verification file from the dashboard instead.

Paste this into Claude, Codex, Cursor, ChatGPT, or another coding agent. The website, the expected output, and the approval boundary are already written in. First run? Complete the one-time setup; your agent can handle that too.

This is the sequence the agent follows. It reads data on its own. You approve each send or change.

1. 01

   Pick categories

   Run list_categories for the values a listing accepts (up to three per website).

2. 02

   List the website

   Run submit_site with the primary website, a title, and a short description.

3. 03

   Grab the badge

   Run get_badge_snippets for ready-to-paste badge and embed code, then add it to the website.

4. 04

   Verify

   Run verify_site after you add the badge. It checks the badge and verifies the site. Any account can also use a DNS TXT record or verification file in the dashboard.

5. 05

   Read the baseline

   Run lookup_site for the first DR, TrueDR, and trust evidence to measure everything against.

The exact MCP tool calls behind the prompt. Your agent runs these against the verifieddr server; the ones that send anything still stop for your approval.

# 1. Valid category values (up to 3 per website)list_categories { } # 2. List the website on VerifiedDRsubmit_site { url: "yourwebsite.com", title: "VerifiedDR", categories: ["saas"] } # 3. Grab the badge and embed snippetsget_badge_snippets { site: "yourwebsite.com" } # 4. Check the badge is live; marks the site verifiedverify_site { site: "yourwebsite.com" } # 5. Your opening DR, TrueDR, and trust evidencelookup_site { site: "yourwebsite.com" }