mcp-registry/com.disclosedby/record · v2
As of 2026-10-22 00:24 UTC, the Disclosedby Record MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 23 outages in 90 days, with a median recovery of 6 minutes.
Dated quotes of GDPR art. 28 subprocessor lists: who lists whom, fourth parties, what changed, when.
Claude Code
claude mcp add --transport http disclosedby-record-mcp-server https://disclosedby.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"disclosedby-record-mcp-server": {
"type": "http",
"url": "https://disclosedby.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.disclosedby%2Frecord/fixes
{
"name": "as_of",
"description": "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 i",
"inputSchema": {
"type": "object",
"required": [
"company",
"date"
],
"properties": {
"date": {
"type": "string",
"description": "ISO date, e.g. 2024-01-01."
},
"company": {
"type": "string",
"description": "A company with a list on this record: its domain (notion.so) or its name (Notion). One company per call."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "What a list said on a date"
}{
"name": "changes",
"description": "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 publ",
"inputSchema": {
"type": "object",
"required": [
"company"
],
"properties": {
"since": {
"type": "string",
"description": "Optional ISO date; only changes on or after it."
},
"company": {
"type": "string",
"description": "A company with a list on this record: its domain (notion.so) or its name (Notion). One company per call."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "What changed on a company's list"
}{
"name": "changes_across",
"description": "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 i",
"inputSchema": {
"type": "object",
"required": [
"companies"
],
"properties": {
"since": {
"type": "string",
"description": "Optional ISO date; only changes on or after it."
},
"companies": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 200
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Changes across a reader's own list"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.disclosedby/record"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.disclosedby/record"}) over MCP.
changes ~243 tokensin_chain ~239 tokensas_of ~238 tokenschanges_across ~224 tokenslist ~217 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.disclosedby%2Frecord?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.disclosedby%2Frecord?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.disclosedby%2Frecord.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.disclosedby%2Frecord.svg :target: https://glimind.com/server/mcp-registry%2Fcom.disclosedby%2Frecord?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cbfe616812a105c0…, first seen 2026-10-17, included at leaf 1646 of 42,394. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable data servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 00:24 UTC, the Disclosedby Record MCP server is up with a Glimind reliability score of 75/100 (grade B). Over the last 30 days it answered 99.4% of Glimind's liveness checks. It had 23 outages in 90 days, with a median recovery of 6 minutes.
Disclosedby Record MCP server advertises 7 tools, including as_of, changes, changes_across, in_chain, list.
Point your MCP client at this streamable-http endpoint: https://disclosedby.com/api/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.