Marketplace Overview
The RickyData Marketplace is the web interface for browsing MCP servers, managing your tool inventory, and chatting with AI agents.
URL: marketplace.rickydata.org
What you can do
| Feature | Auth required | Cost |
|---|---|---|
| Browse servers and tools | No | Free |
| Search by name or category | No | Free |
| View server details, tools, verification status | No | Free |
| Enable/disable servers | Yes (wallet) | Free |
| Store API keys for servers | Yes (wallet) | Free |
| Chat with agents | Yes (wallet + BYOK) | Pay-per-use |
| View wallet balance and transactions | Yes (wallet) | Free |
| Manage spending budgets | Yes (wallet) | Free |
Server discovery
The marketplace indexes servers from multiple registries (npm, PyPI, Docker, Git). Each server listing shows:
- Name and description — what the server does
- Tool count — number of tools available
- Registry — where the package comes from
- Verification tier —
tools_listedortool_smoke_passed - Categories — browseable groupings
- Secrets required — whether the server needs API keys
Verification tiers
| Tier | Meaning | Trust level |
|---|---|---|
tools_listed | Server started successfully and its tools were enumerated | Basic — server runs |
tool_smoke_passed | At least one tool probe executed successfully | Higher — tools actually work |
Continuous discovery workflows periodically re-verify servers and update the marketplace.
Security trust chain
The marketplace includes a security verification page at marketplace.rickydata.org/security that calls real gateway endpoints and shows:
- AMD SEV-SNP attestation status
- Code hash integrity (runtime vs published)
- Build provenance (git commit, image digest)
- Key source verification (vTPM PCR-bound)
- Cross-gateway trust state
Every claim is independently verifiable — you never need to trust the gateway itself.
Authentication
The marketplace uses wallet-based authentication via Privy:
- Click Connect Wallet in the header
- Sign in with email, Google, GitHub, Discord, or any Web3 wallet
- Your wallet address becomes your identity
All secrets, enablement state, budgets, and sessions are scoped to your wallet.
Architecture
The Marketplace UI is a thin client that talks to the MCP Gateway API, which in turn reads from the server registry index.
Marketplace UI → MCP Gateway API → Server Registry Index
↑
TEE (AMD SEV-SNP)
Key architectural details:
- The MCP Gateway runs inside a Trusted Execution Environment (AMD SEV-SNP). Your API keys and secrets never leave the enclave — not even RickyData operators can read them.
- Servers are proxied through the gateway, not run on your local machine. When you call a tool, the gateway spins up the server process inside the TEE, executes the call, and returns the result.
- Every tool call is metered and logged per-wallet. You can inspect your usage history and spending from the wallet dashboard.
- The gateway verifies server integrity on every boot using code-hash attestation, so you can confirm the server running your request matches the published source.
Pricing
RickyData uses a usage-based model with a generous free tier.
| Tier | Details |
|---|---|
| Free | 100 requests/day. Tool calls count as 0.25 requests each, so you get up to 400 tool calls/day at no cost. |
| Default model | MiniMax-M2.7 — included in the free tier for agent chat. |
| BYOK | Bring your own Anthropic or OpenAI API key to use premium models (Claude Sonnet/Opus, GPT-4o, etc.). Model costs are billed directly by the provider. |
| USDC billing | Usage beyond the free tier is billed in USDC from your wallet balance. Top up via the wallet dashboard. |
| Spending budgets | Set daily or monthly caps per-wallet to avoid surprises. Configurable from the Marketplace UI or via the CLI. |
Quick tour
Here is a walkthrough of the core Marketplace flow:
- Browse — open the Marketplace and search by name, or filter servers by category (data, dev tools, finance, etc.).
- Inspect — click a server to view its tool list, verification tier, description, and any secrets it requires (e.g., an API key).
- Enable — toggle the server on. It appears in your active tool list immediately. If the server needs secrets, you will be prompted to enter them — they are stored encrypted inside the TEE.
- Chat — open the playground (or use Claude Code locally) and start using the enabled tools. The agent will automatically see your active servers and can call their tools on your behalf.
Next steps
- UI Operations — how to use the web interface
- Server Publishing — publish your own MCP servers