Publishing a server
A listing pins a server's manifest hash, its endpoint and its price. On day one the house curator pins official servers; a publisher can take its listing over.
What a listing is
{ serverId, publisher domain, endpoint, manifestHash, price per call (cr), curator signature }Official listings
Official third-party servers are free listings: Daemon does not meter or charge for them, and they are still pinned, probed and stakeable. Each is the publisher's own server, checked by the builder at listing.
| Listing | Publisher | Price | Endpoint |
|---|---|---|---|
| GitHub | GitHub | free | https://api.githubcopilot.com/mcp/ |
| Supabase | Supabase | free | https://mcp.supabase.com/mcp |
| Blockscout | Blockscout | free | https://mcp.blockscout.com/mcp |
| quotes | Daemon (house) | 1 cr | /mcp/quotes |
| filings | Daemon (house) | 2 cr | /mcp/filings |
| infer | Daemon (house) | 2 cr per 1k tokens | /mcp/infer |
| fetch | Daemon (house) | 1 cr | /mcp/fetch |
A listing reads "official server by GitHub, pinned and probed by Daemon". It is not an affiliation.
Claiming a listing
A publisher claims its listing by serving /.well-known/daemon.json with its address on its own domain. From then its signature replaces the curator's, and the payout for its paid tools goes to it. The claim flow ships in the second release; until then, write to the Daemon account on X and the curator moves the listing by hand.
Pricing a tool
Prices are whole cr per call. The publisher receives 95% of every paid call. The other 5% is the protocol fee, split as on the payments page.