etf-scout-mcp (pierdom/etf-scout-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

etf-scout-mcp

MCP server for ETF research via justETF, Yahoo Finance, and OpenFIGI

→ pierdom/etf-scout-mcp· listed on github_repo_search

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

pierdom

Source: github_repo_search

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
✅
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 3 credentials: ETF_SCOUT_MCP_HTTP_BEARER_TOKEN, OPENFIGI_API_KEY, OIDC_CLIENT_SECRET
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.
configETF_SCOUT_MCP_TRANSPORT
configETF_SCOUT_MCP_HTTP_HOST
configETF_SCOUT_MCP_HTTP_PORT
🔐 secretETF_SCOUT_MCP_HTTP_BEARER_TOKENthat value>
configETF_SCOUT_MCP_CACHEjustETF returning nothing — results cache up to 24h; delete
configETF_SCOUT_MCP_CACHE_TTL_QUOTE
configETF_SCOUT_MCP_CACHE_TTL_PROFILE
configETF_SCOUT_MCP_CACHE_TTL_HISTORY
configETF_SCOUT_MCP_LOG_LEVEL
🔐 secretOPENFIGI_API_KEY25 req/min unauthenticated, 25 req/6s with a free OPENFIGI_API_KEY
configOIDC_CONFIG_URL3. Set in .env: (the IdP's .well-known/openid-configuration URL),
configOIDC_CLIENT_ID, OIDC_CLIENT_SECRET, OIDC_BASE_URL (your public URL). All four
🔐 secretOIDC_CLIENT_SECRETOIDC_CLIENT_ID, , OIDC_BASE_URL (your public URL). All four
configOIDC_BASE_URLOIDC_CLIENT_ID, OIDC_CLIENT_SECRET, (your public URL). All four
configOIDC_REDIRECT_PATH
// 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

10/10 tools missing one or more hints — get_quotes (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); compute_overlap (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); compare_etfs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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.

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 2 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/pierdom/etf-scout-mcp)](https://m8ven.ai/mcp/pierdom/etf-scout-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 8179d88d82f5f593fd3838b67c090f293894d325
code hash: 891f3ea0038559f7b0ebd0649ae095dce6ccafd66c6f3962f9a9082c1dbc524b
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