invest-igator (PanagiotisKaraliolios/invest-igator) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 1 tool. No publisher has claimed this listing.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

PanagiotisKaraliolios

Source: Smithery

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 →

Install from

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
1 tools verified — handlers match their declared behaviour
1 read-only tool verified — handlers contain no write/delete/exec
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 8 credentials: ADMIN_PASSWORD, AI_MUTATION_SECRET, AUTH_DISCORD_SECRET, AZURE_OPENAI_API_KEY, BETTER_AUTH_SECRET, CLOUDFLARE_SECRET_ACCESS_KEY, INFLUXDB_TOKEN, POLYGON_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.
configADMIN_EMAIL
configADMIN_NAME
🔐 secretADMIN_PASSWORD
configAI_API_KEY_PEPPER
configAI_CRED_ACTIVE_KID
configAI_CRED_KEYS
configAI_EVAL_LIVE
🔐 secretAI_MUTATION_SECRET
configAPP_NAME
configAUTH_DISCORD_ID, AUTH_DISCORD_SECRET: Discord OAuth credentials (required if enabling Discord)
🔐 secretAUTH_DISCORD_SECRETAUTH_DISCORD_ID, : Discord OAuth credentials (required if enabling Discord)
🔐 secretAZURE_OPENAI_API_KEY
configAZURE_OPENAI_CHAT_DEPLOYMENT
configAZURE_OPENAI_CHAT_MODEL
configAZURE_OPENAI_RESOURCE_NAME
🔐 secretBETTER_AUTH_SECRETSecret for Better Auth JWT/cookies (required in production)
configBETTER_AUTH_URLPublic base URL of the app (default: <http://localhost:3000>)
configCLOUDFLARE_ACCESS_KEY_ID
configCLOUDFLARE_ACCOUNT_ID
configCLOUDFLARE_BUCKET_NAME
configCLOUDFLARE_R2_PUBLIC_URL
🔐 secretCLOUDFLARE_SECRET_ACCESS_KEY
configE2E_BASE_URL
configE2E_USE_PREVIEW
configEMAIL_FROMFrom address for transactional emails (required)
configEMAIL_SERVERNodemailer connection string (e.g. SMTP URI) (required)
configENABLE_MCP
configINFLUXDB_BUCKET
configINFLUXDB_ORG
🔐 secretINFLUXDB_TOKEN
configINFLUXDB_URLFor local dev, make sure points at the local instance —
configPASSWORD_PEPPERExtra pepper for hashing local passwords (required)
🔐 secretPOLYGON_API_KEYPOLYGON_API_URL, — required by the env schema (src/env.js, z.string()), so the app fails validation on boot without them unless SKIP_ENV_VALIDATION=1; note no code path consumes them yet
configPOLYGON_API_URL, POLYGON_API_KEY — required by the env schema (src/env.js, z.string()), so the app fails validation on boot without them unless SKIP_ENV_VALIDATION=1; note no code path consumes them yet
configPW_SKIP_WEBSERVERConfig: playwright.config.ts (uses a built-in dev server unless =1).
configSKIP_ENV_VALIDATIONSee the [Environment variables](#-environment-variables) section below. For a smoke test you can set placeholders and use =1 while you iterate.
configYAHOO_API_URL(base URL, default <https://query2.finance.yahoo.com/v8/finance>; code appends /chart/<symbol>, so do not include /chart) — FX ingestion also sources rates from Yahoo
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployNEXT_PUBLIC_ADSENSE_CLIENT_ID
deployNEXT_PUBLIC_ADSENSE_SLOT_DASHBOARD
deployNEXT_PUBLIC_ADSENSE_SLOT_LANDING
deployNEXT_PUBLIC_ADSENSE_SLOT_WATCHLIST
deployNEXT_PUBLIC_GA_MEASUREMENT_ID
deployNEXT_PUBLIC_SITE_URL
deployNEXT_PUBLIC_UMAMI_WEBSITE_ID
deployPORT
// quality suggestions

Dependencies

77 dependencies, 1 flagged: @playwright/test

All four hints declared on every tool

1/1 tools missing one or more hints — echo.say (missing: destructiveHint, idempotentHint). 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.

Tool handlers catch errors

Only 0/1 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

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

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

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Dependency freshness

1/58 production deps stale: server-only@2022-09-03 (3.9y)

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 5 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 Score](https://m8ven.ai/badge/mcp/panagiotiskaraliolios/invest-igator)](https://m8ven.ai/mcp/panagiotiskaraliolios/invest-igator)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 655998fa5d297263569461e0303c5bd8eb1cbecf
code hash: f64ca1ec3adabb874c0dc27ddc8cf914cb2829e0b42aae5a04f90cce464545e1
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