disclosedby MCP server

• Registry namecom.disclosedby/recordverified in the MCP registry

The registry name sits under disclosedby.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools7
• Server calls itselfdisclosedby
• Server version2
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 232 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score94 of 100answers 100 · definitions 81 · context 100 · connects 100
• Answered100% of days15 of 15 daily checks
• Median first answer294 ms
• Space in an agent's context≈ 1,680 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsB · 81 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 1 of 7
• Not saying whether it only reads or can destroy: 7 of 7

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list

  What one company's published subprocessor list says, as this record holds it: every row quoted as the company wrote it, with the purpose and location it printed, when the row was first and last seen here, the source page and the date it…

• named_by

  Which companies name one subprocessor on their published lists, with the name each company prints for it, when it was first seen on that list and when the list was read. One subprocessor per call. Free to read, cite and link. Every row is…

• changes

  The dated changes to one company's list, each derived from two readings of that list and carrying both. A change is what the page said on one date against what it said on another; it is never a claim about when a company began or ended a…

• resolve

  What company a name on a list refers to, through this record's hand-checked identity table. Exact match only, never a guess: an unknown name comes back unresolved, which is an answer. Free to read, cite and link. Every row is a dated…

• as_of

  What one company's list said on a given date, from the reading this record holds nearest before it, with that reading's own date, its web-archive capture where there is one, its source and its digest. Says so when the date is earlier than…

• in_chain

  Given the companies a reader buys from, every path from that list to one subprocessor: named directly, or named by a company whose own list names it (a fourth party, or sub-subprocessor). A second hop is a different relationship, quoted…

• changes_across

  The dated changes to the lists of several companies at once, each carrying the two readings it came from. The same facts as `changes`, gathered for one reader's own list of companies. Needs a key on an account whose watch is running: this…