Biorhythm MCP Server by RoxyAPI
REMOTE · ROXYAPI.COM · SCANNED SEP 20
Biorhythm cycles, forecasts, critical days and compatibility for AI agents, one API key.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1686 tokens (~281/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Biorhythm MCP Server by RoxyAPI server?
Biorhythm MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/mcp/biorhythm, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · roxyapi.com
claude mcp add --transport http com-roxyapi-biorhythm 'https://roxyapi.com/mcp/biorhythm'
{
"mcpServers": {
"com-roxyapi-biorhythm": {
"url": "https://roxyapi.com/mcp/biorhythm"
}
}
} {
"servers": {
"com-roxyapi-biorhythm": {
"type": "http",
"url": "https://roxyapi.com/mcp/biorhythm"
}
}
} [mcp_servers.com-roxyapi-biorhythm] url = "https://roxyapi.com/mcp/biorhythm"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-roxyapi-biorhythm": {
"type": "remote",
"url": "https://roxyapi.com/mcp/biorhythm",
"enabled": true
}
}
} openclaw mcp add com-roxyapi-biorhythm --url 'https://roxyapi.com/mcp/biorhythm' --transport streamable-http
mcp_servers:
com-roxyapi-biorhythm:
url: "https://roxyapi.com/mcp/biorhythm" {
"McpServers": {
"com-roxyapi-biorhythm": {
"Transport": "http",
"Url": "https://roxyapi.com/mcp/biorhythm"
}
}
} assistant mcp add com-roxyapi-biorhythm -t streamable-http -u 'https://roxyapi.com/mcp/biorhythm'
{
"mcpServers": {
"com-roxyapi-biorhythm": {
"type": "http",
"url": "https://roxyapi.com/mcp/biorhythm"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 0
- Authorization: unverified → partial ▲ security
- Schema quality: 325 → 263 ▲ functional
- Schema quality: fail → pass ▲ functional
- “post_biorhythm_compatibility” reworded the description of “compact” cosmetic
- “post_biorhythm_critical_days” reworded the description of “compact” cosmetic
- “post_biorhythm_daily” reworded the description of “compact” cosmetic
- “post_biorhythm_forecast” reworded the description of “compact” cosmetic
- “post_biorhythm_phases” reworded the description of “compact” cosmetic
- “post_biorhythm_reading” reworded the description of “compact” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://roxyapi.com/mcp/biorhythm
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roxyapi.com | CN=WE1,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | fb04ac30ca01abb60e3558bdfadfe2f4 |
| SANs: roxyapi.com, *.roxyapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of roxyapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roxyapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'inline-speculation-rules' 'unsafe-eval' https://challenges.cloudflare.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; img-src 'self' data: https:; font-src 'self' https://fonts.scalar.com; connect-src 'self' https://api.scalar.com https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src https://challenges.cloudflare.com https://roxyapi.github.io; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), usb=(), bluetooth=(), accelerometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roxyapi.com/mcp/biorhythm | Verified | 200 | |
| http (plaintext) | http://roxyapi.com/mcp/biorhythm | HTTPS enforced | 301 | https://roxyapi.com/mcp/biorhythm |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
post_biorhythm_compatibility Calculate compatibility - Biorhythm alignment between two people ~263
Calculate biorhythm compatibility between two people by overlaying their cycle profiles on a target date. Returns per-cycle alignment scores (0-100) for physical, emotional, and intellectual cycles, an overall compatibility score, relationship rating, strengths, challenges, practical advice, and a daily sync snapshot showing the absolute difference in each primary cycle. Perfect for dating apps, relationship platforms, team-building tools, and couples coaching applications.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| lang | string | – | Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E… |
| person1 | object | yes | – |
| person2 | object | yes | – |
| targetDate | string | – | Date to evaluate compatibility on in YYYY-MM-DD format. Defaults to today (UTC). Compatibility varies by day since biorhythm cycles are continuous. |
No output schema declared.
{"person1":{"birthDate":"1990-07-15"},"person2":{"birthDate":"1992-03-22"}}post_biorhythm_critical_days Find critical days - Zero crossing detection for any date range ~299
Find all critical days (zero crossings) within a date range up to 180 days. Returns each critical day with cycle name, period, direction (ascending or descending), severity (single, double, or triple), and advisory text. Highlights rare double critical days where two primary cycles cross zero simultaneously and extremely rare triple critical days where all three primary cycles cross zero on the same date. Ideal for calendar integrations, push notification systems, alert engines, and wellness scheduling tools.
| Name | Type | Req | Description |
|---|---|---|---|
| birthDate | string | yes | Birth date of the person in YYYY-MM-DD format. |
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| endDate | string | – | End date of the search range in YYYY-MM-DD format. Defaults to startDate + 90 days. Maximum range: 180 days. |
| lang | string | – | Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E… |
| startDate | string | – | Start date of the search range in YYYY-MM-DD format. Defaults to today (UTC). |
No output schema declared.
{"birthDate":"1990-07-15"}post_biorhythm_daily Get daily biorhythm - Seeded reading for daily check-in features ~307
Get a daily biorhythm reading with seeded randomness for consistent "biorhythm of the day" features. Same seed and same date always produce the same reading, perfect for daily push notifications, morning briefings, and wellness app check-ins. Returns energy rating, overall phase, a spotlight on one featured cycle, quick-read values for all three primary cycles, a daily message, and actionable advice. The spotlight cycle is deterministically selected by the seed, creating variety across users while maintaining consistency for each individual.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| date | string | – | Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones. |
| lang | string | – | Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E… |
| seed | string | – | Optional seed for reproducible readings. Same seed + same date = same reading every time. Pass any unique identifier (userId, email hash, session token). Omit for anonymous daily readings. |
No output schema declared.
{}post_biorhythm_forecast Get biorhythm forecast - Multi-day cycle predictions with best and worst days ~284
Generate a biorhythm forecast for a date range up to 90 days. Returns daily cycle values for physical, emotional, intellectual, and intuitive cycles, daily energy ratings, critical day identification, and a summary with best day, worst day, average energy, and period-level guidance. Ideal for wellness apps, productivity planners, scheduling tools, and calendar integrations that need forward-looking biorhythm data.
| Name | Type | Req | Description |
|---|---|---|---|
| birthDate | string | yes | Birth date of the person in YYYY-MM-DD format. |
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| endDate | string | – | End date of the forecast range in YYYY-MM-DD format. Defaults to startDate + 30 days. Maximum range: 90 days. |
| lang | string | – | Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E… |
| startDate | string | – | Start date of the forecast range in YYYY-MM-DD format. Defaults to today (UTC). |
No output schema declared.
{"birthDate":"1990-07-15"}post_biorhythm_phases Get phase info - Lightweight cycle status for dashboards and widgets ~252
Get current phase information for all 10 biorhythm cycles without the full interpretation payload. Returns value, phase name, phase label, day position within cycle, cycle period, days until next critical crossing, and short-term trend for each cycle. Includes a compact summary string. Designed as a lightweight endpoint for dashboards, widgets, status bars, and quick-check interfaces that need biorhythm phase data without editorial text.
| Name | Type | Req | Description |
|---|---|---|---|
| birthDate | string | yes | Birth date of the person in YYYY-MM-DD format. |
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| lang | string | – | Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E… |
| targetDate | string | – | Date to get phase information for in YYYY-MM-DD format. Defaults to today (UTC). |
No output schema declared.
{"birthDate":"1990-07-15"}post_biorhythm_reading Get biorhythm reading - Complete cycle analysis for any date ~281
Calculate a complete biorhythm reading for a given birth date and target date. Returns all 10 cycle values (physical, emotional, intellectual, intuitive, aesthetic, awareness, spiritual, passion, mastery, wisdom), phase detection with 8 distinct states, energy rating (1-10), overall phase assessment, editorial-grade interpretation, actionable advice, and critical day alerts. Perfect for wellness apps, dating platforms, productivity tools, and AI chatbot integrations that need structured biorhythm data.
| Name | Type | Req | Description |
|---|---|---|---|
| birthDate | string | yes | Birth date of the person in YYYY-MM-DD format. This is the anchor for all biorhythm cycle calculations. |
| compact | boolean | – | Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens. |
| lang | string | – | Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E… |
| targetDate | string | – | Date to calculate the reading for in YYYY-MM-DD format. Defaults to today (UTC) if omitted. |
No output schema declared.
{"birthDate":"1990-07-15"}What is the Biorhythm MCP Server by RoxyAPI server?
Biorhythm MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/biorhythm. Biorhythm cycles, forecasts, critical days and compatibility for AI agents, one API key. This page covers its hosted endpoint (https://roxyapi.com/mcp/biorhythm).
Is the Biorhythm MCP Server by RoxyAPI server safe to use?
Biorhythm MCP Server by RoxyAPI scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Biorhythm MCP Server by RoxyAPI server expose?
Biorhythm MCP Server by RoxyAPI exposes 6 tools: post_biorhythm_reading, post_biorhythm_forecast, post_biorhythm_critical_days, post_biorhythm_compatibility, post_biorhythm_phases, post_biorhythm_daily. Their descriptions and schemas cost roughly 1,686 tokens of context every time the server is loaded.
Does the Biorhythm MCP Server by RoxyAPI server require authentication?
No. We connected to Biorhythm MCP Server by RoxyAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Biorhythm MCP Server by RoxyAPI server still maintained?
Biorhythm MCP Server by RoxyAPI is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.