AI Training Data Broker
REMOTE · AITRAININGDATABROKER.COM
Guidance on selling or licensing company data to AI labs: deal steps, de-identification, compliance.
Available components
Last scanned (10 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 611 tokens (~122/item across 5 items; 5 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 Management30
- Stability observed for 9 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 71
First indexed and scored.
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://aitrainingdatabroker.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aitrainingdatabroker.com | CN=YE1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6fccb9768b10f331350112d5dd039ae7a60 |
| SANs: *.aitrainingdatabroker.com, aitrainingdatabroker.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aitrainingdatabroker.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| aitrainingdatabroker.com. | No DS | 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' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; frame-src https://www.youtube-nocookie.com https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; font-src 'self' data:; object-src 'none'; base-uri 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aitrainingdatabroker.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://aitrainingdatabroker.com/api/mcp | HTTPS enforced | 301 | https://aitrainingdatabroker.com/api/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 →
fetch Fetch (connector) ~36
Connector-style fetch of one article by the id from search. Same opening as get_post.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Article slug from search |
No output schema declared.
No examples provided.
get_post Read an article ~126
One article by slug (the last part of its URL) or its full URL: title, date, who it is for, the opening 120 words, the questions its FAQ answers, and a link to read the rest. Use it after a list or search result when the user wants to know what an article says. Limitation: returns the opening, not the full text; the full article and its answers are on the linked page.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Article slug, e.g. how-much-do-ai-labs-pay-for-company-data, or the full URL |
No output schema declared.
No examples provided.
latest_posts Latest articles ~140
The newest articles on the AI Training Data Broker blog, optionally only those for sellers (companies selling or licensing their data to AI labs) or buyers (labs sourcing licensed training data). Each result is a title, date, reading time, one-line summary and a link to the full article. Limitation: at most 10 per call, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | seller: companies selling or licensing their data. buyer: AI labs and model teams sourcing data. deid: de-identifying data to meet privacy laws (HIPAA, CCPA, GDPR). Leave out for all. |
| limit | integer | – | How many to return |
No output schema declared.
No examples provided.
search Search (connector) ~38
Connector-style search over the blog. Returns ids for fetch. Prefer search_posts for a filtered list.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Words to search for |
No output schema declared.
No examples provided.
search_posts Search articles ~144
Search the AI Training Data Broker blog by topic, for example "what is my company data worth", "is it legal", "exclusive license", "RL data". Returns matching articles with a one-line summary and a link to the full article. Limitation: plain word matching in English, at most 10 results.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | seller: companies selling or licensing their data. buyer: AI labs and model teams sourcing data. deid: de-identifying data to meet privacy laws (HIPAA, CCPA, GDPR). Leave out for all. |
| limit | integer | – | How many to return |
| query | string | yes | Words to search for |
No output schema declared.
No examples provided.
How do I install the AI Training Data Broker MCP server?
AI Training Data Broker is a hosted endpoint at https://aitrainingdatabroker.com/api/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 · aitrainingdatabroker.com
claude mcp add --transport http com-aitrainingdatabroker-mcp 'https://aitrainingdatabroker.com/api/mcp'
What is the AI Training Data Broker MCP server?
AI Training Data Broker is an MCP server listed in the public MCP registry as com.aitrainingdatabroker/mcp. Guidance on selling or licensing company data to AI labs: deal steps, de-identification, compliance. This page covers its hosted endpoint (https://aitrainingdatabroker.com/api/mcp).
Is the AI Training Data Broker MCP server safe to use?
AI Training Data Broker scores 76 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 AI Training Data Broker MCP server expose?
AI Training Data Broker exposes 5 tools: latest_posts, search_posts, get_post, search, fetch. Their descriptions and schemas cost roughly 484 tokens of context every time the server is loaded.
Does the AI Training Data Broker MCP server require authentication?
No. We connected to AI Training Data Broker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Training Data Broker MCP server still maintained?
AI Training Data 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.
What did VerifyMCP test on the AI Training Data Broker MCP server?
VerifyMCP ran 13 checks on AI Training Data Broker, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.