alpaca-guard-mcp (evidai/agent-payment-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

C
Emerging
74/100
3 months ago

alpaca-guard-mcp

Alpaca trading API with a hard daily USD cap enforced server-side. Paper trading by default — live trading blocked until you explicitly opt in.

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

evidai

Source: Glama

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

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

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: GITHUB_OAUTH_CLIENT_ID. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 11 credentials: ALPACA_API_KEY, ALPACA_SECRET_KEY, CDP_API_PRIVATE_KEY, GITHUB_OAUTH_CLIENT_SECRET, GOOGLE_OAUTH_CLIENT_SECRET, LEMONCAKE_PAY_TOKEN, LEMONCAKE_SELLER_KEY, LEMON_CAKE_PAY_TOKEN, RESEND_API_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_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.
configADMIN_EMAILS
🔐 secretALPACA_API_KEY
configALPACA_GUARD_ALLOW_LIVE
configALPACA_GUARD_LEDGER_DIR
configALPACA_PAPER_TRADE
🔐 secretALPACA_SECRET_KEY
configCDP_API_KEY_ID
🔐 secretCDP_API_PRIVATE_KEY
configCLOUD_RUN_URL
configGITHUB_OAUTH_CLIENT_ID
🔐 secretGITHUB_OAUTH_CLIENT_SECRET
configGOOGLE_APPLICATION_CREDENTIALS_JSON
configGOOGLE_OAUTH_CLIENT_ID
🔐 secretGOOGLE_OAUTH_CLIENT_SECRET
configGOOGLE_SERVICE_ACCOUNT_JSON
configGOOGLE_SHEETS_CONTACT_ID
configGOOGLE_SHEETS_CONTACT_SHEET
🔐 secretLEMONCAKE_PAY_TOKEN
configLEMONCAKE_SANDBOX_BASE
🔐 secretLEMONCAKE_SELLER_KEYthen add a Seller Key in /app and set → it charges for real (no code change)
🔐 secretLEMON_CAKE_PAY_TOKEN
configPRICE_PER_CALL
🔐 secretRESEND_API_KEY
🔐 secretSTRIPE_SECRET_KEY
🔐 secretSTRIPE_WEBHOOK_SECRET
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_API_URL
deployNEXT_PUBLIC_APP_URL
deployNEXT_PUBLIC_COINBASE_PROJECT_ID
deployNEXT_PUBLIC_GA_ID
deployNEXT_PUBLIC_PRIVY_APP_ID
deployNEXT_PUBLIC_TRANSAK_API_KEY
deployPORT
deployPOSTGRES_URL
deployPOSTGRES_URL_NON_POOLING
// quality suggestions

Tool annotations

8/9 tools have annotations

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

All four hints declared on every tool

6/9 tools missing one or more hints — setup (missing: destructiveHint); guard_status (missing: destructiveHint); get_account (missing: destructiveHint), +3 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 3 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/evidai/agent-payment-mcp)](https://m8ven.ai/mcp/evidai/agent-payment-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 020faed8d9538a9b32ea1993e290e5641a583bab
code hash: 173060242f62a115c025d096d76e8c55486b95c704c1cf0b7a41459567eb54c8
verified: 6/11/2026, 11:13:13 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