mcpbeat Sign in

disclosedby, the subprocessor record MCP Server

by disclosedby Your server? Claim it
answering

disclosedby, the subprocessor record is answering right now. Last checked 3 min ago. It exposes 8 tools.

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

Uptime history 47 days of history · worst day 97%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
8
Tools
read from the server
328 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 October 2026. No other catalogue keeps this.

8 Nov 3 tool descriptions were rewritten as_of, changes_across, in_chain
8 Nov a tool appeared check
6 Nov a tool description was rewritten in_chain
6 Nov a tool changed the parameters it asks for in_chain
8 Oct a tool description was rewritten in_chain
8 Oct a tool changed version

disclosedby, the subprocessor record does not always answer

Over the last week it answered 99.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add record --transport http https://disclosedby.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://disclosedby.com/api/mcp
~/.codex/config.toml
[mcp_servers.record]
url = "https://disclosedby.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "record": {
      "url": "https://disclosedby.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "record": {
      "type": "http",
      "url": "https://disclosedby.com/api/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

changes
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 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.
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 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.
as
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 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.
chain
in_chain
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.
check
check
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.
list
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 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.
named
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 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.
resolve
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 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.

Endpoints

URLTransportStateLatencyChecked
https://disclosedby.com/api/mcp streamable-http answering 340 ms 3 min ago

Alternatives to disclosedby, the subprocessor record

same job, measured the same way
getfilings: the Filings door
by allooloo

The disclosures of an issuer in a date range, from the record: signed and receipted (RCO-10060).

3 tools answering
General Dispatch
by generaldispatch

The system of record for home-service businesses, run by your agent: CRM, booking, texts, quotes.

answering
Pramana MCP
by loopg

Read your recorded AI agent runs, and what changed when you swapped a model or prompt.

126 installs/wk local only
OPSIN
by opsinlab

Autonomous lab for the agent economy: switches parts of AI agents on and off, signs what changes.

18 tools answering
Rolston Paul field notes
by rolstonpaul

Read-only search and reading of the field notes on rolstonpaul.com, quoted word for word with URLs.

5 tools answering
Dataconto: who buys company records and code
by dataconto

Who pays owners for company records, code and datasets, closed companies included. Sourced terms.

9 tools answering
Part D Cap
by builtforai

Medicare Part D out-of-pocket cap: when you hit it, and what the payment plan changes

1 tools answering
Backpack
by andrewslogic

A live record of a business or a life, kept up to date from what people say.

answering

disclosedby, the subprocessor record — questions

Answers built from our own checks of this server.

What can disclosedby, the subprocessor record do?
It exposes 8 tools, read directly from the server on our last check. Among them: as_of, changes, changes_across, check, in_chain, list and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is disclosedby, the subprocessor record working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 328 ms. The bar chart above shows every period we have measured.
How do I connect disclosedby, the subprocessor record?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does disclosedby, the subprocessor record need an API key?
No. disclosedby, the subprocessor record completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is disclosedby, the subprocessor record?
It answers our handshake in 328 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.