mcp.thordata.com
https://mcp.thordata.com/.well-known/mcp
active Production-safe Score 91/100 http no auth
At a glance
| Endpoint | https://mcp.thordata.com/.well-known/mcp |
|---|---|
| Source | https://mcp.thordata.com/mcp |
| Transport | http |
| Tools | 10 |
| Auth | none |
| First seen | 2026-09-30 13:03:22 |
| Last checked | 2026-11-17 21:58:16 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 641 / 909 ms |
| Last successful check | 2026-11-17 21:58:16 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (10)
fetch_dataset— Fetch one 10-record page from a ThorData dataset. This call charges the wallet for records actually returned on this page. First call: passfetch_web_scraper— Run one allowlisted Thordata Web Scraper and wait up to five minutes for its final JSON result. A timeout returns the remote task_id withoutget_dataset_info— Read a ThorData dataset's billing unit price, currency, record limits and batch size. This tool does not charge the wallet.get_request_status— Query a dataset order by order_id, or a legacy request by request_id or idempotency_key. This tool does not charge the wallet.history— Query Thor SERP request history.list_datasets— List the dataset packages currently available to this account. This tool does not charge the wallet.list_engines— List Thor SERP engines and schema resource URIs.list_web_scrapers— List the seven supported Thordata Web Scraper products and their current public parameters.search— Execute a Thor SERP search using the current Thor engine schema.statistics— Query Thor SERP usage statistics.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:58:16 | ✓ | ✓ | 574 ms | 90 | active |
| 2026-11-17 21:43:15 | ✓ | ✓ | 698 ms | 90 | active |
| 2026-11-17 21:28:14 | ✓ | ✓ | 592 ms | 90 | active |
| 2026-11-17 21:13:07 | ✓ | ✓ | 707 ms | 90 | active |
| 2026-11-17 20:57:30 | ✓ | ✓ | 793 ms | 90 | active |
| 2026-11-17 20:42:29 | ✓ | ✓ | 534 ms | 90 | active |
| 2026-11-17 20:27:29 | ✓ | ✓ | 752 ms | 90 | active |
| 2026-11-17 20:12:27 | ✓ | ✓ | 661 ms | 90 | active |
| 2026-11-17 19:55:09 | ✓ | ✓ | 831 ms | 90 | active |
| 2026-11-17 19:40:02 | ✓ | ✓ | 1597 ms | 87 | active |
| 2026-11-17 19:24:44 | ✓ | ✓ | 835 ms | 90 | active |
| 2026-11-17 19:09:36 | ✓ | ✓ | 662 ms | 90 | active |
| 2026-11-17 18:54:28 | ✓ | ✓ | 775 ms | 90 | active |
| 2026-11-17 18:39:21 | ✓ | ✓ | 721 ms | 90 | active |
| 2026-11-17 18:24:14 | ✓ | ✓ | 650 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.thordata.com/.well-known/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-thordata-com-well-known-mcp # JSON