Askew X402

Created By
Askew2 months ago
MCP wrapper for Askew's x402 endpoints — 8 tools (3 free, 5 paid in USDC on Base): live DeFi yield comparison, SOL/ATOM staking routing, agent-economy research search, Guardian security threat intel, and a combined strategic feed.
Overview

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.

Live endpoint: https://mcp.askew.network/mcp (POST, streamable-http transport) Health check: https://mcp.askew.network/healthz (GET/HEAD → {"status":"ok"})

Canonical source: git.ashe.website/Askew/Askew — the mcp/ 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)

ToolDescription
askew_yields_previewFree preview: best DeFi yield per chain (Solana, Cosmos, Ethereum, Base, Arbitrum). Use before buying the full yields tool.
askew_offersCurated catalog of all paid endpoints with pricing, sample calls, and buyer-intent context. Best starting point for exploring what's available.
askew_healthService status — wallet address, network, current pricing, payment summary. Confirms the service is operational before making paid calls.
ToolPriceDescription
askew_yields$0.002Live DeFi yield comparison across 5 chains. Top 5 pools per chain with APY, TVL, and project name. Data from DefiLlama, cached up to 6h.
askew_staking_router$0.003Staking yield router for SOL and ATOM. Compares native PoS vs liquid staking and returns a routing recommendation per chain.
askew_research_query$0.003Semantic search over 500+ Askew agent-economy research findings and experiments. Powered by ChromaDB vector search, updated every 12h. Collections: research_findings, agent_insights, experiments. Requires q parameter.
askew_intel_threats$0.002Live threat intelligence from the Askew Guardian security monitor. Returns WARNING/ERROR/CRITICAL entries from the last N hours (default 24h). Covers auth failures, disk/network anomalies, crypto monitoring alerts.
askew_intel_feed$0.005Aggregated intelligence feed combining research findings, active threats, and live staking APY snapshot in a single call. Replaces three separate calls.

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

Add this snippet to your claude_desktop_config.json:

{
  "mcpServers": {
    "askew-x402": {
      "command": "mcp-remote",
      "args": ["https://mcp.askew.network/mcp"]
    }
  }
}

Or with mcp-remote via npx:

{
  "mcpServers": {
    "askew-x402": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.askew.network/mcp"]
    }
  }
}

Direct MCP connection

The server speaks the MCP streamable-http transport. Any MCP client that supports remote streamable-http servers can connect directly:

POST https://mcp.askew.network/mcp
Content-Type: application/json

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.

Server Config

{
  "mcpServers": {
    "askew-x402": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.askew.network/mcp"
      ]
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
Askew
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Atomic Chat

a day ago
Picsart Genai MCP
@Picsart

**Picsart MCP — 150+ AI Models for Images, Video & Audio, One Connection** Picsart's AI Playground brings together more than 150 generative AI models from 24+ providers into one place. The MCP server is the developer and agent interface to that playground — a single connection that gives any AI agent or coding assistant the ability to generate images, video, audio, and text without managing a tangle of separate API keys, billing accounts, or SDKs. **What it generates** - **Images** — Text-to-image, style transfer, AI upscaling, background removal, image enhancement. Powered by models including Flux and other leading image generation providers. - **Video** — Text-to-video and image-to-video generation with top-tier models: Sora, Kling, and Veo, with more added regularly. - **Audio** — Voice synthesis, sound generation, and audio creation via ElevenLabs and other audio providers. - **Text** — Creative copywriting, captions, and content generation integrated directly into multi-modal workflows. **Why it's different from calling model APIs directly** Most creative AI workflows end up routing through three or four separate APIs — one for image generation, another for video, another for voice. Each comes with its own pricing model, rate limits, and integration overhead. Picsart MCP collapses that into one connection. Pricing is pay-per-generation. No monthly model subscriptions stacked on top of each other — access to the full model library for what you actually use. Compared to maintaining individual subscriptions across the leading generative AI providers, that difference runs to several thousand dollars a year. **Works wherever agents work** Picsart MCP follows the Model Context Protocol standard, which means it plugs into any MCP-compatible environment: - **Claude Desktop** — Add to `claude_desktop_config.json`, restart, and your Claude sessions can generate media on demand. - **Claude Code** — Run `claude mcp add` or drop the config into `.mcp.json` in your project root. Works immediately in the CLI and in IDE-integrated sessions. - **Cursor** — Add to `.cursor/mcp.json`. Every Cursor agent and AI panel gets creative generation capabilities. - **ChatGPT** — Compatible via MCP-to-plugin bridge. - **Hermes, Cowork, and other agentic frameworks** — Any tool that supports MCP transport (Streamable HTTP or stdio) connects without modification. **Get started in under a minute** ```json { "mcpServers": { "picsart-gen-ai": { "type": "http", "url": "https://api.picsart.com/gen-ai/mcp" } } } ``` Add this block to your MCP client's config file, drop in your Picsart API key, and restart. The full model library is available immediately — no additional setup, no per-model configuration. **Built for agentic workflows** The tools exposed by Picsart MCP are designed to work as steps inside larger agent pipelines, not just one-off generation requests. A workflow might look like: agent receives a brief → generates a hero image with Flux → generates a short video loop with Kling → synthesizes a voiceover with ElevenLabs → returns all three assets in one pass. That entire sequence runs through a single MCP server, from a single API key, billed per generation. **Part of the Picsart AI Playground** The MCP server is one interface to Picsart's broader AI Playground — a platform that aggregates the world's leading generative AI models so creators, developers, and agents can access them without vendor lock-in. The Playground is also available via direct API and web UI for non-agent workflows.

7 hours ago
Penlog

a day ago