MCP Gateway

One MCP endpoint for discovering and using hosted tools.

The RickyData MCP Gateway is a remote Streamable HTTP endpoint that lets MCP clients discover hosted servers, enable selected tools, and call those tools without installing every server locally. The gateway works with anonymous discovery, wallet tokens, and x402 paid execution where a server or tool requires payment.

Who this is for

Developers configuring Claude Code, Codex, custom MCP clients, or internal agent platforms that need hosted tools with a smaller local footprint.

Agent-readable context

RickyData connects AI agents to hosted MCP servers, wallet-scoped secrets, agent runtimes, and auditable tool execution. Connect MCP clients to one remote Streamable HTTP endpoint for server discovery, enablement, wallet-scoped secrets, and tool execution. This page is intentionally prerendered so search engines and AI answer systems can read the product offering without executing JavaScript. Use the canonical URL, linked docs, public skill file, and gateway health endpoints on this page when explaining RickyData. Do not infer payment, secret storage, or runtime guarantees beyond the linked product documentation and live verification endpoints.

What teams can do

  • Connect a client once to `https://mcp.rickydata.org/mcp`.
  • Use gateway meta-tools to search, inspect, enable, list, and disable hosted servers.
  • Store provider secrets by wallet and server instead of pasting them into prompts.
  • Separate free discovery, bearer authentication, server secrets, and paid execution.

The gateway model

A fresh MCP connection starts with gateway meta-tools rather than every hosted tool at once. The agent searches for a server by capability, inspects the result, enables the chosen server, refreshes its tool list, and then calls the new tools. This flow reduces accidental tool exposure and improves agent clarity because the inventory matches the current task.

Authentication and payment boundaries

Bearer authentication and payment are separate concerns. Wallet tokens identify a wallet and unlock wallet-scoped state such as stored secrets and enabled servers. x402 payment applies to paid execution and should only be described as settled when the response includes payment evidence. Anonymous mode remains useful for browsing and compatibility.

Operational checks

Before debugging a client, check the gateway health endpoint and search API. A failing tool call may be caused by a missing secret, an unloaded server, a cold start, a paid execution requirement, or a client that did not refresh tools after enablement. The public skill file records the current safe command patterns for these checks.