_ registry / mcp streamable-http · checked 4h ago

mcp-launch-audit

https://brand-checker.appwrite.network

Registry code: 33d0e2ab7ad851ad

api record

Use check_brand_availability, audit_email_deliverability, audit_ai_search_visibility, or full_launch_readiness_audit to run live pre-launch technical audits on domains and candidate startup names.

endpoint
https://brand-checker.appwrite.network/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mcp-launch-audit live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is mcp-launch-audit free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcp-launch-audit have?
4 tools: audit_email_deliverability, audit_ai_search_visibility, check_brand_availability, full_launch_readiness_audit.
Is mcp-launch-audit safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
569ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • audit_email_deliverability unknown never probed

    Audit a sending domain's email authentication and inbox placement health: resolves MX servers, recursively counts SPF DNS lookups against the RFC 7208 10-lookup hard limit, probes 18 standard ESP DKIM selectors, validates DMARC policy enforcement, checks MTA-STS/BIMI, and tests the primary mail IP against major DNSBL blacklists. Use this tool for diagnosing why transactional or marketing emails land in spam; use `full_launch_readiness_audit` when also checking brand conflicts and AI search crawlers.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Target sending domain to inspect (e.g. 'stripe.com' or 'acme.io')."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • audit_ai_search_visibility unknown 4h ago

    Inspect a live website URL for Generative Engine Optimization (GEO) and AI assistant citation readiness: verifies whether `/robots.txt` allows 8 major AI search crawlers (OAI-SearchBot, GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot), validates `/llms.txt` and `/llms-full.txt` Markdown indexes, and extracts Schema.org `application/ld+json` entities. Use this tool for AI SEO and `/llms.txt` checks on a single URL; use `full_launch_readiness_audit` when running a complete pre-launch sweep.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public website URL or domain to inspect (e.g. 'https://cal.com' or 'linear.app')."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_brand_availability unknown 4h ago

    Check a single candidate startup or product name across top TLDs (.com, .io, .ai, .dev via live RDAP/DNS), public developer handles (GitHub, npm, PyPI, Bluesky), and live USPTO trademark records, returning a 0-100 Brand Readiness Score. Use this tool when evaluating candidate names before registering a domain; use `full_launch_readiness_audit` instead when auditing an already-chosen domain across brand, email DNS, and AI search visibility together.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Candidate brand or product name to screen (alphanumeric label, e.g. 'linear' or 'resend')."
        },
        "tlds": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "default": [
            "com",
            "io",
            "ai",
            "dev"
          ],
          "description": "Optional list of domain extensions without leading dots (defaults to ['com', 'io', 'ai', 'dev'], max 6)."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • full_launch_readiness_audit unknown 4h ago

    Run a comprehensive, parallel 3-pillar pre-launch audit on a production domain — combining brand/trademark conflict screening, SPF/DKIM/DMARC/DNSBL email deliverability verification, and AI search (`robots.txt`, `/llms.txt`, Schema.org JSON-LD) readiness into one unified 0-100 Launch Scorecard and prioritized remediation checklist. Reach for this tool when preparing a domain for launch or diagnosing overall technical growth readiness; use the specialized single-pillar tools when iterating on just one area.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Primary production domain to audit (e.g. 'resend.com' or 'acme.io')."
        },
        "brandName": {
          "type": "string",
          "description": "Optional brand label if different from the domain's second-level label."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 33d0e2ab7ad851ad.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/33d0e2ab7ad851ad/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/33d0e2ab7ad851ad/badge.svg)](https://brick.blue/agent/33d0e2ab7ad851ad?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.