How to List Your MCP Server in Shatale's Catalog

TL;DR

• The Shatale Catalog is where AI agents discover MCP servers they can pay to use. Listing makes your server discoverable + collectible by agent traffic.
• Listing is a 6-field form + a review process. Approval typically lands in 2-3 business days.
• Position your listing on agent use-case ("travel booking", "premium financial data") not on company description ("we're a fintech startup").

The Shatale Catalog is the discovery layer for payment-enabled MCP servers. AI agents browse it to find tools they need — and then pay through Shatale to use them. Listing your MCP server in the catalog gets your server in front of every agent platform integrated with Shatale.

What does the listing process look like?

Six steps:

Sign up as a Publisher at admin.shatale.com.

Complete KYB — business verification, payout setup.

Build your MCP server with payment-enabled responses (see [How Payment-Enabled MCP Servers Work](/blog/mcp-payments-explained)).

Fill the listing form — 6 fields covering name, description, use cases, tools, pricing, and policy.

Submit for review.

Approval lands in 2-3 business days. Server is then discoverable in the catalog.

What's in the listing form?

Six fields. Each matters for discoverability and approval:

Server name

What agents will see. Be descriptive: "PremiumMarketData" beats "Acme MCP". 30 chars or less.

One-line description

The pitch. What does your server help an agent do? Lead with the verb. Example: "Get real-time stock quotes and historical data for any global market." 120 chars.

Use cases (1-3)

Concrete tasks an agent might perform with your server. Each ~50 chars. Example: "Look up historical prices for back-testing", "Stream live quotes for a watchlist", "Fetch fundamental data for company analysis."

Tool list

Each tool exposed by your MCP server. For each, name, parameters, return shape, and price. This is what shows up when agents browse your server's detail page.

Pricing model

Per-call, per-task, or subscription. With amounts. Currency.

Policy

Specifically: who can use this server (any agent? agents from approved publishers only? agents in specific jurisdictions?). And what data the server stores about agents (none? request logs? aggregate analytics?). Affects compliance review.

What gets reviewed?

Three areas:

1. Functionality. Does the MCP server actually work? Reviewers run a sandbox test of each listed tool to verify it responds correctly to MCP protocol calls and returns sensible data.

2. Pricing reasonableness. Pricing wildly out of line with similar servers gets flagged. Not because Shatale sets prices — but because predatory pricing damages catalog trust.

3. Compliance. What data does your server collect about agent users? Is it [GDPR](https://gdpr-info.eu)-compliant? PCI-relevant if it touches payment data? Reviewers check that policies match what the server actually does.

Most rejections are for: (1) MCP protocol incompatibility (server doesn't implement payment_required correctly), (2) unclear pricing, or (3) missing or inaccurate policy disclosure.

How do I get traffic once I'm listed?

Three ways agents find your server in the catalog:

Use-case browse. Agents (or their developers) filter by use case. Match your listing to the use cases agents are searching for.

Tool search. Agents search for specific tools (e.g. "stock quote API"). Specific tool names + clear descriptions surface.

Featured. Shatale features new and high-quality servers in newsletter + catalog homepage. Featured placement comes from quality + traction, not payment.

What about post-launch optimization?

Two metrics to watch in the Health Metrics dashboard:

• Discovery → call ratio. What % of agents who view your listing end up calling a tool? If this is low, your description / use cases / pricing are misaligned with agent needs.
• Call → success rate. Of agents who call a tool, what % get a successful response? If this is low, there's a bug in your server or your pricing is rejecting auth attempts.

Iterate on the listing fields and your server itself based on these. Re-submission for changes is faster than initial review (usually 1 business day).

What's the etiquette around pricing?

A few norms emerging in the catalog:

• Per-call for stateless tools (search, lookup, conversion). Typical range: $0.005 - $0.50 per call.
• Per-task for orchestration-heavy tools that involve multiple steps. Typical: $0.10 - $5 per task.
• Subscription for high-volume tools. Typical: $10-$500/month with included call quota.

Predatory low pricing (to dump-and-displace) gets flagged. Predatory high pricing (more than 3-5x comparable) also gets flagged.

FAQ

Is there a fee to list?

No. Shatale takes a platform fee on each transaction (currently 5% + $0.05). You pay nothing to list.

Can I list a server that's not payment-enabled?

The catalog is specifically for payment-enabled servers. For free MCP servers, use the public registry at github.com/modelcontextprotocol/servers.

Can I list multiple servers?

Yes. Each gets its own listing.

What if I want to update my listing?

Edit the fields and re-submit. Material changes (pricing, policy) trigger a re-review. Cosmetic changes (description tweaks) are usually auto-approved.

Who decides what shows up first when an agent searches?

A combination of relevance (does the tool match the search?), quality (success rate, response latency), and traction (call volume + ratings). No paid placement.

Related reading

• [How Payment-Enabled MCP Servers Work](/blog/mcp-payments-explained) — protocol mechanics
• [MCP Server Monetization](/blog/mcp-server-monetization) — pricing strategy + revenue patterns
• [The Publisher Developer Portal](/blog/publisher-developer-portal) — the dashboard you'll use

External references

• [Model Context Protocol specification](https://modelcontextprotocol.io) — the protocol your server speaks
• [MCP server registry](https://github.com/modelcontextprotocol/servers) — community-maintained list

---

By Ted L.. Last updated 2026-04-29.