Remote MCP · Endpoint

disclosedby, the subprocessor record MCP server

No. disclosedby, the subprocessor record answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
197 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Dated quotes of GDPR art. 28 subprocessor lists: who lists whom, fourth parties, what changed, when.
Listing
From the official MCP registry (active).
Recent checks of disclosedby, the subprocessor record
CheckedResultHandshake
1 hour agoHandshake completed197 ms
1 day agoHandshake completed438 ms
2 days agoHandshake completed482 ms
3 days agoHandshake completed457 ms
4 days agoHandshake completed178 ms
5 days agoHandshake completed196 ms
6 days agoHandshake completed168 ms
8 days agoHandshake completed170 ms
11 days agoHandshake completed187 ms
13 days agoHandshake completed189 ms
15 days agoHandshake completed432 ms
18 days agoHandshake completed181 ms
20 days agoHandshake completed226 ms
22 days agoHandshake completed171 ms
24 days agoHandshake completed190 ms
26 days agoHandshake completed191 ms
27 days agoHandshake completed511 ms
29 days agoHandshake completed199 ms
29 days agoHandshake completed446 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 28.

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.