Skip to content

MCP servers › co.cosmicchemistry › vedic-astrology

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

co.cosmicchemistry/vedic-astrology

Free Vedic astrology: birth chart, dasha, Sade Sati, Saturn return, panchang, planetary hours. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: other · AI-classifiedversion 1.0.0streamable HTTP21 tools

Summary

co.cosmicchemistry/vedic-astrology is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 21 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
21
Described as changing data
0 of 21 toolsAI-classified
Mainly works on
nothing outside itself: it only answers questionsAI-classified
Topic
otherAI-classified
Last tested
2026-10-23

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-16 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-16 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-16).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
21tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.

None of its 21 tools are described as changing anything.

  • vedic_birth_chartreads or searches

    “Use this when someone asks for their Vedic birth chart, kundli, janam kundali, sidereal chart, or where their planets are in Vedic astrology (signs, houses, nakshatras, rising sign).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestring“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
  • vedic_rising_signreads or searches

    “Use this when someone asks for their rising sign, ascendant or lagna in Vedic astrology, or why their Vedic rising sign differs from a Western app.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 3 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestringrequired“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
  • moon_sign_nakshatrareads or searches

    “Use this when someone asks for their Moon sign (rashi), birth star or nakshatra and pada in Vedic astrology.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestring“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
  • sade_sati_checkreads or searches

    “Use this when someone asks whether they are in Sade Sati, when their Sade Sati starts or ends, or about Saturn’s seven and a half years.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestring“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
  • saturn_return_datesreads or searches

    “Use this when someone asks when their Saturn return is (in Vedic, sidereal reckoning), whether they are in it now, or at what ages it comes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestring“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
  • current_dashareads or searches

    “Use this when someone asks which mahadasha or antardasha they are running, their Vimshottari dasha timeline, when their next dasha begins, or when a dasha ends ("when does my Rahu dasha end", "my cur…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 3 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestringrequired“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
    • on_datestring“Optional: a day as YYYY-MM-DD, to see which periods were or will be running then.”
    • mahadashastring“Optional: one mahadasha lord, to list all nine antardashas of that mahadasha with dates, past, now or ahead.”
  • manglik_checkreads or searches

    “Use this when someone asks if they are Manglik or have Mangal dosha.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestring“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
  • planet_in_house_meaningreads or searches

    “Use this when someone asks what a planet in a house means in Vedic astrology, e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • planetstringrequired
    • houseintegerrequired“House number, 1 to 12.”
  • daily_panchangreads or searches

    “Use this when someone asks for today’s panchang or the Hindu calendar for a place: the tithi, nakshatra, yoga, karana, Rahu kaal (rahu kalam), Yamaganda, Gulika, Abhijit muhurat, choghadiya, sunrise …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • placestring“Town or city, with region or country if known, e.g.”
    • datestring“The date wanted, as YYYY-MM-DD.”
  • festival_and_vrat_datesreads or searches

    “Use this when someone asks when a Hindu festival, vrat or observance falls, or what is coming up: "when is Diwali", "next Ekadashi", "Karwa Chauth date", "Pradosh vrat this month", "festivals in Nove…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • placestring“Town or city, with region or country if known, e.g.”
    • fromstring“First day of the list, as YYYY-MM-DD.”
    • daysinteger“How many days to list, 1 to 120.”
    • namestring“Optional: only days whose name contains this word, e.g.”
  • moon_todayreads or searches

    “Use this when someone asks where the Moon is right now, today or on another date: its sign (Vedic and Western), its nakshatra, its phase, or when the next full moon or new moon comes ("what sign is t…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • placestring“Optional: the town, so the times come as local clock times there.”
    • datestring“Optional: a date as YYYY-MM-DD, for the Moon at midday that day.”
  • planetary_hourson 1 other serverreads or searches

    “Use this when someone asks for the planetary hours or hora of a day and place, which planet rules the hour now, or when a planet’s hour comes ("planetary hours today in London", "what planetary hour …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • placestringrequired“Town or city, with region or country if known, e.g.”
    • datestring“The date wanted, as YYYY-MM-DD.”
Show 9 more tools
  • mercury_retrogradereads or searches

    “Use this when someone asks whether Mercury is retrograde now, when the next Mercury retrograde starts or ends, or for the Mercury retrograde dates of a year ("is Mercury in retrograde", "when does Me…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • yearinteger“Optional: list every Mercury retrograde of this year.”
  • venus_retrogradereads or searches

    “Use this when someone asks whether Venus is retrograde now, when Venus retrograde starts or ends, or for the Venus retrograde dates of a year ("is Venus retrograde", "Venus retrograde 2026", "when do…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • yearinteger“Optional: list every Venus retrograde touching this year.”
  • chara_karakasreads or searches

    “Use this when someone asks for their atmakaraka (soul planet), amatyakaraka (career planet), darakaraka (spouse or partner planet) or their seven chara karakas in Jaimini or Vedic astrology ("what is…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestring“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
    • whichstring“The karaka asked about.”
  • divisional_chartreads or searches

    “Use this when someone asks for their navamsa (D9) chart, read for marriage and inner strength, or their dashamsha (D10) chart, read for career ("my navamsa chart", "D9 chart", "Venus in my navamsa", …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 4 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestringrequired“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
    • chartstringrequired“d9 for the navamsa, d10 for the dashamsha (career).”
  • indu_lagna_money_signreads or searches

    “Use this when someone asks for their Indu Lagna, their money or wealth sign, or which planet is key for money in their Vedic chart ("indu lagna calculator", "my wealth sign in astrology", "which plan…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 3 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestringrequired“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
  • vedic_and_western_signsreads or searches

    “Use this when someone asks what their sign is in Vedic (sidereal) astrology compared with Western (tropical) astrology, why their sign is different in Vedic astrology, or for their "real" or sidereal…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestring“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
  • vehicle_purchase_datesreads or searches

    “Use this when someone asks for a good day or muhurat to buy a car, bike or other vehicle from their birth details ("vehicle purchase muhurat", "best day to buy a car as per my chart", "car muhurat ne…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 2 required
    • birth_datestringrequired“Date of birth, YYYY-MM-DD, e.g.”
    • birth_timestring“Local clock time of birth, 24-hour HH:MM, e.g.”
    • birth_placestringrequired“Town or city of birth, with region or country if known, e.g.”
    • town_nowstring“Optional: where they live now, for the time zone of the days.”
    • fromstring“Optional: the first of the 60 days, as YYYY-MM-DD.”
  • birth_chart_compatibilityreads or searches

    “Use this when someone asks whether two people are compatible in Vedic astrology, for synastry, or to compare two birth charts ("are we compatible", "compare my chart with my partner’s", "Vedic compat…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 4 required
    • person_a_birth_datestringrequired“The first person’s date of birth, YYYY-MM-DD.”
    • person_a_birth_timestring“The first person’s local clock time of birth, 24-hour HH:MM, if known.”
    • person_a_birth_placestringrequired“The first person’s town or city of birth, with region or country if known.”
    • person_b_birth_datestringrequired“The second person’s date of birth, YYYY-MM-DD.”
    • person_b_birth_timestring“The second person’s local clock time of birth, 24-hour HH:MM, if known.”
    • person_b_birth_placestringrequired“The second person’s town or city of birth, with region or country if known.”
  • mahadasha_meaningreads or searches

    “Use this when someone asks what a mahadasha or antardasha means in Vedic astrology in general, or how long one lasts, without asking for their own dates: "what does Rahu mahadasha mean", "Saturn maha…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • planetstringrequired“The mahadasha lord.”
    • antardashastring“Optional: the antardasha lord inside it.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 21 tools
Says what it returns
100% of 21 tools
States limits, defaults or errors
5% of 21 tools
Says when to use it
100% of 21 tools
Items covered per tool
3.0 of 4 on average

Counted from the listing

Parameters with a description
98% of 64
Tools with a description
100% of 21
Typical description length
514 characters

The tool set

Counted from the listing

Tools
21
Size of the list
about 6,596 tokens for an agent to load (characters ÷ 4)
Naming
21 of 21 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 21 of 21 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://cosmicchemistry.co/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "vedic-astrology": {
      "url": "https://cosmicchemistry.co/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "vedic-astrology": {
      "type": "http",
      "url": "https://cosmicchemistry.co/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"vedic-astrology","type":"http","url":"https://cosmicchemistry.co/mcp"}'
Claude Code
claude mcp add --transport http vedic-astrology https://cosmicchemistry.co/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://cosmicchemistry.co/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint cosmicchemistry.co/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about co.cosmicchemistry/vedic-astrology

Answered from the data above

Does co.cosmicchemistry/vedic-astrology need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has co.cosmicchemistry/vedic-astrology been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can co.cosmicchemistry/vedic-astrology do?

It lists 21 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can co.cosmicchemistry/vedic-astrology change or delete data?

None of its 21 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “other” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 719 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 21 tools, 0 resources, 0 prompts.
  4. 2,061 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
No value: the AI answer was held back because the quoted text did not clearly support it.
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “co.cosmicchemistry/vedic-astrology: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/co.cosmicchemistry/vedic-astrology

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/co.cosmicchemistry/vedic-astrology)](https://protocolprobe.com/mcp/servers/co.cosmicchemistry/vedic-astrology)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology