# Astro API (remote · 81.166.197.155)

Astronomical logical calculator for AI clients.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `81.166.197.155`: 64/100 (this document), [markdown](https://verifymcp.io/servers/frankthomastveter-astro-api/81.md), [page](https://verifymcp.io/servers/frankthomastveter-astro-api/81)

## Channel facts

- Endpoint: `https://81.166.197.155/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (astrologos.run).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC not yet verified: we couldn't validate it against a resolver.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 530 tokens (~66/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Astro API MCP server?

Astro API is a hosted endpoint at https://81.166.197.155/mcp, 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.

### Claude

```bash
claude mcp add --transport http frankthomastveter-astro-api 'https://81.166.197.155/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.frankthomastveter-astro-api]
url = "https://81.166.197.155/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "frankthomastveter-astro-api": {
      "type": "remote",
      "url": "https://81.166.197.155/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add frankthomastveter-astro-api --url 'https://81.166.197.155/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  frankthomastveter-astro-api:
    url: "https://81.166.197.155/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "frankthomastveter-astro-api": {
      "Transport": "http",
      "Url": "https://81.166.197.155/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add frankthomastveter-astro-api -t streamable-http -u 'https://81.166.197.155/mcp'
```

### Other

```json
{
  "mcpServers": {
    "frankthomastveter-astro-api": {
      "type": "http",
      "url": "https://81.166.197.155/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 60)

First indexed and scored.

## MCP tools (8)

### `astrologos.run` (~143 tokens)

Run an Astrologos program and return a job id plus sync output when available.

Input parameters:

- `json` (boolean): Alias for json_output
- `json_output` (boolean): When true, runtime stdout contains only values emitted by Astrologos json commands
- `max_millis` (integer): Optional requested maximum runtime milliseconds
- `metadata` (object): Optional JSON object recorded with the job
- `mode` (string): Execution mode
- `source_label` (string): Display label for inline source
- `source_text` (string, required): Astrologos source program
- `token` (string): Optional fallback Astrologos MCP token. Prefer Authorization: Bearer.

### `astrologos.job_status` (~55 tokens)

Read the current status for one owned Astrologos job.

Input parameters:

- `job_id` (string, required): Astrologos job UUID
- `token` (string): Optional fallback Astrologos MCP token. Prefer Authorization: Bearer.

### `astrologos.job_result` (~57 tokens)

Read stored stdout and stderr for one completed owned Astrologos job.

Input parameters:

- `job_id` (string, required): Astrologos job UUID
- `token` (string): Optional fallback Astrologos MCP token. Prefer Authorization: Bearer.

### `astrologos.abort_job` (~62 tokens)

Request cancellation for one owned Astrologos job.

Input parameters:

- `job_id` (string, required): Astrologos job UUID
- `reason` (string): Cancellation reason
- `token` (string): Optional fallback Astrologos MCP token. Prefer Authorization: Bearer.

### `astrologos.usage` (~41 tokens)

Read current quota and reservation usage for the authenticated account.

Input parameters:

- `token` (string): Optional fallback Astrologos MCP token. Prefer Authorization: Bearer.

### `astrologos.validate_token` (~41 tokens)

Validate an Astrologos token without returning token material.

Input parameters:

- `token` (string): Optional fallback Astrologos MCP token. Prefer Authorization: Bearer.

### `astrologos.help` (~92 tokens)

Search or read Astrologos help without consuming execution quota.

Input parameters:

- `include_doc` (boolean): Include full rendered docs in search results. Defaults to true; set false for compact results.
- `limit` (integer): Maximum search results
- `query` (string): Search query. Omit when requesting overview or topic_id.
- `topic_id` (string): Stable help topic id, for example function:time.

### `astrologos.get_settings_link` (~28 tokens)

Return the Astrologos web settings link for account settings, plans, and tokens.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/frankthomastveter-astro-api/81#diagnostics

## Score history

- 2026-09-29: 64
- 2026-09-28: 63
- 2026-09-27: 63
- 2026-09-26: 62
- 2026-09-25: 62
- 2026-09-24: 61
- 2026-09-23: 61
- 2026-09-22: 60
- 2026-09-21: 60

## Common questions

### What is the Astro API MCP server?

Astro API is an MCP server listed in the public MCP registry as io.github.FrankThomasTveter/astro-api. Astronomical logical calculator for AI clients. This page covers its hosted endpoint (https://81.166.197.155/mcp).

### Is the Astro API MCP server safe to use?

Astro API scores 64 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 Astro API MCP server expose?

Astro API exposes 8 tools: astrologos.run, astrologos.job_status, astrologos.job_result, astrologos.abort_job, astrologos.usage, and 3 more. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.

### Does the Astro API MCP server require authentication?

No. We connected to Astro API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Astro API MCP server still maintained?

Astro API is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://81.166.197.155/mcp
- Website: https://81.166.197.155/
- Changelog RSS feed: https://verifymcp.io/servers/frankthomastveter-astro-api/81.xml
- Changelog JSON feed: https://verifymcp.io/servers/frankthomastveter-astro-api/81.json
- HTML version of this page: https://verifymcp.io/servers/frankthomastveter-astro-api/81