sF1nX/x402station
by Various
MCP adapter (x402station-mcp on npm) + AgentKit action provider + consumer-side demo agent for x402station — pre-flight oracle for x402 endpoints. Backend (signal logic, ingest pip
MCP
sF1nX/x402station
Added 1 June 2026
Overview
sF1nX/x402station is a developer tool that provides an MCP adapter (x402station-mcp on npm) and an AgentKit action provider for interacting with x402 endpoints. It includes a consumer-side demo agent and a private backend for signal logic, ingest pipeline, and probe history.
Best for
Best for
Developers building MCP-compatible agents or AgentKit actions that need to validate x402 endpoints before use.
Use cases
- Integrate x402 endpoint pre-flight checks into MCP-compatible agents
- Build consumer-side agents that probe x402 endpoints before use
- Extend AgentKit with x402 action providers for automated endpoint validation
Notes
sF1nX/x402station is a developer tool that provides an MCP adapter (x402station-mcp on npm) and an AgentKit action provider for interacting with x402 endpoints. It includes a consumer-side demo agent and a private backend for signal logic, ingest pipeline, and probe history.
0 stars on GitHub. Last updated 2026-05-11. Licensed MIT.
Use cases
- Integrate x402 endpoint pre-flight checks into MCP-compatible agents
- Build consumer-side agents that probe x402 endpoints before use
- Extend AgentKit with x402 action providers for automated endpoint validation
Pros
- Provides a ready-to-use MCP adapter for x402 endpoints
- Includes both backend logic and consumer-side demo agent
- Supports integration with AgentKit for broader automation
Cons
- Backend components are private, limiting full customization
- Zero stars on GitHub suggests early-stage or low adoption
- Documentation and community support may be minimal
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Provides a ready-to-use MCP adapter for x402 endpoints
- Includes both backend logic and consumer-side demo agent
- Supports integration with AgentKit for broader automation
Cons
- Backend components are private, limiting full customization
- Zero stars on GitHub suggests early-stage or low adoption
- Documentation and community support may be minimal