Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Astro API

REMOTE · 81.166.197.155

Astronomical logical calculator for AI clients.

Available components

0 this week 74 Trust /100

Last scanned (14 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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
Transport & Reachability100
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (11)

  • TLS certificate
  • Authorization
  • HSTS header
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  • DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 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=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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
MCP tools · 8 exposed · ~519 tokens

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 →

Tool Tokens
astrologos.abort_job ~62

Request cancellation for one owned Astrologos job.

NameTypeReqDescription
job_idstringyesAstrologos job UUID
reasonstring–Cancellation reason
tokenstring–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.

NameTypeReqDescription
include_docboolean–Include full rendered docs in search results. Defaults to true; set false for compact results.
limitinteger–Maximum search results
querystring–Search query. Omit when requesting overview or topic_id.
topic_idstring–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.

NameTypeReqDescription
job_idstringyesAstrologos job UUID
tokenstring–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.

NameTypeReqDescription
job_idstringyesAstrologos job UUID
tokenstring–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.

NameTypeReqDescription
jsonboolean–Alias for json_output
json_outputboolean–When true, runtime stdout contains only values emitted by Astrologos json commands
max_millisinteger–Optional requested maximum runtime milliseconds
metadataobject–Optional JSON object recorded with the job
modestring–Execution mode
source_labelstring–Display label for inline source
source_textstringyesAstrologos source program
tokenstring–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.

NameTypeReqDescription
tokenstring–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.

NameTypeReqDescription
tokenstring–Optional fallback Astrologos MCP token. Prefer Authorization: Bearer.

No output schema declared.

No examples provided.

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.

remote · 81.166.197.155

# add to Claude Code
claude mcp add --transport http frankthomastveter-astro-api 'https://81.166.197.155/mcp'
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 74 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Astro API MCP server?

VerifyMCP ran 11 checks on Astro API, covering TLS certificate, Authorization, HSTS header, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Astro API: HTTPS and DNSSEC. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.