AgenticMarketServer Registry
Publish your MCP server on AgenticMarket so users can install it in one command and you earn revenue on every call.
If this is your first submission, review Publishing Server before filling the form.
Requirements
Before submitting your server, your MCP server must:
- Be accessible over a public HTTPS URL
- Follow the MCP specification — your server must respond to standard MCP messages
- Expose at least one tool that is discoverable by MCP clients
- Be live and reachable at the time of submission
For full details on what a valid MCP server looks like refer to the official MCP documentation.
Before submission, validate handshake and tool discovery in MCP Playground to avoid preventable review failures.
Submitting a server
Go to dashboard/submit and fill in the following:
For pricing strategy and payout behavior, read Monetization.
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Unique per your account. Lowercase, no spaces. Cannot be changed after publish. |
| Description | Yes | Short description shown in search and server cards. |
| Long description | Yes | Full documentation for your server. Markdown supported — treat it like a README. |
| MCP server URL | Yes | The public HTTPS endpoint of your MCP server. Cannot be changed after publish. Contact us via the contact page if you need to update it. |
| Category | Yes | Select the category that best fits your server. |
| Price per call | Yes | Set in cents. Minimum $0.03. Cannot be changed after publish — to change price you must publish a new listing. |
| Visibility | Yes | Listed (appears in marketplace) or Unlisted (only accessible via direct URL). Can be changed after publish. |
Price is permanent. Once set, price cannot be changed on an existing listing. This protects users from unexpected price changes. If you need a different price, publish a new server listing.
Review process
After submission your server enters a 24-hour review. We check:
- Title, description, and category are accurate and match the server's actual functionality
- MCP server is reachable and responds correctly to MCP standard messages
- Tools are properly exposed and discoverable
- Price is reasonable relative to what the server does
- Listing does not violate our Terms of Service
You will receive a dashboard notification when your server is approved.
If your server is rejected
If your server is rejected you will receive an email to your account address with:
- The specific reason for rejection
- Suggestions for what to fix or improve
You can resubmit after addressing the issues. Common reasons for rejection:
- Server not reachable or not following MCP standard
- Description does not match actual functionality
- Missing or incomplete tool definitions
- Terms of Service violation
Managing your server after publish
From your dashboard you can:
- Edit description and long description at any time
- Toggle your server between active and inactive — inactive servers return a clear unavailable message to users, your listing is preserved
- View call counts, installs, and earnings per server
The following cannot be changed after publish:
- Server name
- MCP server URL
- Price per call
For name or URL changes contact us.
Server URL format
Once approved your server is available at:
agenticmarket.dev/username/server-name
Share this URL to let users install your server directly.
You can also confirm how listings appear to users in the public server registry.
Verifying requests from AgenticMarket
When a user calls your server, AgenticMarket forwards the request to your server with the following headers:
x-agenticmarket-secret: <your-unique-secret>
x-request-id: <unique-id-per-request>
Content-Type: application/json
User-Agent: AgenticMarket-Proxy/1.0
Your x-agenticmarket-secret is unique to your server and is shown in your dashboard immediately after submission, including while the server is still in pending preview. Validate this header on every incoming request and reject anything without it. This ensures only requests routed through AgenticMarket reach your server.
The x-request-id is unique per call and can be used to correlate requests in your own logs.
