disclosedby, the subprocessor record
REMOTE · DISCLOSEDBY.COM · SCANNED SEP 29
Dated quotes of GDPR art. 28 subprocessor lists: who lists whom, what changed, and when.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1485 tokens (~212/item across 7 items; 7 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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
claude mcp add --transport http com-disclosedby-record 'https://disclosedby.com/api/mcp'
{
"mcpServers": {
"com-disclosedby-record": {
"url": "https://disclosedby.com/api/mcp"
}
}
} {
"servers": {
"com-disclosedby-record": {
"type": "http",
"url": "https://disclosedby.com/api/mcp"
}
}
} [mcp_servers.com-disclosedby-record] url = "https://disclosedby.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-disclosedby-record": {
"type": "remote",
"url": "https://disclosedby.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-disclosedby-record --url 'https://disclosedby.com/api/mcp' --transport streamable-http
mcp_servers:
com-disclosedby-record:
url: "https://disclosedby.com/api/mcp" {
"McpServers": {
"com-disclosedby-record": {
"Transport": "http",
"Url": "https://disclosedby.com/api/mcp"
}
}
} assistant mcp add com-disclosedby-record -t streamable-http -u 'https://disclosedby.com/api/mcp'
{
"mcpServers": {
"com-disclosedby-record": {
"type": "http",
"url": "https://disclosedby.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 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
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
- 24 Sept 26 61
First indexed and scored.
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 29 Sept 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 | 21 Sept 2026 | 20 Dec 2026 | RSA 2048 | SHA256-RSA | ee9f38c4fce3e09e121ed45f15704554 |
| 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. | present | 19718 | 13 | Verified |
| disclosedby.com. | absent | 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 |
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 →
as_of What a list said on a date ~215
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 whose watch is running: this is part of the watch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | A company with a list on this record: its domain (notion.so) or its name (Notion). One company per call. |
| date | string | yes | ISO date, e.g. 2024-01-01. |
No output schema declared.
No examples provided.
changes What changed on a company's list ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | A company with a list on this record: its domain (notion.so) or its name (Notion). One company per call. |
| since | string | – | Optional ISO date; only changes on or after it. |
No output schema declared.
No examples provided.
changes_across Changes across a reader's own list ~168
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 is part of the watch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| since | string | – | Optional ISO date; only changes on or after it. |
No output schema declared.
No examples provided.
in_chain Is a company in your chain ~215
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 second hop 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 whose watch is running: this is part of the watch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | The companies the reader buys from, by domain or name. |
| target | string | yes | The subprocessor to look for. |
No output schema declared.
No examples provided.
list A company's subprocessor 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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | A 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 Who names a subprocessor ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| subprocessor | string | yes | A subprocessor named on at least one list: its name, an alias, or its id here. |
No output schema declared.
No examples provided.
resolve Resolve a name ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A name as printed on a list, or an alias. |
No output schema declared.
No examples provided.
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, what changed, and 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 63 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 7 tools: list, named_by, changes, resolve, as_of, and 2 more. Their descriptions and schemas cost roughly 1,293 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 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.