io.github.SirCharan/findmyzodiac
REMOTE · FINDMYZODIAC.COM
Western zodiac sign from date of birth and sign compatibility scores. English and Hindi.
Available components
Last scanned (23 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Entertainment and Games
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 338 tokens (~169/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 67
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 4 Nov 2026 · Probed https://findmyzodiac.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=findmyzodiac.com | CN=YR1,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | RSA 2048 | SHA256-RSA | 58c75c6cc587a5e1a35c60e06f8ea952151 |
| SANs: findmyzodiac.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of findmyzodiac.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| findmyzodiac.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://findmyzodiac.com/mcp | Verified | 200 | |
| http (plaintext) | http://findmyzodiac.com/mcp | HTTPS enforced | 308 | https://findmyzodiac.com/mcp |
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 →
check_compatibility ~196
Score two signs 0-100 with the published rule: element base (same 80; fire-air 85; earth-water 85; fire-earth 45; fire-water 40; earth-air 50; air-water 55), modality same -5 / different +5, no modality adjustment for a sign with itself (same sign = 75), clamp and round; symmetric. Bands: 80+ strong, 65-79 good, 50-64 mixed, <50 challenging. Returns score, band, verdict (one line per band), elements, modalities, method_url '/guides/how-compatibility-is-scored', page_url. Case-insensitive; Hindi sign names accepted. Example input: {"sign_a":"Aries","sign_b":"Leo"}
| Name | Type | Req | Description |
|---|---|---|---|
| sign_a | string | yes | First sign, English or Hindi |
| sign_b | string | yes | Second sign, English or Hindi |
No output schema declared.
No examples provided.
get_zodiac_sign ~142
Western sun sign from a date of birth (year optional, ignored). Returns sign slug, name_en, name_hi, start, end, element, modality, ruler, is_cusp (first or last day), cusp_neighbour, convention 'standard calendar dates', url. Validation error for impossible dates like 02-30. Example input: {"month":7,"day":23,"lang":"en"}
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | Day of birth, 1 to 31 |
| lang | string | – | Language of the sign name in url: en or hi |
| month | integer | yes | Month of birth, 1 to 12 |
No output schema declared.
No examples provided.
How do I install the io.github.SirCharan/findmyzodiac MCP server?
io.github.SirCharan/findmyzodiac is a hosted endpoint at https://findmyzodiac.com/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 · findmyzodiac.com
claude mcp add --transport http sircharan-findmyzodiac 'https://findmyzodiac.com/mcp'
What is the io.github.SirCharan/findmyzodiac MCP server?
io.github.SirCharan/findmyzodiac is an MCP server listed in the public MCP registry as io.github.SirCharan/findmyzodiac. Western zodiac sign from date of birth and sign compatibility scores. English and Hindi. This page covers its hosted endpoint (https://findmyzodiac.com/mcp).
Is the io.github.SirCharan/findmyzodiac MCP server safe to use?
io.github.SirCharan/findmyzodiac scores 70 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 io.github.SirCharan/findmyzodiac MCP server expose?
io.github.SirCharan/findmyzodiac exposes 2 tools: get_zodiac_sign, check_compatibility. Their descriptions and schemas cost roughly 338 tokens of context every time the server is loaded.
Does the io.github.SirCharan/findmyzodiac MCP server require authentication?
No. We connected to io.github.SirCharan/findmyzodiac without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.SirCharan/findmyzodiac MCP server still maintained?
io.github.SirCharan/findmyzodiac is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.