AIData.Broker
REMOTE · AIDATA.BROKER
Sells companies' data to AI labs for them: prices, buyers, deals, rulings and a free valuation.
Available components
Last scanned (12 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2026 tokens (~202/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 3 Nov 26 +1
- “value_data” reworded the description of “kind” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 2026.10.16 → 2026.10.28 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://aidata.broker/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aidata.broker | CN=YR1,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | 623f3a1cb3117999e5a38a2233ac0dfc4d3 |
| SANs: aidata.broker | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aidata.broker. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| broker. | present | 35449 | 8 | Verified |
| aidata.broker. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: data: https://js.stripe.com https://platform.twitter.com https://www.googletagmanager.com https://*.elevenlabs.io; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob: data:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' blob: https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://*.elevenlabs.io wss://*.elevenlabs.io https://elevenlabs.io wss://elevenlabs.io; worker-src 'self' blob: data:; frame-src 'self' https://js.stripe.com https://hooks.stripe.com https://www.youtube-nocookie.com https://www.youtube.com https://player.vimeo.com https://www.loom.com https://www.dailymotion.com https://platform.twitter.com https://elevenlabs.io https://*.elevenlabs.io; frame-ancestors 'self' http://localhost:* https://o-mega.ai https://*.o-mega.ai h |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aidata.broker/mcp | Verified | 200 | |
| http (plaintext) | http://aidata.broker/mcp | HTTPS enforced | 308 | https://aidata.broker/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_software_terms What a business system's terms allow for AI training data ~122
For a business system (Slack, Microsoft 365, Google Workspace, Salesforce, HubSpot, Zendesk, Zoom, GitHub, Notion and more): whether the holder can export its data, what the vendor's API terms say about training AI on data pulled through them, our reading of the content's rights risk, and the clauses word for word. Research from public sources, not legal advice. Without `system`, lists the systems on file.
| Name | Type | Req | Description |
|---|---|---|---|
| system | string | – | The system's name, such as "Slack" or "Zendesk". |
No output schema declared.
No examples provided.
find_buyers Find buyers of a kind of AI training data ~173
Organisations with a public way to sell them data, with their own published terms: what they want, what they pay, when they pay, who removes personal data, eligibility, and what they pay an introducer. Largest published figure first.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | The kind of data: company-records (Company records), source-code (Source code), video (Video and footage), audio-speech (Audio and speech), images (Images), text-archives (Text and archives), dataset… |
| limit | integer | – | How many rows to return (default 10, at most 50). |
| query | string | – | Words that must all appear in the buyer's name or terms. |
No output schema declared.
No examples provided.
find_lots Find data on offer across brokers' catalogues ~278
Every lot publicly on offer in the catalogues the lot index reads each day (companies' records, codebases, footage, speech, environments), in one vocabulary: kind, industry, years of history, systems, size, what its catalogue says about the rights and whether it is ready, each linked to its catalogue's own page. We have not checked any catalogue's claims. No holder is named. Longest history first.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | The holder's industry, as this site names industries. |
| kind | string | – | The kind of data: company-records (Company records), source-code (Source code), video (Video and footage), audio-speech (Audio and speech), images (Images), text-archives (Text and archives), dataset… |
| limit | integer | – | How many rows to return (default 10, at most 50). |
| query | string | – | Words that must all appear in the lot's title, line of business or systems. |
| rights | string | – | "settled": the lot's own catalogue says its holder has the rights with nothing left to confirm; "open": the catalogue names conditions or consent still to confirm. We have not checked either. |
No output schema declared.
No examples provided.
find_vendors Find companies that sell AI training data ~195
Vendors that sell training data, RL environments, evaluations, expert work or annotation to AI developers, each with what it says it sells and where its data comes from in its own words, and whether it says it pays holders for data. A to Z, not ranked.
| Name | Type | Req | Description |
|---|---|---|---|
| buys | boolean | – | Only vendors that say they buy, license or pay for data from its holders. |
| from | string | – | Where it says its data comes from: licensed, customer, experts, captured, synthetic, replica, public ("licensed" means licensed from the companies or creators that hold it). |
| limit | integer | – | How many rows to return (default 10, at most 50). |
| query | string | – | Words that must all appear in the vendor's name or what it sells. |
| sells | string | – | What the vendor sells: rl-environments, datasets, human-data, evals, annotation, simulation. |
No output schema declared.
No examples provided.
get_market_rates Market rates for AI training data ~199
Median, middle half and range per comparable unit (per hour of video or audio, per image, per task, per company, per title, and more) for each kind of AI training data and each side of the market, computed from published prices. Without `kind`, returns every rate the evidence supports a median for.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | The kind of data: company (Company records), code (Source code), video (Video and footage), audio (Audio and speech), images (Images), text (Text and archives), environment (Datasets, tasks and envir… |
| side | string | – | The side of the market: pay (Paid to the people who make it), offer (Offered to holders), licence (Sales that happened), listing (Asking prices off the shelf), collection (Made to order), cost (Cost… |
No output schema declared.
No examples provided.
list_datasets List the open datasets ~63
Every table behind these tools as a CSV and JSON download (our compilation of the tables under CC BY 4.0; quotes keep their sources' terms, and article text is not covered), with row counts, review dates and the permanent copies with their DOIs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_cases Search lawsuits and rulings over AI training data ~116
Lawsuits, rulings, settlements and regulatory actions over data used to train AI, with parties, claim, amounts, outcome, status and the source. Newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | The kind of case: guidance, lawsuit, regulatory action, ruling, settlement. |
| limit | integer | – | How many rows to return (default 10, at most 50). |
| query | string | – | Words that must all appear, such as a party ("Anthropic"), a court or a kind of content ("books"). |
No output schema declared.
No examples provided.
search_deals Search disclosed AI data licensing deals ~146
Licences of data to AI companies disclosed since July 2023: licensor, licensee, content, use (training or display), term, value where disclosed, with a verbatim quote and the source. Newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many rows to return (default 10, at most 50). |
| query | string | – | Words that must all appear, such as a licensor, a licensee ("OpenAI") or a kind of content ("news"). |
| since | string | – | Only deals on or after this date (YYYY, YYYY-MM or YYYY-MM-DD). |
| use | string | – | What the data is used for. |
No output schema declared.
No examples provided.
search_prices Search published AI training data prices ~247
The individual price observations behind the market rates: what a lab, vendor, marketplace or court said data was paid, offered, listed or sold for, with the figure as published, the figure per unit, the date, the source's own words and a link. Newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | The kind of data: company (Company records), code (Source code), video (Video and footage), audio (Audio and speech), images (Images), text (Text and archives), environment (Datasets, tasks and envir… |
| limit | integer | – | How many rows to return (default 50, at most 50). |
| query | string | – | Words that must all appear, such as a company ("Shutterstock"), a language ("hindi") or a kind of record ("egocentric"). |
| side | string | – | The side of the market: pay (Paid to the people who make it), offer (Offered to holders), licence (Sales that happened), listing (Asking prices off the shelf), collection (Made to order), cost (Cost… |
No output schema declared.
No examples provided.
value_data Value a holding of data from public prices ~194
What published prices imply for a holding of data: a low-to-high range in US dollars with the arithmetic behind it. Call it first with only `kind` to get the questions and their answer ids, ask the holder, then call again with `answers`. Questions not answered are taken at their defaults and marked as assumed. An indication, not an offer.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | Answer ids by question id, as returned in `questions` (for video, for example {"hours": "1000-10000"}); every answer is one of the listed answer ids, sent as text. |
| kind | string | yes | What is being valued: records (Company records), code (Codebases), video (Video and footage), speech (Audio and speech), images (Images), text (Text and archives), robotics (Robot and physical-world… |
No output schema declared.
No examples provided.
How do I install the AIData.Broker MCP server?
AIData.Broker is a hosted endpoint at https://aidata.broker/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · aidata.broker
claude mcp add --transport http broker-aidata-market 'https://aidata.broker/mcp'
What is the AIData.Broker MCP server?
AIData.Broker is an MCP server listed in the public MCP registry as broker.aidata/market. Sells companies' data to AI labs for them: prices, buyers, deals, rulings and a free valuation. This page covers its hosted endpoint (https://aidata.broker/mcp).
Is the AIData.Broker MCP server safe to use?
AIData.Broker scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AIData.Broker MCP server expose?
AIData.Broker exposes 10 tools: get_market_rates, search_prices, value_data, find_buyers, find_vendors, and 5 more. Their descriptions and schemas cost roughly 1,733 tokens of context every time the server is loaded.
Does the AIData.Broker MCP server require authentication?
No. We connected to AIData.Broker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AIData.Broker MCP server still maintained?
AIData.Broker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.