mcp-registry/com.cosmicephemeris/mcp
As of 2026-10-26 18:53 UTC, the Cosmicephemeris MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
78 astrology calculations, Tarot, symbolic readings and Vedic calendars via two scoped MCP tools.
Point your MCP client at this streamable-http endpoint: https://api.cosmicephemeris.com/mcp
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
1 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
In the last 30 days: 0 tool(s) removed and 3 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.cosmicephemeris%2Fmcp/fixes
{
"name": "cosmicephemeris_calculate",
"description": "Run one live Cosmic Ephemeris calculation. The supplied API key must permit the selected operation. Each admitted call uses the route's normal quota and key-budget accounting; do not automatically retry failures.",
"inputSchema": {
"type": "object",
"required": [
"operation",
"input"
],
"properties": {
"input": {
"type": "object",
"description": "The exact JSON body for the selected operation at https://cosmicephemeris.com/openapi.json. Standard civil dates: 1800–2200. Explicit historical date objects: 1000 BCE–2500 CE on all 77 date-bearing operations; require a proleptic calendar and, for timed calculations, UT1 or fixed UT1 offset. Numerology requires an explicit year_convention; place-search is date-independent. See https://cosmicephemeris.com/docs.html#historical-dates. Never guess a calendar, timezone, or birth time. Tarot and supplementary Vedic/readings operations use the separate cosmicephemeris_symbolic tool."
},
"operation": {
"enum": [
"ashtakavarga",
"ashtakoota",
"aspect-policy-stability",
"aspect-windows",
"aspects",
"astrocartography",
"birth-chart",
"birth-time-sensitivity",
"chart-input-readiness",
"chart-robustness",
"chart-uncertainty-envelope",
"civil-time-audit",
"composite",
"convention-compare",
"davison",
"eclipse-geometry",
"electional-criterion-budget-audit",
"electional-criterion-budget-pareto-audit",
"electional-criterion-budget-regret-audit",
"electional-criterion-budget-stability-audit",
"electional-criterion-conflict-core-audit",
"electional-criterion-omission-audit",
"electional-criterion-pair-audit",
"electional-criterion-relation-audit",
"electional-criterion-repair-coverage-audit",
"electional-criterion-repair-distinction-audit",
"electional-criterion-repair-hardening-audit",
"electional-criterion-repair-hardening-pareto-audit",
"electional-criterion-repair-hardening-pareto-hierarchy-audit",
"electional-criterion-repair-hardening-regret-audit",
"electional-criterion-repair-hierarchy-audit",
"electional-criterion-repair-impact-audit",
"electional-criterion-repair-loss-frontier-audit",
"electional-criterion-repair-overlap-audit",
"electional-criterion-repair-resilience-audit",
"electional-criterion-robust-repair-audit",
"electional-criterion-shapley-audit",
"electional-feasibility-audit",
"electional-resolution-audit",
"electional-robustness-audit",
"electional-sampling-phase-audit",
"electional-search",
"electional-tolerance-frontier",
"event-calendar",
"event-rule-search",
"fixed-stars",
"horoscope",
"house-boundary-proximity",
"house-ingresses",
"house-placement-stability",
"house-system-readiness",
"houses",
"location-precision-audit",
"location-transition-scan",
"lunar-nodes",
"moon-phases",
"nakshatra-timeline",
"natal-analysis",
"natal-context",
"natal-report",
"natal-svg",
"numerology",
"panchang",
"place-search",
"planetary-events",
"planetary-hours",
"relocation-chart",
"returns",
"secondary-progressions",
"solar-arcs",
"synastry",
"synastry-svg",
"timezone-resolve",
"transit-svg",
"transits",
"varga-svg",
"vargas",
"vimshottari"
],
"type": "string",
"description": "Live Cosmic Ephemeris calculation operation, without the /api/astro/ prefix."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Calculate with Cosmic Ephemeris"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.cosmicephemeris/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.cosmicephemeris/mcp"}) over MCP.
cosmicephemeris_calculate ~867 tokenscosmicephemeris_symbolic ~254 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.cosmicephemeris%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.cosmicephemeris%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cosmicephemeris%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cosmicephemeris%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.cosmicephemeris%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:499ce26cda965ff9…, first seen 2026-10-17, included at leaf 12027 of 74,845. Version history · verify what your client received.
Compare: most reliable data servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:53 UTC, the Cosmicephemeris MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.
Cosmicephemeris MCP server advertises 2 tools, including cosmicephemeris_calculate, cosmicephemeris_symbolic.
Point your MCP client at this streamable-http endpoint: https://api.cosmicephemeris.com/mcp
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.