The status badge
Every listing serves a shields-style SVG at
https://mcpi.app/servers/<slug>/badge.svg, stating the last probe's verdict
— connects, warnings, blockers, or not probed. Drop it in a README:
[](https://mcpi.app/servers/<slug>)The same snippet is shown ready to copy on the listing page itself.
The badge is cached for an hour and the probe runs every six — so it can be up to seven hours behind the endpoint. It states the probe's last recorded verdict, nothing fresher.
Feeds
Every classified contract change is subscribable:
| Feed | What it carries |
|---|---|
https://mcpi.app/servers/<slug>/feed.xml |
One listing's contract changes — first recordings and every classified change |
https://mcpi.app/servers/feed.xml |
The directory-wide river: the newest 50 changes, each entry named after its server |
Entries state the classification first — "1 breaking", "2 compatible" — with the affected items named inside. Entry ids are pinned to the recorded snapshots, so a feed rebuild never re-announces old history.
The same river renders as a page at /changes, and each listing page links its own feed. Point a feed reader, a Slack RSS app, or a CI watcher at the listing feed and you find out about a breaking change before your users do.