dataclue
Registry code: 3c477ac534bf942e
DataClue licenses real-world AI training data: 800,000+ hours of egocentric (first-person) video of people doing real work, 70,680 hours of UMI handheld-gripper demonstrations, and custom collection (new scenarios, robot teleoperation, non-invasive EEG / brain-computer interface data).
Use search_datasets to find data for a need, get_dataset for specs, scenarios and samples, and get_pricing_and_terms for prices and licensing. Use request_quote only when the user asks to contact DataClue (for samples, a pilot, a quote or a custom collection) and has given their own work email; confirm the…
- endpoint
- https://dataclue.app/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 dataclue live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is dataclue free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does dataclue have?
- 4 tools: search_datasets, get_dataset, request_quote, get_pricing_and_terms.
- Is dataclue 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
get_pricing_and_terms open 1h ago
DataClue's list prices, what is included, quote paths (free samples, paid pilot, volume quote, custom collection), licensing, payment and consent terms.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linessearch_datasets unknown never probed
Search DataClue's catalog of licensable AI training data (egocentric video of real work, UMI gripper demonstrations) with a plain-English need, e.g. "50,000 hours of household manipulation video, 1080p, long sessions". Returns matching datasets with hours in stock, price per hour, scenarios and which requirements they meet, plus custom-collection options when nothing in stock fits.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "What data is needed: domain, task, volume, resolution, frame rate, session length, sensors." } }, "additionalProperties": false }arguments 13 linesget_dataset unknown never probed
Full details for one DataClue dataset: overview, scenarios with measured sample specs, delivered resolution, sensors, annotation, delivery format, licensing, FAQs, sample clip URLs and price.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Dataset slug, e.g. \"manufacturing-operations\", \"household-activities\", \"warehouse-logistics\"." } }, "additionalProperties": false }arguments 13 linesrequest_quote unknown never probed
Send a request to DataClue's sales team on the user's behalf: free evaluation samples, a paid pilot, a volume quote, or a custom collection. Side effect: emails the request (including the user's name, work email and company) to DataClue, who reply to that email. Only call this when the user has asked to contact DataClue and has provided their own work email, and show them the details to confirm before sending. Each call sends a new request, so do not retry a successful call.
{ "type": "object", "required": [ "email", "plan" ], "properties": { "name": { "type": "string", "description": "The user's name (required except for samples)." }, "plan": { "enum": [ "sample", "pilot", "volume", "custom" ], "type": "string", "description": "sample = free evaluation clips; pilot = 10-hour paid pilot; volume = quote for a number of hours; custom = data collected to order." }, "email": { "type": "string", "description": "The user's work email. DataClue replies here." }, "hours": { "type": "number", "description": "Hours needed. Required for volume." }, "company": { "type": "string", "description": "The user's company (required except for samples)." }, "details": { "type": "string", "description": "Requirements in the user's words. Required for custom (what should be collected)." }, "datasets": { "type": "array", "items": { "type": "string" }, "description": "Dataset slugs (from search_datasets). Required for pilot and volume." }, "timeline": { "type": "string", "description": "When the data is needed." }, "use_case": { "enum": [ "Robot policy / VLA pretraining", "World model training", "Perception & action recognition", "Evaluation / benchmarking", "Research (non-commercial)", "Other" ], "type": "string", "description": "Intended use. Required for volume." }, "scenarios": { "type": "array", "items": { "type": "string" }, "description": "Optional scenario slugs." } }, "additionalProperties": false }arguments 70 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3c477ac534bf942e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3c477ac534bf942e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3c477ac534bf942e?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.