How we check
Badges come from automated checks, never from payment. A paid pin wears a separate Featured label and does not change these badges. Pricing · disclosure.
- Tested working
- A read-only test passed on a real account in the last 8 days.
- Online (sign-in required)
- The server answered and asked for sign-in, which is what a healthy private connector does. Not yet tested with a real account.
- Not yet tested
- Self-hosted or built-in. The project is active, but we have not run it on a real account yet.
- Stale
- No commits in 180+ days, or archived. It may still work, but expect rough edges.
- Down
- The endpoint or repository did not answer, or no longer exists.
Every 6 hours
- Hosted connectors: we send the standard MCP
initializehandshake to the public endpoint and record the reply and response time. A private connector answering "sign in first" is healthy. - Self-hosted connectors: we read the GitHub repository's last commit, archive flag and latest release. No commits in 180 days = Stale.
- Docs links: we confirm every setup page still loads.
Weekly (coming soon)
Read-only smoke tests on real accounts (e.g. "get vehicle state", "list entities"). Passing earns Tested working. We never run unlock, garage or alarm commands in tests.