Astrology MCP server

The hosted server

https://zodiacs.org/mcp speaks MCP over Streamable HTTP. Its six tools are read-only and need no sign-in: get_sky, get_upcoming_events, check_sky_fact, get_horoscope, open_chart_studio and get_capabilities. In Claude, add it as a custom connector. In code, connect with the official SDK client, which npm install @modelcontextprotocol/client@2.3.1 installs, under Apache-2.0.

The guide checks run this code with that client against the hosted server's own handler, served locally; Mercury was direct at that instant, so the answer is false.

import { Client, StreamableHTTPClientTransport } from '@modelcontextprotocol/client';
const client = new Client({ name: 'sky-check', version: '1.0.0' });
await client.connect(new StreamableHTTPClientTransport(new URL('https://zodiacs.org/mcp')));
try {
  const { tools } = await client.listTools();
  console.log(tools.map((tool) => tool.name));
  const fact = await client.callTool({
    name: 'check_sky_fact',
    arguments: { kind: 'retrograde', body: 'Mercury', instant: '2026-10-12T12:00:00Z' },
  });
  console.log(fact.structuredContent.data.answer);
} finally {
  await client.close();
}

The local server

The local adapter runs over stdio on your own machine and opens no listener and no network connection. It adds natal-chart calculation and the comparison of calculation records to the sky tools. It is a release candidate, not on npm: its archive and digest are on the MCP page.

What either one does not do

Neither server stores what an assistant sends it. A connected assistant still receives the arguments and the results, and its provider's own policies apply to them. The tools calculate the sky; they do not predict, schedule or advise.

References

• AI assistants
• Local MCP server
• Model Context Protocol