Add WarpPay402 MCP Gateway com.warppay402.api

[golfgolfgolf200]

Added a new server configuration for WarpPay402 MCP Gateway (com.warppay402.api), including endpoints, capabilities, payment protocols, and available tools.

Motivation and Context

This PR registers the WarpPay402 MCP Gateway with the official MCP registry so host applications and AI agent platforms can discover and invoke its Web3 intelligence and developer tools.

How Has This Been Tested?

Tested end-to-end against local diagnostic scripts, SSE transport handshakes (https://api.warppay402.com/mcp?v=2), JSON-RPC tools/list method execution, and x402 v2 payment challenge probes across Base, Solana, Arbitrum, and Arc Mainnet.

Breaking Changes

None.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

• Server ID: com.warppay402.api
• Transport: SSE (https://api.warppay402.com/mcp?v=2)
• OpenAPI: https://api.warppay402.com/openapi.json
• Capabilities: 20 monetized tools supporting multi-chain x402 USDC micropayments and ERC-4337 v0.8 Paymaster quote requests.

[github-actions]

Hi @golfgolfgolf200 👋 — thanks for your interest in the MCP Registry!

It looks like this PR is trying to publish an MCP server by adding or editing server files in this repository (under servers/, data/servers/, or in data/seed.json). That isn't how servers get published, so I'm closing this PR automatically.

Servers are published with the mcp-publisher CLI, not by opening a pull request against this repo. The CLI verifies that you own your namespace and submits your server.json directly to the live registry API.

To publish your server, follow the Publishing Quickstart. In short:

# Build the publisher CLI
make publisher

# Authenticate (e.g. via GitHub) and publish your server.json
./bin/mcp-publisher login github
./bin/mcp-publisher publish

Note: data/seed.json is seed data for local development only — adding entries there does not publish anything to the registry.

If you believe this was closed in error, please leave a comment and a maintainer will take a look. 🙇

This is an automated message.