Use case · Server author
Hand your users a tool, not a README.
MCPOrbit is the path of least resistance from 'I built an MCP server' to 'people use my MCP server.' Publish a Server Card; users paste your URL; tools run in seconds.
The 60-second demo
Faster than typing 'npm install'.
The fastest way to onboard someone to your server: tell them to install MCPOrbit (free, signed, no account), paste your domain, and click your tool. They see your output in real time. They didn't read your README. They didn't write a config file.
Distribution
Server Cards as your install path.
Drop a .well-known/mcp.json on your domain. Every MCPOrbit user pointed at your domain discovers your server automatically. No registry submission, no approval queue.
- Single source of truth
- Multiple servers per domain
- Works for private MCP servers behind a VPN
- Spec-aligned (SEP-1649)
Read the deep-dive
Server Cards · SEP-1649 →The first decentralised discovery layer for MCP. We ship it; you own the file.
Drift testing as a developer aid
Catch your own breaking changes before your users do.
Use MCPOrbit's drift workflow against your own server during development. Snapshot a build, change something, see exactly what your downstream consumers will see change.
Drift workflow
Agent panel & drift testing →Baseline → re-run → diff. Your CI is downstream of this workflow.
The shape of it
Build server
Implement your MCP server in any language.
Publish Server Card
Drop the .well-known/mcp.json file.
Demo via MCPOrbit
Anyone with the app discovers and runs it.
Iterate on real feedback
Drift-test your changes locally first.
