Yieldagentx402 Sdks

What Fabio662/yieldagentx402-sdks MCP server does

Fabio662/yieldagentx402-sdks MCP server connects MCP-compatible AI clients to the YieldAgentX402 execution platform. The platform exposes 18 tools covering capability discovery, secure workflow execution, policy dry-runs, approvals, x402 payment settlement, receipt verification, attestation, and finance or CRM skill workflows.

Actions can target 18 networks, including Base, Ethereum, native Bitcoin, Starknet, NEAR, Solana, Stacks, BNB, Rootstock, Filecoin, Aptos, Sui, TON, Tron, XRPL, Stellar, and Algorand. The wallet model is custody-free: a NEAR MPC key authority derives EVM and Bitcoin addresses when needed, while Starknet uses its Stark curve preset. The platform states that private keys are not held by the gateway or worker.

How it works

The MCP package is a stdio wrapper around the YieldAgentX402 API. After installation, an MCP client starts the local process and uses its tools to communicate with the platform. The public discovery operation can be called without an API key and returns the available tools, chains, rate limits, fees, and supported runtime configurations.

For authenticated use, the platform provides an instant test key through POST /api/apply. The returned yax_test_* key has a 5 USD cap and expires after seven days; the README describes it as suitable for safe read-only tools. The platform also publishes an MCP endpoint, an x402 manifest, an MCP manifest, a status endpoint, a TEE report, and a wallet manifest.

Each call returns an HMAC-SHA256-signed receipt. Filecoin and BTFS are used for dual receipt anchoring, and Intel TDX TEE attestation is available for verification. x402 settlement applies a stated 0.25 percent protocol fee, represented as 25 basis points in the published manifest.

Setup and configuration

Install the MCP wrapper with npm:

npx -y agentx402-mcp-server

Add that command to the MCP client configuration for the client you use. The repository specifically lists Claude Desktop, Cursor, and Windsurf as supported destinations for the stdio wrapper. The source material does not specify an environment variable name or a complete client-specific configuration block, so credentials and other settings should be taken from the platform's MCP documentation or generated onboarding configuration.

The repository also contains separate packages for a typed TypeScript SDK, receipt and webhook verification, CrewAI wrappers, and LangChain wrappers. Those packages are related SDK distributions rather than additional tools exposed by the stdio server.

Tools and capabilities

Fabio662/yieldagentx402-sdks MCP server is suited to workflows that need:

• Capability discovery without signup
• Policy previews and dry-runs before execution
• Secure workflow execution with approval steps
• x402 payment settlement
• Signed receipt verification
• TEE attestation checks
• Cross-chain wallet and transaction operations
• Finance and CRM skill tools exposed through the platform

The public README identifies the discovery operation as yax_get_capabilities. It also documents one NEAR MPC authority for EVM and Bitcoin address derivation, rather than separate private-key storage for each network.

Limitations and notes

The repository contains public client libraries and integrations, but the gateway, ShadeGuard policy engine, TEE attestation implementation, orchestrator, and Filecoin/BTFS anchoring services are hosted in a separate private repository. As a result, deploying or modifying those platform components is outside the scope of this repository.

Public discovery does not require authentication, but authenticated or action-oriented workflows may require a platform-issued API key. The README documents a test key with limited value and lifetime rather than a general pricing plan. The 0.25 percent protocol fee applies to x402 settlement according to the published platform information.

The repository is licensed under MIT. The MCP wrapper depends on the availability of the YieldAgentX402 hosted platform and its supported chain infrastructure; the provided material does not describe an offline execution mode.