Biorhythm API with 10 cycle types. Daily, forecast, critical days, compatibility
Biorhythm API with 10 cycle types. Daily, forecast, critical days, compatibility. Working code samples. RoxyAPI single key.
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://roxyapi.com/mcp/biorhythm |
|---|---|
| Source | https://github.com/RoxyAPI/biorhythm-api |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-07-08 19:11:50 |
| Last checked | 2026-11-17 21:44:53 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 351 / 624 ms |
| Last successful check | 2026-11-17 21:44:53 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
post_biorhythm_reading— Calculate a complete biorhythm reading for a given birth date and target date. Returns all 10 cycle values (physical, emotional, intellectuapost_biorhythm_forecast— Generate a biorhythm forecast for a date range up to 90 days. Returns daily cycle values for physical, emotional, intellectual, and intuitivpost_biorhythm_critical_days— Find all critical days (zero crossings) within a date range up to 180 days. Returns each critical day with cycle name, period, direction (aspost_biorhythm_compatibility— Calculate biorhythm compatibility between two people by overlaying their cycle profiles on a target date. Returns per-cycle alignment scorespost_biorhythm_phases— Get current phase information for all 10 biorhythm cycles without the full interpretation payload. Returns value, phase name, phase label, dpost_biorhythm_daily— Get a daily biorhythm reading with seeded randomness for consistent "biorhythm of the day" features. Same seed and same date always produce
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:44:53 | ✓ | ✓ | 432 ms | 90 | active |
| 2026-11-17 21:29:48 | ✓ | ✓ | 338 ms | 90 | active |
| 2026-11-17 21:14:35 | ✓ | ✓ | 321 ms | 90 | active |
| 2026-11-17 20:59:16 | ✓ | ✓ | 336 ms | 90 | active |
| 2026-11-17 20:44:16 | ✓ | ✓ | 328 ms | 90 | active |
| 2026-11-17 20:29:14 | ✓ | ✓ | 427 ms | 90 | active |
| 2026-11-17 20:14:09 | ✓ | ✓ | 690 ms | 90 | active |
| 2026-11-17 19:56:17 | ✓ | ✓ | 370 ms | 90 | active |
| 2026-11-17 19:41:10 | ✓ | ✓ | 595 ms | 90 | active |
| 2026-11-17 19:25:51 | ✓ | ✓ | 331 ms | 90 | active |
| 2026-11-17 19:10:47 | ✓ | ✓ | 370 ms | 90 | active |
| 2026-11-17 18:55:40 | ✓ | ✓ | 435 ms | 90 | active |
| 2026-11-17 18:40:34 | ✓ | ✓ | 361 ms | 90 | active |
| 2026-11-17 18:25:28 | ✓ | ✓ | 361 ms | 90 | active |
| 2026-11-17 18:10:12 | ✓ | ✓ | 337 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://roxyapi.com/mcp/biorhythm") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/roxyapi-com-mcp-biorhythm # JSON