Askew x402
REMOTE · MCP.ASKEW.NETWORK · SCANNED SEP 3
DeFi yields, staking routing, semantic research & security intel via x402 micro-payments on Base
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Askew x402 MCP server?
Askew x402 is a hosted endpoint at https://mcp.askew.network/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 · mcp.askew.network
claude mcp add --transport http rubix1138-askew-x402 'https://mcp.askew.network/mcp'
{
"mcpServers": {
"rubix1138-askew-x402": {
"url": "https://mcp.askew.network/mcp"
}
}
} {
"servers": {
"rubix1138-askew-x402": {
"type": "http",
"url": "https://mcp.askew.network/mcp"
}
}
} [mcp_servers.rubix1138-askew-x402] url = "https://mcp.askew.network/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rubix1138-askew-x402": {
"type": "remote",
"url": "https://mcp.askew.network/mcp",
"enabled": true
}
}
} openclaw mcp add rubix1138-askew-x402 --url 'https://mcp.askew.network/mcp' --transport streamable-http
mcp_servers:
rubix1138-askew-x402:
url: "https://mcp.askew.network/mcp" {
"McpServers": {
"rubix1138-askew-x402": {
"Transport": "http",
"Url": "https://mcp.askew.network/mcp"
}
}
} assistant mcp add rubix1138-askew-x402 -t streamable-http -u 'https://mcp.askew.network/mcp'
{
"mcpServers": {
"rubix1138-askew-x402": {
"type": "http",
"url": "https://mcp.askew.network/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.
- 3 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 29 Aug 26 0
- DNSSEC: pass → unverified ▼ security
- 28 Aug 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 27 Aug 26 −59
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
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 Sept 2026 · Probed https://mcp.askew.network/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.askew.network. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.askew.network. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.askew.network/mcp | Unreachable | ||
| http (plaintext) | http://mcp.askew.network/mcp | HTTPS enforced |
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 →
askew_health ~46
Service status for the Askew x402 endpoint. Returns wallet address, network, current pricing, and payment summary. Free — use to verify the service is operational before making paid calls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
askew_intel_feed ~76
Aggregated intelligence feed combining research findings, active security threats, and live staking APY snapshot in a single call ($0.005 USDC). Sources: ChromaDB research library + Guardian log + staking.db. Best for: broad situational awareness — replaces three separate calls. Requires x402 payment on Base mainnet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
askew_intel_threats ~109
Live threat intelligence from the Askew Guardian security monitor ($0.002 USDC). Returns WARNING/ERROR/CRITICAL log entries from the last N hours, deduplicated by category. Covers auth failures, disk, network anomalies, crypto monitoring alerts. Near-real-time Guardian log view. Best for: security triage before agent operations. Requires x402 payment on Base mainnet.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Lookback window in hours (default: 24, optional) |
No output schema declared.
No examples provided.
askew_offers ~46
Curated catalog of all available paid Askew endpoints with pricing, sample calls, and buyer intent context. Best starting point for agents exploring what Askew sells. No payment required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
askew_research_query ~154
Semantic search over 500+ Askew agent-economy research findings, operational insights, and experiments ($0.003 USDC). Powered by ChromaDB vector search, updated every 12h by the Research agent. Collections: research_findings | agent_insights | experiments. Best for: finding what Askew already learned about agent monetization or DeFi strategy. Requires x402 payment on Base mainnet.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | Collection to search: research_findings | agent_insights | experiments (default: research_findings) |
| limit | integer | – | Number of results to return, 1-20 (default: 5) |
| q | string | yes | Search query (required) |
No output schema declared.
No examples provided.
askew_staking_router ~80
Staking yield router for SOL and ATOM ($0.003 USDC). Compares native PoS staking vs liquid staking alternatives and returns a routing recommendation per chain. Data from DefiLlama + staking portfolio, cached up to 6h. Best for: deciding native vs liquid staking. Requires x402 payment on Base mainnet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
askew_yields ~106
Live DeFi yield comparison across 5 chains in one call ($0.002 USDC). Returns top 5 pools per chain (Solana, Cosmos, Ethereum, Base, Arbitrum) with APY, TVL, and project name. Data from DefiLlama, cached up to 6h. Best for: quick yield scanning before moving capital. Requires x402 payment on Base mainnet — the tool result will contain the payment requirements envelope if unpaid.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
askew_yields_preview ~62
Free preview of top DeFi yield pool per chain across Solana, Cosmos, Ethereum, Base, and Arbitrum. Returns the single best APY option per chain. Use before buying askew_yields for a full comparison. No payment required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Askew x402 MCP server?
Askew x402 is an MCP server listed in the public MCP registry as io.github.rubix1138/askew-x402. DeFi yields, staking routing, semantic research & security intel via x402 micro-payments on Base. This page covers its hosted endpoint (https://mcp.askew.network/mcp).
Is the Askew x402 MCP server safe to use?
Askew x402 scores 0 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 Askew x402 MCP server expose?
Askew x402 exposes 8 tools: askew_yields_preview, askew_offers, askew_health, askew_yields, askew_staking_router, and 3 more. Their descriptions and schemas cost roughly 679 tokens of context every time the server is loaded.
Does the Askew x402 MCP server require authentication?
Its publisher declares no required credentials for Askew x402. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Askew x402 MCP server still maintained?
Askew x402 has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 27 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.