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.

disclosedby, the subprocessor record

REMOTE · DISCLOSEDBY.COM

Dated quotes of GDPR art. 28 subprocessor lists: who lists whom, fourth parties, what changed, when.

Available components

0 this week 74 Trust /100

Last scanned (14 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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 Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1842 tokens (~230/item across 8 items; 8 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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 (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Tool “as_of” rewrote its description, which is the text the model reads security
    • Tool “changes_across” rewrote its description, which is the text the model reads security
    • Tool “in_chain” rewrote its description, which is the text the model reads security
    • Schema quality: 1584 → 1842 ▼ functional
    • New tool “check” functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Tool “in_chain” rewrote its description, which is the text the model reads security
    • Stability: pass → 0.97 functional
    • “in_chain” added an optional parameter “on” cosmetic
    • “in_chain” reworded the description of “target” cosmetic
    • Tool “in_chain” changed its title: Do your vendors use a company → Walk your vendors to a company or a country cosmetic
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +39
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Tool coverage: unverified → 100 ▲ functional
  • 3 Nov 26 −39
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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://disclosedby.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=disclosedby.com CN=WR3,O=Google Trust Services,C=US 15 Nov 2026 13 Feb 2027 RSA 2048 SHA256-RSA 6263cb2904d6e64a101f9feb1327d17a
SANs: disclosedby.com, *.disclosedby.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of disclosedby.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
disclosedby.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
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://disclosedby.com/api/mcp Verified 200
http (plaintext) http://disclosedby.com/api/mcp HTTPS enforced 301 https://disclosedby.com:443/api/mcp
MCP tools · 8 exposed · ~1,650 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
as_of ~216

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 the first reading held. Needs a key on an account with Follow your vendors running: this is part of the subscription on disclosedby.com. Free to read, cite and link. Every row is a dated quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

NameTypeReqDescription
companystringyesA company with a list on this record: its domain (notion.so) or its name (Notion). One company per call.
datestringyesISO date, e.g. 2024-01-01.

No output schema declared.

No examples provided.

changes ~223

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 relationship. `printed_differently` marks an entry the list printed in other words with the same companies in the same countries (a name, a location's wording, the list's date line). Free to read, cite and link. Every row is a dated quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

NameTypeReqDescription
companystringyesA company with a list on this record: its domain (notion.so) or its name (Notion). One company per call.
sincestring–Optional ISO date; only changes on or after it.

No output schema declared.

No examples provided.

changes_across ~169

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 with Follow your vendors running: this is part of the subscription on disclosedby.com. Free to read, cite and link. Every row is a dated quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

NameTypeReqDescription
companiesarrayyes–
sincestring–Optional ISO date; only changes on or after it.

No output schema declared.

No examples provided.

check ~255

Given the companies a reader buys from, which of their own published lists name one company, or a company headquartered in a country, on their latest version: in the list's own words, with when it was first seen here and the day the list was checked. Past the first step it answers in counts only: how many of the companies lead there through a company they name, and how many steps held here have ended. The same answer as the check on disclosedby.com. Which company is in between, and since when each step held, is `in_chain`. Names that matched nothing come back beside the answer. It says who to ask, never who is harmed. Free to read, cite and link. Every row is a dated quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

NameTypeReqDescription
companiesarrayyesThe companies the reader buys from, by domain or name.
targetstringyesThe company to look for, or a country by name or code.

No output schema declared.

No examples provided.

in_chain ~315

Given the companies a reader buys from, every path from that list to one company, or to a country: named directly, or named on the own list of a company they name (a fourth party, or sub-subprocessor). Each step is a list's own row, with its purpose and location as written, and the versions each run of it started and ended between; on a date, the versions held on or before it. A country is reached through hand-checked headquarters, of the company or of its group. A second step is a different relationship, quoted from a different page. Names that matched nothing, companies with no list read and rows that did not resolve come back beside the paths. It says who to ask, never who is harmed. Needs a key on an account with Follow your vendors running: this is part of the subscription on disclosedby.com. Free to read, cite and link. Every row is a dated quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

NameTypeReqDescription
companiesarrayyesThe companies the reader buys from, by domain or name.
onstring–Optional ISO date: the walk as the lists held it then.
targetstringyesThe company to look for, or a country by name or code.

No output schema declared.

No examples provided.

list ~180

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 was read. Says so when no list for that company has been read. Free to read, cite and link. Every row is a dated quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

NameTypeReqDescription
companystringyesA company with a list on this record: its domain (notion.so) or its name (Notion). One company per call.

No output schema declared.

No examples provided.

named_by ~152

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 a dated quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

NameTypeReqDescription
subprocessorstringyesA subprocessor named on at least one list: its name, an alias, or its id here.

No output schema declared.

No examples provided.

resolve ~140

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 quote of a company's own published page: cite the page and the read date. The compilation is protected: extraction or re-use of a substantial part is not permitted, and it may never be compiled into a lead list, a prospecting feed or a sales tool. A key is one reader's own use.

NameTypeReqDescription
namestringyesA name as printed on a list, or an alias.

No output schema declared.

No examples provided.

Install

How do I install the disclosedby, the subprocessor record MCP server?

disclosedby, the subprocessor record is a hosted endpoint at https://disclosedby.com/api/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 · disclosedby.com

# add to Claude Code
claude mcp add --transport http com-disclosedby-record 'https://disclosedby.com/api/mcp'
Common questions

What is the disclosedby, the subprocessor record MCP server?

disclosedby, the subprocessor record is an MCP server listed in the public MCP registry as com.disclosedby/record. Dated quotes of GDPR art. 28 subprocessor lists: who lists whom, fourth parties, what changed, when. This page covers its hosted endpoint (https://disclosedby.com/api/mcp).

Is the disclosedby, the subprocessor record MCP server safe to use?

disclosedby, the subprocessor record scores 74 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 disclosedby, the subprocessor record MCP server expose?

disclosedby, the subprocessor record exposes 8 tools: list, named_by, changes, resolve, check, and 3 more. Their descriptions and schemas cost roughly 1,650 tokens of context every time the server is loaded.

Does the disclosedby, the subprocessor record MCP server require authentication?

No. We connected to disclosedby, the subprocessor record without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the disclosedby, the subprocessor record MCP server still maintained?

disclosedby, the subprocessor record 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 disclosedby, the subprocessor record MCP server?

VerifyMCP ran 12 checks on disclosedby, the subprocessor record, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about disclosedby, the subprocessor record: Authorization. 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.