Remote MCP · Endpoint
disclosedby, the subprocessor record MCP server
No. disclosedby, the subprocessor record answered an MCP handshake 52 minutes ago.
UpLast checked 52 minutes ago
Server URL
https://disclosedby.com/api/mcp
The last check completed an MCP handshake.
- Registry name
- com.disclosedby/record
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 226 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 16 checks
- Described by its publisher as
- Dated quotes of GDPR art. 28 subprocessor lists: who lists whom, fourth parties, what changed, when.
- Website
- https://disclosedby.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 52 minutes ago | Handshake completed | 226 ms |
| 2 days ago | Handshake completed | 171 ms |
| 4 days ago | Handshake completed | 190 ms |
| 5 days ago | Handshake completed | 191 ms |
| 7 days ago | Handshake completed | 511 ms |
| 8 days ago | Handshake completed | 199 ms |
| 9 days ago | Handshake completed | 446 ms |
| 12 days ago | Handshake completed | 444 ms |
| 13 days ago | Handshake completed | 200 ms |
| 15 days ago | Handshake completed | 194 ms |
| 17 days ago | Handshake completed | 190 ms |
| 18 days ago | Handshake completed | 419 ms |
| 19 days ago | Handshake completed | 438 ms |
| 20 days ago | Handshake completed | 1.39 s |
| 21 days ago | Handshake completed | 222 ms |
| 21 days ago | Handshake completed | 200 ms |
The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with disclosedby, the subprocessor record and makes no claim about it beyond what these checks measured.