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

mirror-ai-citability

https://mcp.danielsdesignstudio.com

Registry code: 366151abf53658ae

api record

Mirror is the Brand Discovery Intelligence system by Daniels AI Design Studio (Stowe, Vermont). It measures whether a brand can be found, read, cited and called by AI — but that measurement is delivered by a person, not by this endpoint. THIS SERVER HAS ONE PUBLIC TOOL: `request_record`. It requests a Brand Discovery Record — the human-approved source of truth a brand publishes for AI assistants and agents. It is free, it publishes nothing, and a person replies. Nothing here returns a Reflection, a score, or an index: `reflect`, `score`, `aci55` and `mcp_engine` left the public surface on…

endpoint
https://mcp.danielsdesignstudio.com/mcp
protocol
streamable-http ·2025-06-18
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 mirror-ai-citability live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is mirror-ai-citability free to use?
Not measured yet.
What tools does mirror-ai-citability have?
1 tool: request_record.
Is mirror-ai-citability 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
99.4%

90 days 99.2%· all time 99.2%

latency
1,797ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 397 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • request a brand discovery record for ai assistants
  • ask a person to assess a brand's ai visibility
takes → gives
text → text
tools
1 sends messages
_ 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

_ what it can do 1 tools
1 never probed 0 of 1 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.

  • request_record sends messages unknown never probed

    Request a Brand Discovery Record — the human-approved source of truth a brand provides to AI assistants and agents, maintained by Mirror. A Record is a machine-readable reference page, hosted by Mirror, stating a brand's verified facts with schema.org structured data and citations, and linking to the brand's own site as the canonical source. It is what a brand PUBLISHES so AI can find, read and cite it: Mirror measures, the Record responds. This is the one public tool of the Mirror switchboard; the measurement itself (a full Brand Reflection) is delivered by a person on request. IMPORTANT — this tool creates a REQUEST, not a Record. Nothing is published by calling it. Automated validation (Signal Input) runs immediately and its results are returned to you. Every Brand Discovery Record is reviewed by Daniels AI and approved by the organization it represents before publication. No autonomous process publishes a brand's machine-readable truth. Fill the fields below with verified, citable facts only. The Record specification is versioned; this tool reports the version it validated against.

    mcp-tool

    {
      "type": "object",
      "required": [
        "brand_name",
        "official_url",
        "tagline",
        "description",
        "relationship"
      ],
      "properties": {
        "social": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Official profile URLs."
        },
        "address": {
          "type": "object",
          "properties": {
            "city": {
              "type": "string"
            },
            "postal": {
              "type": "string"
            },
            "region": {
              "type": "string"
            },
            "street": {
              "type": "string"
            },
            "country": {
              "type": "string"
            }
          },
          "description": "{street, city, region, postal, country}"
        },
        "history": {
          "type": "string",
          "description": "Founding and lineage, factual."
        },
        "tagline": {
          "type": "string",
          "description": "One plain line: what it is and where."
        },
        "overview": {
          "type": "string",
          "description": "Short factual prose — what the brand is."
        },
        "citations": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "title",
              "publisher",
              "url"
            ],
            "properties": {
              "url": {
                "type": "string"
              },
              "title": {
                "type": "string"
              },
              "publisher": {
                "type": "string"
              }
            }
          },
          "description": "Optional. Any authoritative sources you already have, ideally 3 from 3 different domains — [{title, publisher, url}]. Supply what exists; Daniels sources citations as part of the engagement, so having none is not a barrier."
        },
        "brand_name": {
          "type": "string",
          "description": "Exact public name of the brand."
        },
        "phone_e164": {
          "type": "string",
          "description": "E.164 format, e.g. +1-802-760-4653"
        },
        "description": {
          "type": "string",
          "description": "1-2 factual sentences, ~160 characters. No marketing claims."
        },
        "positioning": {
          "type": "string",
          "description": "The most clarifying fact: category, who it serves, and what it is NOT."
        },
        "recognition": {
          "type": "string",
          "description": "Awards or coverage, each traceable to a citation."
        },
        "schema_type": {
          "type": "string",
          "description": "Optional. schema.org @type — e.g. GolfCourse, Restaurant, LodgingBusiness, Organization. Omit if unsure; Daniels sets the type at Signal Review."
        },
        "official_url": {
          "type": "string",
          "description": "The brand's OWN official website (canonical). Must be the brand's domain — never Mirror's."
        },
        "relationship": {
          "enum": [
            "represents_brand",
            "agent_for_brand",
            "third_party",
            "testing",
            "other"
          ],
          "type": "string",
          "description": "REQUIRED. Who is asking, and on whose behalf. Signal Input fails without it. Only a request from someone representing the brand can become an authorized Record. If you are trying this tool out, say \"testing\" — it is filed as a test, you still get the full Signal Input validation, and it never enters the review queue."
        },
        "founding_year": {
          "type": "string",
          "description": "Year established (YYYY)."
        },
        "public_access": {
          "type": "boolean",
          "description": "Is it open to the public? The confusion-killer field."
        },
        "differentiator": {
          "type": "string",
          "description": "The notable, verifiable thing."
        },
        "requester_note": {
          "type": "string",
          "description": "Why this request is being made."
        },
        "requester_contact": {
          "type": "string",
          "description": "REQUIRED. A working email for Signal Review and Signal Approval follow-up. Example/reserved domains (example.com, .test, .invalid) fail Signal Input. Without it a Record cannot be authorized."
        }
      }
    }
    arguments 134 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 366151abf53658ae.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/366151abf53658ae/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/366151abf53658ae/badge.svg)](https://brick.blue/agent/366151abf53658ae?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
50%

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.