_ registry / mcp streamable-http · checked 2h ago

disclosedby

https://disclosedby.com

Registry code: d36a3a50fa29469f

api record

A public, dated record of who processes whose data, built only from the subprocessor lists software companies publish under GDPR art. 28. Every row is a quote of a company's own page, with the day it was read. Answers say what the record does not hold as well as what it does: a company with no list read, a name that did not resolve, a date earlier than the first reading held. Take those as stated, never as nothing. "First seen" is the first reading this record holds, not the day a subprocessor was added. Free to read, cite and link. Every row is a dated quote of a company's own published…

endpoint
https://disclosedby.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is disclosedby live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is disclosedby free to use?
Yes — the hub reached it with no key and no payment.
What tools does disclosedby have?
7 tools: as_of, changes, named_by, resolve, in_chain, changes_across, list.
Is disclosedby safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.4%

90 days 98.8%· all time 98.8%

latency
348ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 336 checks · signed record
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
_ what it is for
used for
  • look up a company subprocessor list
  • track changes to subprocessor lists
  • find which companies use a subprocessor
  • trace data processing chains for vendors
takes → gives
text → data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • as_of reads unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 18 lines
  • changes reads unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 17 lines
  • named_by reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subprocessor"
      ],
      "properties": {
        "subprocessor": {
          "type": "string",
          "description": "A subprocessor named on at least one list: its name, an alias, or its id here."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • resolve reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "A name as printed on a list, or an alias."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • in_chain reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "companies",
        "target"
      ],
      "properties": {
        "target": {
          "type": "string",
          "description": "The subprocessor to look for."
        },
        "companies": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 200,
          "description": "The companies the reader buys from, by domain or name."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • changes_across reads unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 20 lines
  • list reads unknown 24h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company"
      ],
      "properties": {
        "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
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d36a3a50fa29469f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d36a3a50fa29469f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d36a3a50fa29469f/badge.svg)](https://brick.blue/agent/d36a3a50fa29469f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.