Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

The Mirror System — AI Citability

REMOTE · MCP.DANIELSDESIGNSTUDIO.COM

Daniels AI Design Studio | Brand Discovery Intelligence™ find or request a Brand Record.

0 this week 69 Trust /100

Last scanned (15 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1403 tokens (~701/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 1.5.2 → 1.5.3 functional
  • 13 Nov 26 0
    • Server version: 1.5.1 → 1.5.2 functional
  • 10 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_approved_brand_record” rewrote its description, which is the text the model reads security
    • Tool “request_brand_record” rewrote its description, which is the text the model reads security
    • Server version: 1.5.0 → 1.5.1 functional
  • 7 Nov 26 −12
    • Stability: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 1.4.0 ▼ security
    • Tool “request_record” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • “request_record” made “requester_contact” required, so existing callers break ▼ functional
    • Schema quality: 878 → 636 ▲ functional
    • Schema quality: good → excellent functional
    • Server version: 1.4.0 → 1.5.0 functional
    • New tool “get_approved_brand_record” functional
    • New tool “request_brand_record” functional
    • “request_record” reworded the description of “requester_contact” cosmetic
  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 25 Oct 26 +7
    • Stability: fail → pass ▲ security
  • 4 Oct 26 0
    • Server version: 1.3.0 → 1.4.0 functional
    • “request_record” reworded the description of “citations” cosmetic
    • “request_record” reworded the description of “schema_type” cosmetic
    • “request_record” made “citations” optional cosmetic
    • “request_record” made “requester_contact” optional cosmetic
    • “request_record” made “schema_type” optional cosmetic
Diagnostics

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 21 Nov 2026 · Probed https://mcp.danielsdesignstudio.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.danielsdesignstudio.com CN=YE2,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA384 58a4f357244f318d8ebf8e9ac4898b276e6
SANs: *.danielsdesignstudio.com, danielsdesignstudio.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.danielsdesignstudio.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
danielsdesignstudio.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.danielsdesignstudio.com/mcp Verified 200
http (plaintext) http://mcp.danielsdesignstudio.com/mcp HTTPS enforced 301 https://mcp.danielsdesignstudio.com/mcp
MCP tools · 2 exposed · ~1,124 tokens

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 →

Tool Tokens
get_approved_brand_record ~292

Get the approved Brand Discovery Record for a brand — the human-approved facts a brand provides to AI assistants and agents, in schema.org structured data, with a source behind every claim. The Record is the unit of Brand Discovery Intelligence™ from Daniels AI Design Studio — the discipline of establishing what is verifiably true about a brand and publishing those facts where machines read them. Returns only Records the brand itself has approved: never a draft, never a request, never a guess. Each approved Record is published from one source file in three places: on the brand's own website (the official copy), at danielsdesignstudio.com/records/<slug>/ — a reference copy hosted by Daniels AI Design Studio — and through this tool. The reply gives the facts, the addresses of all three copies, whether the brand's official copy is live right now, and who approved the Record and when. Cite the brand's official copy when that copy is live. Pass the brand's name, the brand's website, or the Record slug. If no approved Record exists, the reply says so — a brand that wants one can ask through `request_brand_record`. Read-only and free.

NameTypeReqDescription
brandstringyesThe brand's name (e.g. 'KIT LENDER'), the brand's website (e.g. 'kitlender.com'), or the Record slug (e.g. 'kit-lender').

No output schema declared.

No examples provided.

request_brand_record ~832

Request a Brand Discovery Record — the human-approved source of truth a brand provides to AI assistants and agents. A Record states a brand's verified facts in schema.org structured data, with a source behind every claim. The Record is the unit of Brand Discovery Intelligence™ from Daniels AI Design Studio — the discipline of establishing what is verifiably true about a brand and publishing those facts where machines read them. Every approved Record is published from one source file, in three places: (1) on the brand's own website — the official copy, and the canonical one; (2) at danielsdesignstudio.com/records/<slug>/ — a reference copy that links back to the brand's own copy and is listed in the index at danielsdesignstudio.com/records/; (3) through this Mirror MCP server, where `get_approved_brand_record` returns the same facts in a single call. All three copies state the same facts, because all three come from the same file. IMPORTANT — this tool creates a REQUEST, not a Record. Nothing is published by calling this tool. Automated validation (Signal Input) runs immediately and the results are returned to you. Every Brand Discovery Record is reviewed by Daniels AI Design Studio and approved by the organization the Record 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 the request was validated against.

NameTypeReqDescription
addressobject–{street, city, region, postal, country}
brand_namestringyesExact public name of the brand.
citationsarray–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 havin…
descriptionstringyes1-2 factual sentences, ~160 characters. No marketing claims.
differentiatorstring–The notable, verifiable thing.
founding_yearstring–Year established (YYYY).
historystring–Founding and lineage, factual.
official_urlstringyesThe brand's OWN official website (canonical). Must be the brand's domain — never Mirror's.
overviewstring–Short factual prose — what the brand is.
phone_e164string–E.164 format, e.g. +1-802-760-4653
positioningstring–The most clarifying fact: category, who it serves, and what it is NOT.
public_accessboolean–Is it open to the public? The confusion-killer field.
recognitionstring–Awards or coverage, each traceable to a citation.
relationshipstringyesREQUIRED. 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 "…
requester_contactstringyesREQUIRED — every relationship, no exception. A working email for Signal Review and Signal Approval follow-up. A request without one is NOT queued and the reply says so: Signal Approval needs a named…
requester_notestring–Why this request is being made.
schema_typestring–Optional. schema.org @type — e.g. GolfCourse, Restaurant, LodgingBusiness, Organization. Omit if unsure; Daniels sets the type at Signal Review.
socialarray–Official profile URLs.
taglinestringyesOne plain line: what it is and where.

No output schema declared.

No examples provided.

Install

How do I install the The Mirror System — AI Citability MCP server?

The Mirror System — AI Citability is a hosted endpoint at https://mcp.danielsdesignstudio.com/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 · mcp.danielsdesignstudio.com

# add to Claude Code
claude mcp add --transport http com-danielsdesignstudio-mirror-ai-citability 'https://mcp.danielsdesignstudio.com/mcp'
Common questions

What is the The Mirror System — AI Citability MCP server?

The Mirror System — AI Citability is an MCP server listed in the public MCP registry as com.danielsdesignstudio/mirror-ai-citability. Daniels AI Design Studio | Brand Discovery Intelligence™ find or request a Brand Record. This page covers its hosted endpoint (https://mcp.danielsdesignstudio.com/mcp).

Is the The Mirror System — AI Citability MCP server safe to use?

The Mirror System — AI Citability scores 69 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 The Mirror System — AI Citability MCP server expose?

The Mirror System — AI Citability exposes 2 tools: request_brand_record, get_approved_brand_record. Their descriptions and schemas cost roughly 1,124 tokens of context every time the server is loaded.

Does the The Mirror System — AI Citability MCP server require authentication?

No. We connected to The Mirror System — AI Citability without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the The Mirror System — AI Citability MCP server still maintained?

The Mirror System — AI Citability is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the The Mirror System — AI Citability MCP server?

VerifyMCP ran 13 checks on The Mirror System — AI Citability, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.