AuctionTrace
REMOTE · API.AUCTIONTRACE.COM · SCANNED AUG 3
Historical ES Book Pressure data, matched evidence, and evaluation guidance for $5 USDC via x402.
Available components
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 →
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 Usability17
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 983 tokens (~491/item across 2 items; 2 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.auctiontrace.com
claude mcp add --transport http vermontforest-auctiontrace https://api.auctiontrace.com/mcp
[mcp_servers.vermontforest-auctiontrace] url = "https://api.auctiontrace.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vermontforest-auctiontrace": {
"type": "remote",
"url": "https://api.auctiontrace.com/mcp",
"enabled": true
}
}
} openclaw mcp add vermontforest-auctiontrace --url https://api.auctiontrace.com/mcp --transport streamable-http
mcp_servers:
vermontforest-auctiontrace:
url: "https://api.auctiontrace.com/mcp" {
"mcpServers": {
"vermontforest-auctiontrace": {
"type": "http",
"url": "https://api.auctiontrace.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Jul 26 58
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 3 Aug 2026 · Probed https://api.auctiontrace.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=auctiontrace.com | CN=YE2,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5986a25d3554ae4754b2daab039e64a1472 |
| SANs: api.auctiontrace.com, auctiontrace.com, www.auctiontrace.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
DNSSEC insecure
Validation of api.auctiontrace.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| auctiontrace.com. | 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 |
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.auctiontrace.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.auctiontrace.com/mcp | HTTPS enforced | 301 | https://api.auctiontrace.com/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.
get_auctiontrace_product Get AuctionTrace product ~769
BRING YOUR OWN ES STRATEGY. TEST WHETHER AUCTIONTRACE HELPS MANAGE ITS TRADES BETTER. WHAT IT IS For $5.00 USDC on Base mainnet, AuctionTrace delivers 751,598 validated, timestamped ES Book Pressure observations, a seven-category application map, matched historical evidence, rejected-use guidance, and an accompanying public toolkit for package verification, strict as-of alignment, and matched result comparison. Join the observations strict as-of after entries your strategy already makes; keep entries and baseline behavior fixed. WHAT THE EVIDENCE SUPPORTS Across seven category-specific historical applications, relative profit-factor improvement versus matched price-only management ranged from 2.40% to 26.26%. All seven published AuctionTrace treatment profit factors remained below 1.0, ranging from 0.5130 to 0.9246. The evidence therefore supports better post-entry management versus each matched baseline; it does not establish a profitable standalone system, guarantee profitability, or predict future performance. Six high-sample studies covered 63,350 identical entries and improved all 18 of 18 study windows and all 36 of 36 chronological halves. WHERE IT WAS TESTED 1. Mean reversion — Use adverse pressure when it contradicts the mean-reversion thesis. PF 0.7882 -> 0.8835 (+12.09%). 2. Range rotation — De-risk when pressure contradicts the return-to-center thesis. PF 0.6645 -> 0.8390 (+26.26%). 3. Trend and momentum — Detect early post-entry failure while preserving the original entry. PF 0.8034 -> 0.9246 (+15.09%). 4. Pullback and retracement — Distinguish pressure consistent with resumption from a failed reclaim. PF 0.7038 -> 0.8054 (+14.44%). 5. Breakout and continuation — Cut risk when pressure contradicts the breakout while preserving runner logic. PF 0.7195 -> 0.7946 (+10.44%). 6. Scalping and microstructure — Use immediate adverse pressure to de-risk short-horizon trades. PF 0.5010 -> 0.5130 (+2.40%). 7. Reversal and exhaustion — Select which stopped t…
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_offer | object | yes | — |
| available | boolean | yes | — |
| catalog_url | string | yes | — |
| coverage | object | yes | — |
| data_contract | object | yes | — |
| dataset_id | string | yes | — |
| delivery | string | yes | — |
| description | string | yes | — |
| limitations | array | yes | — |
| manifest_url | string | yes | — |
| market | string | yes | — |
| name | string | yes | — |
| network | string | yes | — |
| payment_protocol | string | yes | — |
| price_usd | string | yes | — |
| product_class | string | yes | — |
| product_family | string | yes | — |
| publisher | string | yes | — |
| purchase_url | string | yes | — |
| record_count | integer | yes | — |
No examples provided.
submit_auctiontrace_offer_feedback Submit AuctionTrace offer feedback ~214
Submit private, optional feedback about the current AuctionTrace offer. Discovery --------- Call get_auctiontrace_product and read agent_offer.questionnaire before submitting. The HTTP equivalent and complete contract are at /api/v1/offer-feedback/schema. When to use ----------- - Tell the owner what task you are performing and what you were looking for. - Explain what is useful, unclear, undesirable, missing, or blocking purchase. - Request owner follow-up without purchasing. Do / Don't ---------- Do provide a stable submission_id so retries are idempotent. Do select the closest enumerated values and use free text only for additional context. Don't include credentials, payment signatures, private keys, proprietary strategy formulas, private addresses, local paths, or sensitive personal data. Idempotency ----------- Retrying the same submission_id from the same anonymous client returns the existing receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| responses | object | yes | — |
| schema_version | string | yes | — |
| stage | string | — | — |
| submission_id | string | — | — |
No output schema declared.
No examples provided.