Back to search
20
MCP http

YieldAgentX402

fabianjefferson2/agentx402-mcp-server

Governed workflows with ShadeGuard-style checks on execution paths, x402 settlement on payment flows, Intel TDX attestation where the enclave path is used, and HMAC-SHA256 receipts with Filecoin + BTFS anchoring when uploads succeed. Resend and Supabase-backed skills for finance and CRM workflows. No wallets to manage, no keys to custody.

Watch this dependency

Get before/after evidence when observed tools, schemas, authentication access, availability or the endpoint changes.

Inspect evidence and set up a watch Share public evidence report
Uptime
0.0%
3 direct probes · 30d
Response
248ms
last probe
Tools
—
not inspected yet
Resources
0
readable
Prompts
0
available
Primary URL
https://yieldagentx402.app/mcp-server
Score: 20/100
Our probe could not complete the MCP handshake.
why this score
fail Answers the MCP handshake 10/50
initialize returned HTTP 200: initialize response missing JSON-RPC result.
How to earn +40 points
Return a valid initialize result
POST a JSON-RPC server/discover to the primary URL yourself (2026-07-28: stateless, with _meta and the Mcp-Method header); it must answer 200 with the supported versions, capabilities and serverInfo. Servers on earlier revisions answer initialize with protocolVersion, capabilities and serverInfo.
Docs →
n/a Lists tools, resources or prompts 0/30
Not scored: a catalogue only counts once the handshake succeeds.
n/a 3 or more catalogue items 0/10
Not scored: a catalogue only counts once the handshake succeeds.
pass Describes itself 10/10
340 characters; more than 30 earns these points.

How to use

Add to your Claude Desktop / Cursor / Cline MCP config:

{
  "mcpServers": {
    "yieldagentx402": {
      "url": "https://yieldagentx402.app/mcp-server",
      "transport": "http"
    }
  }
}