com.roxyapi/astrology v1.0.1

40D

Security Trust Score

Grade D · Weak posture

Tier 2 · Live endpointLow confidence · 24%rubric 2.9.0

Declared MCP capabilities

ResourcesPrompts

This server scored D. Run it behind runtime policy enforcement so one bad tool call can't become an incident.

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

Pass
Indirect Prompt Injection (IPI) Defensesguardno injection markers
Tool/prompt/resource text is free of hidden instructions that could hijack the agent.
Pass
User-in-the-Loop / Approval Scopeguardno destructive tool scope
No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.
Not checked
Strict JSON Schema Enforcementno source files
Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.
N/A
Tool Definition Integrityguardno prior version to diff
Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

Application Security Checks

Not checked
No command-injection sinksguardno source
Untrusted tool input reaching a shell yields remote code execution.
Not checked
No dynamic code executionguardno source
eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.
Not checked
No path traversalguardno source
Naive path checks let tools read/write outside intended directories (EscapeRoute-class).
Not checked
No SSRF sinksguardno source
Fetching tool-supplied URLs can pivot into internal networks and metadata services.
Not checked
No unsafe deserializationguardno source
pickle/yaml.load/etc. on untrusted data can execute code.
Not checked
No committed secretsguardno source
Hardcoded keys/tokens in published source are live credentials an attacker can use.
Not checked
Credentials sourced from environmentno source files
Reading secrets from env/secret stores avoids hardcoding them.
Not checked
Dependencies pinned (lockfile)no source files
A lockfile makes installs reproducible and resistant to silent dependency swaps.
Not checked
Actively maintainedno GitHub repository
Unmaintained servers don't receive security fixes.
Not checked
Repository not archivedguardno GitHub repository
Archived repositories will never be patched.
Not checked
Declares a licenseno GitHub repository
A clear license is required for legal enterprise use.
Not checked
Has a security policyno source files
A SECURITY.md gives a private path to report vulnerabilities.
Not checked
Signed releasesnot evaluated
Signed releases let consumers verify artifacts weren't tampered with.
Not checked
Adoption & popularityno adoption signal
A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.
N/A
No known-vulnerable dependenciesno dependencies to scan
Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.
N/A
No install/post-install scriptsguardno published package
install hooks run arbitrary code on every consumer at install time.
N/A
Package name not typosquattingguardno published package
Names mimicking popular packages are a common malware delivery vector.
N/A
Published with provenanceno published package
Build provenance attests the artifact was built from the claimed source by CI.
N/A
Established maintainerno published package
Brand-new / single anonymous maintainers raise takeover and malware risk.

Transport & Trust Model

Warn
IAM / Authentication Scopingno authentication handling detected
OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.
Fix: Implement OAuth 2.1 with a .well-known/oauth-protected-resource document.
Pass
Transport Encryption (TLS)guardall remotes use HTTPS
Plaintext HTTP exposes traffic and bearer tokens to interception.
Not checked
Execution Sandboxingno source files
A container/sandbox image limits blast radius; a server that runs natively has full host access.
Not checked
Network Exposureno source files
Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.
N/A
Live Endpoint Reachablenot dynamically scanned
A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.
N/A
Authentication Enforced (live)not dynamically scanned
If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (39)

get_astrology_signspost_astrology_housespost_astrology_lilithget_astrology_signs_idpost_astrology_aspectspost_astrology_planetspost_astrology_synastrypost_astrology_transitspost_astrology_asteroidspost_astrology_solar_arcpost_astrology_arabic_lotspost_astrology_fixed_starspost_astrology_local_spacepost_astrology_natal_chartpost_astrology_profectionspost_astrology_lunar_returnpost_astrology_progressionspost_astrology_solar_returnget_astrology_planet_meaningspost_astrology_aspect_patternspost_astrology_aspects_monthlypost_astrology_composite_chartpost_astrology_planets_monthlypost_astrology_transit_aspectspost_astrology_astrocartographypost_astrology_relocation_chartpost_astrology_transits_monthlyget_astrology_moon_phase_currentget_astrology_planet_meanings_idpost_astrology_parallels_monthlypost_astrology_planetary_returnsget_astrology_moon_phase_upcomingpost_astrology_ecliptic_crossingsget_astrology_horoscope_sign_dailypost_astrology_compatibility_scoreget_astrology_horoscope_sign_weeklyget_astrology_horoscope_sign_yearlyget_astrology_horoscope_sign_monthlyget_astrology_moon_phase_calendar_year_month