Agent Desk API (deskfeed.dev)
REMOTE · DESKFEED.DEV
Crypto market context for agents: futures state + trusted events. x402 pay-per-call on Base.
Available components
Last scanned (5 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Crypto and Web3
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 (good).Pass
- Context-footprint check failed: tool/resource definitions use about 536 tokens (~134/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 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.
- 15 Oct 26 0
- Tool “market_state” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.4.0 → 0.5.0 functional
- 14 Oct 26 63
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 18 Oct 2026 · Probed https://deskfeed.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=deskfeed.dev | CN=YE1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6c81855855052ca6d8a4875d7d86fb5a475 |
| SANs: *.deskfeed.dev, deskfeed.dev | ||||||
| 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 deskfeed.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| deskfeed.dev. | 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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deskfeed.dev/mcp | Verified | 200 | |
| http (plaintext) | http://deskfeed.dev/mcp | HTTPS enforced | 301 | https://deskfeed.dev/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 →
bsc_alerts ~181
Volume-anomaly observations across newly created BSC pools, from a 15-minute monitoring sweep: pools whose hourly volume spiked vs the prior hour (floor $1,000 and 100x), with pool name, hourly volume, spike ratio, price move and source link. Machine-readable monitoring feed for agents tracking early on-chain activity. Observation data only — thresholds uncalibrated; not signals, not financial advice. Refreshed every 15 minutes; data age disclosed in every response. Paid per call via x402: $0.005 USDC on Base — the payment challenge is returned automatically; x402-capable clients retry with payment.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max alerts to return (newest first) (default: 10) |
| window_hours | integer | – | Look-back window in hours (default: 24) |
No output schema declared.
No examples provided.
event_facts ~165
Verified market-moving events for crypto agents: headlines categorized (liquidations, macro, regulation and more) and tagged to BTC/ETH, each with source, publisher, timestamp, original link, and a trust tier distinguishing primary official sources from aggregated headlines. Filter by symbol, category, and count. Fresh every 15 minutes. Paid per call via x402: $0.005 USDC on Base — the payment challenge is returned automatically; x402-capable clients retry with payment.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category (e.g. LIQUIDATION, MACRO, REGULATION) |
| limit | integer | – | Max events to return (default: 10) |
| symbol | string | – | Filter events by symbol, e.g. BTCUSDT |
No output schema declared.
No examples provided.
market_state ~178
Multi-timeframe market state for BTCUSDT, ETHUSDT, SOLUSDT, XRPUSDT & DOGEUSDT USD-M perpetual futures in one call: mark & index price, funding rate, open interest change, taker buy share, per-timeframe (4h/1h/15m) EMA-20/50, RSI-14, ATR and prior 20-bar high/low. Structured for trading agents needing clean market context. Descriptive data only — not financial advice. Refreshed every 15 min; data age disclosed in every response. Paid per call via x402: $0.01 USDC on Base — the payment challenge is returned automatically; x402-capable clients retry with payment.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | Futures symbol; ALL returns every covered symbol (default: BTCUSDT) |
No output schema declared.
No examples provided.
ping ~12
Health check (free).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Agent Desk API (deskfeed.dev) MCP server?
Agent Desk API (deskfeed.dev) is a hosted endpoint at https://deskfeed.dev/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 · deskfeed.dev
claude mcp add --transport http dev-deskfeed-deskfeed-api 'https://deskfeed.dev/mcp'
What is the Agent Desk API (deskfeed.dev) MCP server?
Agent Desk API (deskfeed.dev) is an MCP server listed in the public MCP registry as dev.deskfeed/deskfeed-api. Crypto market context for agents: futures state + trusted events. x402 pay-per-call on Base. This page covers its hosted endpoint (https://deskfeed.dev/mcp).
Is the Agent Desk API (deskfeed.dev) MCP server safe to use?
Agent Desk API (deskfeed.dev) scores 65 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 Agent Desk API (deskfeed.dev) MCP server expose?
Agent Desk API (deskfeed.dev) exposes 4 tools: market_state, event_facts, bsc_alerts, ping. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.
Does the Agent Desk API (deskfeed.dev) MCP server require authentication?
No. We connected to Agent Desk API (deskfeed.dev) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Desk API (deskfeed.dev) MCP server still maintained?
Agent Desk API (deskfeed.dev) is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.