Pricing
The paywall is on capability, not on how many servers you run. Adding more targets costs us fractions of a cent, so charging by the target would punish the maintainers who publish the most — and they're the ones worth the most to this product.
What changes between tiers is check frequency and what a claim comes with — not which checks run (every tier runs the same ones), and not how many targets you're allowed to have data on.
Indie exists for one reason: to know before your users do.
Every tier: 15 protocol checks in four states, signed attestations (verifiable against the published public keys), a public report page with 90-day availability history, a listing in the directory, and answers through our MCP endpoint.
Any public MCP server, checked without anyone signing in.
- Targets
- Not included
- Remote check frequency
- every 12 hours
- README badge
- static "observed"
- Alert emails
- Not included
- Report page ownership
- public, unowned
- Servers you can follow
- Not included
- Billing
- Not included
Claim your own server — checks every 8 hours once it's yours.
- Targets
- 1
- Remote check frequency
- every 8 hours
- README badge
- static "claimed"
- Alert emails
- unreachable or protocol check failed (once two runs in a row find it) · recovered · daily digest
- Report page ownership
- yours, listed in your account
- Servers you can follow
- 10
- Billing
- Not included
For maintainers who want to know before their users do.
- Targets
- 10 (subscription quantity adjustable — 2× = 20, 3× = 30)
- Remote check frequency
- 15 minutes
- README badge
- live if the latest check is signed: state + time; otherwise static "claimed"
- Alert emails
- same, checked every 15 minutes
- Report page ownership
- same
- Servers you can follow
- 50
- Billing
- Stripe; manage from your account
Requires a claimed server — claim first, then upgrade in one click.
interval=year · quantity=1
Billing runs through Stripe. Signing in doesn't charge you — you'll see the actual checkout step before anything is billed.