spock (jsj9346/spock) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
7 days ago

spock

→ jsj9346/spock· listed on github_code

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

jsj9346

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

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

// 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 10 credentials: DB_PASSWORD, POSTGRES_PASSWORD, SPOCK_MCP_API_KEY, KIS_APP_KEY, KIS_APP_SECRET, DART_API_KEY, BOK_API_KEY, OPENAI_API_KEY, EDINET_API_KEY, JQUANTS_PASSWORD
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.
configSPOCK_PROJECT_PATH
configDB_NAMEquant_platform
configDB_HOST
configDB_PORT
configDB_USER
🔐 secretDB_PASSWORDyour_password
configPOSTGRES_HOST
configPOSTGRES_PORT
configPOSTGRES_DB
configPOSTGRES_USER
🔐 secretPOSTGRES_PASSWORD
configCACHE_MAX_SIZE_MB
configCACHE_TTL_SECONDS
configBATCH_SIZE
configLOG_LEVEL
configLOG_DIR
🔐 secretSPOCK_MCP_API_KEY
configRATE_LIMIT_PER_MINUTE
🔐 secretKIS_APP_KEYyour_kis_app_key
🔐 secretKIS_APP_SECRETyour_kis_app_secret
🔐 secretDART_API_KEY
🔐 secretBOK_API_KEY
configKIS_ACCOUNT_NUMBER
configSNS_MAKENAIDE_TRADING_ALERTS_ARN
configSNS_MAKENAIDE_SYSTEM_ALERTS_ARN
configSNS_NOTIFICATIONS_ENABLED
configSNS_CRITICAL_ONLY
configSNS_MAX_DAILY_MESSAGES
configSNS_QUIET_START
configSNS_QUIET_END
configSNS_SPAM_PREVENTION_LEVEL
configSNS_TIME_WINDOW_MINUTES
configSNS_MAX_MESSAGES_PER_WINDOW
configSNS_DUPLICATE_DETECTION
configSNS_PATTERN_ANALYSIS
configSNS_COOLDOWN_MULTIPLIER
configSNS_SECURITY_MODE
configSNS_SENSITIVE_DATA_MASKING
configSNS_MESSAGE_ENCRYPTION
configSNS_AUDIT_LOGGING
configSNS_IP_FILTERING
configSNS_ALLOWED_SOURCES
configEC2_AUTO_SHUTDOWN
🔐 secretOPENAI_API_KEY
🔐 secretEDINET_API_KEY
configJQUANTS_ID
🔐 secretJQUANTS_PASSWORD
configSEC_USER_AGENT
// 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

22/22 tools missing one or more hints — call_tool_handler (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); run_backtest (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_available_tickers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 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.

Tool test coverage

14/22 tools referenced in tests (64%)

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

Secrets not logged

2 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 4 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/jsj9346-spock-fsunot)](https://m8ven.ai/mcp/jsj9346-spock-fsunot)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: d44f43847eb5b3eb9f0faf6883c60aa9935c882c
code hash: 8e79899846b8e91c25ea78af118b92a2a21992942f7b7a34a67fa1ab1c51df22
verified: 8/19/2026, 1:23:58 PM
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