The-Phantom (Mo-101/The-Phantom) is an MCP server listed on the M8ven Trust Index. It scores 0 out of 100, grade F. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
0/100

The-Phantom

mostar industries

→ Mo-101/The-Phantom· 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

Mo-101

Source: github_code

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

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
5 flows detected: MAPBOX_TOKEN, FIRMS_MAP_KEY, IOM_DTM_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Hardcoded credentials detected
1 live-looking API key in source: 1 Google API key
🚨
Known vulnerabilities in dependencies: 1 critical, 7 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 8 credentials: ACLED_API_KEY, AFRO_SENTINEL_OIDC_TOKEN, AFRO_SENTINEL_TOKEN, DHIS2_PASSWORD, FIRMS_MAP_KEY, IOM_DTM_API_KEY, NEO4J_PASSWORD, VITE_SUPABASE_PUBLISHABLE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical7 high6 medium2 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.2.4GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highnext@15.5.18GHSA-89xv-2m56-2m9x

Next.js: Server-Side Request Forgery in Server Actions on custom servers

highnext@15.5.18GHSA-m99w-x7hq-7vfj

Next.js: Denial of Service in App Router using Server Actions

highnext@15.5.18GHSA-p9j2-gv94-2wf4

Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

highxlsx@0.18.5GHSA-4r6h-8v6p-xvw6

Prototype Pollution in sheetJS

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
🔐 secretACLED_API_KEY
configACLED_BASE_URL
configACLED_EMAIL
configAFRO_SENTINEL_API_URL
🔐 secretAFRO_SENTINEL_OIDC_TOKEN
🔐 secretAFRO_SENTINEL_TOKEN
configDHIS2_BASE_URL
🔐 secretDHIS2_PASSWORD
configDHIS2_USERNAME
🔐 secretFIRMS_MAP_KEY
🔐 secretIOM_DTM_API_KEY
configIOM_DTM_BASE_URL
🔐 secretNEO4J_PASSWORD
configNEO4J_URI
configNEO4J_USER
configNEON_DATABASE_URL
configOLLAMA_BASE_URL
🔐 secretVITE_SUPABASE_PUBLISHABLE_KEY
configVITE_SUPABASE_URL
configPHANTOM_ENGINE_REPO
configPHANTOM_ENGINE_IMPORT
configPHANTOM_RUN_ID
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployNEXT_PUBLIC_API_BASE_URL
deployNEXT_PUBLIC_API_COMPUTE_SCORES_URL
deployNEXT_PUBLIC_API_OLLAM_CHAT_URL
deployNEXT_PUBLIC_API_PHANTOM_MCP_URL
deployNEXT_PUBLIC_API_PUBLIC_KEY
deployNEXT_PUBLIC_API_TEMPORAL_URL
deployNEXT_PUBLIC_APP_URL
deployNEXT_PUBLIC_ENABLE_NEON_TEMPORAL
deployNEXT_PUBLIC_FIREBASE_API_KEY
deployNEXT_PUBLIC_FIREBASE_APP_ID
deployNEXT_PUBLIC_FIREBASE_AUTH_DOMAIN
deployNEXT_PUBLIC_FIREBASE_PROJECT_ID
deployNEXT_PUBLIC_MAPBOX_BASEMAP
deployNEXT_PUBLIC_MAPBOX_LIGHT_PRESET
deployNEXT_PUBLIC_MAPBOX_SHOW_3D_OBJECTS
deployNEXT_PUBLIC_MAPBOX_SHOW_PEDESTRIAN_ROADS
deployNEXT_PUBLIC_MAPBOX_SHOW_PLACE_LABELS
deployNEXT_PUBLIC_MAPBOX_SHOW_POI_LABELS
deployNEXT_PUBLIC_MAPBOX_SHOW_ROADS_AND_TRANSIT
deployNEXT_PUBLIC_MAPBOX_SHOW_ROAD_LABELS
deployNEXT_PUBLIC_MAPBOX_SHOW_TRANSIT_LABELS
deployNEXT_PUBLIC_MAPBOX_STANDARD_FONT
deployNEXT_PUBLIC_MAPBOX_STANDARD_THEME
deployNEXT_PUBLIC_MAPBOX_TOKEN
deployNEXT_PUBLIC_OLLAMA_HOST
deployNEXT_PUBLIC_OLLAMA_MODEL
deployPORT
deploySUPABASE_ANON_KEY
deploySUPABASE_SERVICE_ROLE_KEY
deploySUPABASE_URL
// 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

7/7 tools missing one or more hints — view_location (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fly_to_corridor (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); radar_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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.).

No hardcoded API keys

1 live-looking API key in source: 1 Google API key

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

Only 0/7 tools referenced in tests (0%)

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

Secrets not logged

1 secret value sent to error

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 5 high severity in production deps — next@15.5.18 (high), next@15.5.18 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

3 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 8 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/mo-101/the-phantom?variant=verified)](https://m8ven.ai/mcp/mo-101/the-phantom)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: da1490f919d19269c2a942dae4b126453f3525cd
code hash: e66fbf54e09f1211acd06308bc592c10c0a24f78f79b93f98733bfc708680e4f
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