
Askew x402
io.github.rubix1138Published by GitHub account rubix1138v0.1.0Updated Oct 24, 2026
DeFi yields, staking routing, semantic research & security intel via x402 micro-payments on Base
Overview
Remote MCP server exposing Askew's paid x402 endpoints for DeFi yields, staking routing, semantic research and security threat intel, paid in USDC on Base.
- What you can do
- Preview best DeFi yields per chain and browse the paid endpoint catalog with pricing and sample calls, plus check service status, wallet address and current pricing for free. Buy live yield comparisons across five chains with APY, TVL and project names. Get staking routing recommendations comparing native proof-of-stake against liquid staking for SOL and ATOM. Run semantic search over Askew's agent-economy research findings, insights and experiments. Retrieve recent security threat entries (auth failures, disk/network anomalies, crypto alerts) or a combined feed of research, threats and staking APY.
- When to use it
- Useful when an assistant needs live DeFi yield or staking data, Askew's research corpus, or security telemetry, and the user is willing to pay small per-call fees in USDC on Base. Start with the free preview and catalog tools to judge whether the paid data is worth it.
- Requirements
- A remote streamable-http endpoint; no local runtime or API key for the direct path. Paid tools require an x402-capable client with a wallet holding USDC on Base mainnet, or an xpay.tools key passed as a query parameter for the proxied path. Network access to the endpoint.
Installation
In SourceWeft
- Open Askew x402 in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.rubix1138%2Faskew-x402/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"askew-x402": {
"type": "http",
"url": "https://mcp.askew.network/mcp"
}
}
}README
Askew x402 MCP Server
An MCP (Model Context Protocol) server that exposes Askew's x402 monetised endpoints as callable tools. Agents and MCP clients get structured access to live DeFi yields, staking routing, semantic research search, and security threat intelligence — with micro-payments handled via the x402 protocol on Base mainnet.
Two ways to reach the same 8 tools:
Health check: https://mcp.askew.network/healthz (GET/HEAD → {"status":"ok"})
Canonical source:
git.ashe.website/Askew/Askew— themcp/directory is the authoritative source. This GitHub repo is a discovery mirror only so that Glama, Smithery, and mcp.so can index it. Code here may lag the canonical repo by a commit or two.
Tools (8 total — 3 free, 5 paid)
Free tools (no payment required)
Paid tools (USDC on Base mainnet via x402)
Paid tools return the x402 payment-required envelope when unpaid — x402-aware MCP clients (using the paidTool primitive from @coinbase/x402) can autopay; vanilla MCP clients see the price and payment requirements and know what to do next.
Adding to Claude Desktop
Direct (self-sovereign x402):
Proxied via xpay.tools (uses your xpay credit balance):
Direct MCP connection
The server speaks the MCP streamable-http transport. Any MCP client that supports remote streamable-http servers can connect directly:
Pricing & payment
All paid tools use x402 — a IETF-inspired HTTP payment protocol built on USDC on Base mainnet. No API key required; payment is handled at the HTTP layer.
- Payment token: USDC on Base mainnet
- Price range: $0.002–$0.005 per call
- x402 version: 2 (header:
X-Payment-Required)
The receiving wallet address is returned by the askew_health tool and the askew_offers catalog.
About Askew
Askew is an autonomous agent ecosystem running 20+ specialised agents (research, DeFi, social, security) on a self-hosted server. The x402 endpoints monetise live data the agents produce: yield scans, staking recommendations, security telemetry, and semantic research.
More at git.ashe.website/Askew/Askew.
Source: README.md at commit 1ef864f
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts