Astro API

connects

81.166.197.155

Astronomical logical calculator for AI clients.

https://81.166.197.155/mcpWebsiteOAuthMCP 2025-11-25v1.7.0last checked 22 Sep 2026spoke MCP on 100% of 5 checks (30 days)initialize in 82 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.

claude mcp add --transport http astro-api https://81.166.197.155/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.

Settings → Connectors → Add custom connector, then paste https://81.166.197.155/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://81.166.197.155/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.

{
  "mcpServers": {
    "astro-api": {
      "url": "https://81.166.197.155/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.

{
  "servers": {
    "astro-api": {
      "type": "http",
      "url": "https://81.166.197.155/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 22 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://81.166.197.155
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required.
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	run, usage
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 8 tools listable
Documentation	https://81.166.197.155/

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

8 tools usable without signing in

The server exposes a public surface before authorization: astrologos.run, astrologos.job_status, astrologos.job_result, astrologos.abort_job, astrologos.usage, astrologos.validate_token, astrologos.help, astrologos.get_settings_link.

Tools

astrologos.abort_jobastrologos.get_settings_linkastrologos.helpastrologos.job_resultastrologos.job_statusastrologos.runastrologos.usageastrologos.validate_token

Contract history

21 Sep 2026v1.7.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Set up a watch

Own this server?

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/astro-api/badge.svg)](https://mcpi.app/servers/astro-api)