3 monitored services5 min check interval288 bars per serviceProduction monitor
Recorded availability
Service history
Each bar = 5 minutes · Hover, focus or tap
News API
RESTID: api
Unknown
GET /api/v2/newsNews read + cursor validation
No check result is available yet.
24 hours agoLoading checks…Latest
— healthy observed checksProbe duration —
Service details
Checks a real NVIDIA news response, its freshness field and follow-up cursor.
Service ID
api
Check method
News read + cursor validation
Last observation
Not recorded
Recorded windows
0 of 288
Degraded / unavailable
0 / 0
Unknown windows
0
Agent connection
MCPID: mcp
Unknown
POST /api/mcpInitialize + newsbeat_brief
No check result is available yet.
24 hours agoLoading checks…Latest
— healthy observed checksProbe duration —
Service details
Checks protocol initialization, then calls the news briefing tool.
Service ID
mcp
Check method
Initialize + newsbeat_brief
Last observation
Not recorded
Recorded windows
0 of 288
Degraded / unavailable
0 / 0
Unknown windows
0
News collection
INGESTIONID: ingestion
Unknown
/api/cron/ingestCatalog-wide freshness
No check result is available yet.
24 hours agoLoading checks…Latest
— healthy observed checksProbe duration —
Service details
Reads collection records for every supported topic against its own freshness window. Collection is scheduled every 15 minutes.
Service ID
ingestion
Check method
Catalog-wide freshness
Last observation
Not recorded
Recorded windows
0 of 288
Degraded / unavailable
0 / 0
Unknown windows
0
Operational Degraded Unavailable No check / unknown
Times shown in UTC. Healthy percentages use observed checks only; missing windows stay unknown. On narrow screens, scroll the bars horizontally. Use the arrow keys to move between checks and Escape to close their details.
What these checks mean
Every five minutes, Rarebird tests a news API request and an MCP news lookup, then checks the last successful collection time for every supported topic.
Freshness, clearly stated
A topic is fresh when its last successful check falls within its configured refresh window. A successful check can return no headlines. Delayed collection is shown separately from connection failures.
A record of observed checks
The feed contains automated check results, with up to 24 hours shown here. Missing or old checks mean status is unknown. Monitoring runs on Rarebird’s infrastructure and cannot independently verify a complete hosting outage.