Back to MCP Trust Indexm8ven
C
Warning
74/100
1 day ago

project_astro

MCP Server and Kali API Server- With Claude Desktop Integ

→ whit3rabbit0/project_astro· listed on github_code

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

whit3rabbit0

Source: github_code · also listed on mcp.so

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHubmcp.so

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
2 flows detected: API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 2 credentials: API_KEY, OPENAI_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configKALI_API_BASE_URL
configMCP_PORT
🔐 secretAPI_KEYAPI key for authenticated access
configASTRO_HOST127.0.0.1 Server bind address
configASTRO_PORT8080 Server listen port
configAPI_PORT
configASTRO_DEBUGfalse Enable debug logging
configASTRO_OIDC_ROLES
configASTRO_TRANSPORTstreamable-http MCP transport (streamable-http or stdio)
configASTRO_SCOPE_CONFIGPath to scope YAML config
configASTRO_DB_PATH~/.astro/engagements.db SQLite database path
configASTRO_OIDC_ISSUER
configASTRO_OIDC_CLIENT_ID
configASTRO_OIDC_AUDIENCE
🔐 secretOPENAI_API_KEY
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

68/68 tools missing one or more hints — nmap_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); gobuster_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dirb_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +65 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 7/68 tools referenced in tests (10%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets stay with their owner

2 secret/sensitive values flow into network calls (API_KEY → dynamic, API_KEY → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not logged

3 secret values sent to console.log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/whit3rabbit0-project-astro-1iy3ho?variant=verified)](https://m8ven.ai/mcp/whit3rabbit0-project-astro-1iy3ho)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3842ba12056abf289c2b7313fe8acfdf6c58d913
code hash: b3093e0a675fbeeac59dc0b9ce1c2c84ee029d9d27dd30af154371b9aa821456
verified: 8/18/2026, 9:25:14 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client