Astro API
REMOTE · 81.166.197.155 · SCANNED SEP 29
Astronomical logical calculator for AI clients.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (astrologos.run). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 530 tokens (~66/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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 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.
remote · 81.166.197.155
claude mcp add --transport http frankthomastveter-astro-api 'https://81.166.197.155/mcp'
{
"mcpServers": {
"frankthomastveter-astro-api": {
"url": "https://81.166.197.155/mcp"
}
}
} {
"servers": {
"frankthomastveter-astro-api": {
"type": "http",
"url": "https://81.166.197.155/mcp"
}
}
} [mcp_servers.frankthomastveter-astro-api] url = "https://81.166.197.155/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"frankthomastveter-astro-api": {
"type": "remote",
"url": "https://81.166.197.155/mcp",
"enabled": true
}
}
} openclaw mcp add frankthomastveter-astro-api --url 'https://81.166.197.155/mcp' --transport streamable-http
mcp_servers:
frankthomastveter-astro-api:
url: "https://81.166.197.155/mcp" {
"McpServers": {
"frankthomastveter-astro-api": {
"Transport": "http",
"Url": "https://81.166.197.155/mcp"
}
}
} assistant mcp add frankthomastveter-astro-api -t streamable-http -u 'https://81.166.197.155/mcp'
{
"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.
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.
- 29 Sept 26 +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.
- 28 Sept 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 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 60
First indexed and scored.
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 29 Sept 2026 · Probed https://81.166.197.155/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of 81.166.197.155. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| 81.166.197.155. | Error no A/AAAA/CNAME RRset answered for the name |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://81.166.197.155/mcp | Verified | 200 | |
| http (plaintext) | http://81.166.197.155/mcp | Inconclusive | 405 |
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 →
astrologos.abort_job ~62
Request cancellation for one owned Astrologos job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Astrologos job UUID |
| reason | string | – | Cancellation reason |
| token | string | – | Optional fallback Astrologos MCP token. Prefer Authorization: Bearer. |
No output schema declared.
No examples provided.
astrologos.get_settings_link ~28
Return the Astrologos web settings link for account settings, plans, and tokens.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
astrologos.help ~92
Search or read Astrologos help without consuming execution quota.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
astrologos.job_result ~57
Read stored stdout and stderr for one completed owned Astrologos job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Astrologos job UUID |
| token | string | – | Optional fallback Astrologos MCP token. Prefer Authorization: Bearer. |
No output schema declared.
No examples provided.
astrologos.job_status ~55
Read the current status for one owned Astrologos job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Astrologos job UUID |
| token | string | – | Optional fallback Astrologos MCP token. Prefer Authorization: Bearer. |
No output schema declared.
No examples provided.
astrologos.run ~143
Run an Astrologos program and return a job id plus sync output when available.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Astrologos source program |
| token | string | – | Optional fallback Astrologos MCP token. Prefer Authorization: Bearer. |
No output schema declared.
No examples provided.
astrologos.usage ~41
Read current quota and reservation usage for the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Optional fallback Astrologos MCP token. Prefer Authorization: Bearer. |
No output schema declared.
No examples provided.
astrologos.validate_token ~41
Validate an Astrologos token without returning token material.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Optional fallback Astrologos MCP token. Prefer Authorization: Bearer. |
No output schema declared.
No examples provided.
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.