DAP Compute Market Tracker
REMOTE · DAP.SOLUTIONS
Compute derivatives, their indices and regulator actions, each fact sourced. Agents pay per call.
Available components
Last scanned (59 minutes ago)
Scores higher than 58% 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2147 tokens (~195/item across 11 items; 11 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 Management13
- Stability observed for 4 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compute_list_prices” rewrote its description, which is the text the model reads security
- Tool “compute_market_events” rewrote its description, which is the text the model reads security
- Tool “compute_query” rewrote its description, which is the text the model reads security
- Tool “get_compute_record” rewrote its description, which is the text the model reads security
- Tool “list_compute_coverage” rewrote its description, which is the text the model reads security
- Tool “search_compute_contracts” rewrote its description, which is the text the model reads security
- Schema quality: 233 → 195 ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “find-cheapest-gpu-hour” functional
- New tool “get-compute-contract” functional
- New tool “get-gpu-price” functional
- New tool “list-price-changes” functional
- New tool “list-regulator-actions” functional
- “compute_list_prices” reworded the description of “gpu” cosmetic
- “compute_list_prices” reworded the description of “instance” cosmetic
- “compute_query” reworded the description of “query” cosmetic
- 4 Nov 26 0
- Tool “compute_list_prices” rewrote its description, which is the text the model reads security
- “compute_list_prices” added an optional parameter “price_type” cosmetic
- “compute_list_prices” added an optional parameter “region” cosmetic
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1085 → 1352 ▼ functional
- New tool “compute_query” functional
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 180 → 217 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “compute_list_prices” functional
- 1 Nov 26 70
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://dap.solutions/compute/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dap.solutions | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 110c2c12de8ecfc80eae5a48a600f84f |
| SANs: dap.solutions, bellwether.dap.solutions, *.bellwether.dap.solutions | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dap.solutions. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| solutions. | present | 23131 | 8 | Verified |
| dap.solutions. | 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=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dap.solutions/compute/mcp | Verified | 200 | |
| http (plaintext) | http://dap.solutions/compute/mcp | HTTPS enforced | 301 | https://dap.solutions/compute/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 →
compute_list_prices GPU rental list prices ~330
Use when you need GPU rental list prices with their history. Every AWS and Azure line, one per region and instance, never averaged, per instance-hour and per GPU-hour, with every change since 2020. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | GPU family, for example H100, A100, H200, B200, B300 or GB200. Each line is the list price the provider publishes in its own feed (AWS Price List, one price list a month back to October 2020; Azure R… |
| history | boolean | – | Include every price point in the window, not only the latest price and the changes. |
| instance | string | – | One instance type, for example p5.48xlarge or Standard_ND96isr_H100_v5. The price per GPU-hour is derived: the listed price per instance-hour divided by the GPUs on the provider's specification page. |
| price_type | string | – | On-demand or Spot. |
| provider | string | – | Cloud provider, for example AWS or Azure. |
| region | string | – | One region, by code or name, for example us-east-1 or East US. |
| since | string | – | ISO date, YYYY-MM-DD. History from this date; the price holding on that date is included. |
| until | string | – | ISO date, YYYY-MM-DD. History up to this date. |
No output schema declared.
No examples provided.
compute_market_events Compute market events ~160
Use when you need dated events on compute derivatives. Lists announcements, filings, regulator actions and dates still to come, filtered by date, type or contract. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | string | – | Restrict to events about one contract id (ct-). |
| kind | string | – | Restrict to one event type. |
| limit | integer | – | Maximum events to return. |
| since | string | – | ISO date, YYYY-MM-DD. Only events on or after this date. |
| until | string | – | ISO date, YYYY-MM-DD. Only events on or before this date. |
| upcoming_only | boolean | – | Only dates after the snapshot date. |
No output schema declared.
No examples provided.
compute_query Query the compute market console ~275
Use when you need to filter, group, rank or chart compute market data in one call. Takes the console's query object and returns lines, headline numbers, a league table, contracts, events and sources. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| query | object | yes | The console query object. {} is the default view: every line, all time. Filters are a tree of field, operator and value. Fields: provider, chip (GPU, e.g. h100-80), model (a model or its maker), regi… |
No output schema declared.
No examples provided.
find-cheapest-gpu-hour Cheapest GPU-hour ~141
Use when you need the cheapest place to rent a given GPU. Compares every tracked provider's current list price per GPU-hour, optionally in one region, and returns the cheapest with its source. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chip | string | yes | GPU family, for example H100, A100, H200, B200, B300 or GB200. |
| price_type | string | – | On-demand (default) or Spot. |
| region | string | – | Only lines in this region, by code or name. Leave out to compare every region. |
No output schema declared.
No examples provided.
get_compute_record Get one compute market record ~90
Use when you have a record id (ct-, ser-, ent- or ev-) and need it in full. Returns its classification, status history, held-back fields and every source. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A record id from a search, an event list or list_compute_coverage. |
No output schema declared.
No examples provided.
get-compute-contract One compute derivative contract ~99
Use when you need one compute derivative contract in full. Returns its terms, status history, the index it settles against and its venue, with sources. Index values are not returned. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | string | yes | The contract id (ct-), its exchange code or its full name, for example ct-nymex-gpu1. |
No output schema declared.
No examples provided.
get-gpu-price Current GPU rental price ~153
Use when you need what one cloud charges to rent a GPU in one region now. Returns the price per GPU-hour, the last change, the source URL and when it was read. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chip | string | yes | GPU family, for example H100, A100, H200, B200, B300 or GB200. |
| price_type | string | – | On-demand (default) or Spot. |
| provider | string | yes | Cloud provider: AWS or Azure. |
| region | string | yes | One region, by code or name, for example us-east-1, eastus or East US. |
No output schema declared.
No examples provided.
list_compute_coverage Compute market coverage ~41
Use when you need to know what the Compute Market Tracker covers before concluding something does not exist. Returns the snapshot date, counts and every source. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-price-changes GPU list price changes ~164
Use when you need to know whether GPU rental prices moved. Lists list-price changes since a date for one chip or provider, newest first, up to 100 rows, each with its source. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chip | string | – | GPU family, for example H100. Give chip, provider or both. |
| limit | integer | – | Most rows to return, newest first. At most 100. |
| price_type | string | – | On-demand (default) or Spot. |
| provider | string | – | Cloud provider: AWS or Azure. Give chip, provider or both. |
| since | string | yes | ISO date, YYYY-MM-DD. Changes after this date. |
No output schema declared.
No examples provided.
list-regulator-actions Regulator actions on traded compute ~129
Use when you need what regulators have done about traded compute. Lists regulator actions and due dates on compute derivatives since a date, newest first, with sources. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most rows to return, newest first. At most 100. |
| regulator | string | – | Only actions by one regulator, by short name or full name, for example CFTC. |
| since | string | yes | ISO date, YYYY-MM-DD. Actions and due dates on or after this date. |
No output schema declared.
No examples provided.
search_compute_contracts Search compute derivative contracts ~198
Use when you need to find compute derivative contracts. Searches futures and options on GPU rental indices by venue, status, index publisher, jurisdiction, settlement or name. 50 free calls a day, then $0.01 USDC on Base per call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| index_publisher | string | – | Restrict to contracts settling against one publisher's index, for example "Silicon Data". |
| jurisdiction | string | – | Two letter country code of the listing venue, for example US. |
| limit | integer | – | Maximum contracts to return. |
| query | string | – | Words matched against the contract name, code, venue and index, for example "H100" or "NYMEX". |
| settlement | string | – | Restrict by settlement method. |
| status | string | – | Restrict to one status. |
| venue | string | – | Restrict to one venue by short name, for example NYMEX or ICE. |
No output schema declared.
No examples provided.
How do I install the DAP Compute Market Tracker MCP server?
DAP Compute Market Tracker is a hosted endpoint at https://dap.solutions/compute/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 · dap.solutions
claude mcp add --transport http solutions-dap-compute 'https://dap.solutions/compute/mcp'
What is the DAP Compute Market Tracker MCP server?
DAP Compute Market Tracker is an MCP server listed in the public MCP registry as solutions.dap/compute. Compute derivatives, their indices and regulator actions, each fact sourced. Agents pay per call. This page covers its hosted endpoint (https://dap.solutions/compute/mcp).
Is the DAP Compute Market Tracker MCP server safe to use?
DAP Compute Market Tracker scores 72 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 DAP Compute Market Tracker MCP server expose?
DAP Compute Market Tracker exposes 11 tools: search_compute_contracts, get_compute_record, compute_market_events, compute_list_prices, compute_query, and 6 more. Their descriptions and schemas cost roughly 1,780 tokens of context every time the server is loaded.
Does the DAP Compute Market Tracker MCP server require authentication?
No. We connected to DAP Compute Market Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DAP Compute Market Tracker MCP server still maintained?
DAP Compute Market Tracker 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.