JPYC Commerce MCP (ackey-web/JPYC-commerce-mcp) 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
2 months ago

JPYC Commerce MCP

Enables autonomous AI agents to conduct non-custodial commerce using JPYC stablecoin on Polygon, with trust scoring, task evaluation, negotiation, and on-chain verification via Soulbound Tokens.

→ ackey-web/JPYC-commerce-mcp· listed on glama

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

ackey-web

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glama

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 6 credentials: ANTHROPIC_API_KEY, DEPLOYER_PRIVATE_KEY, POLYGONSCAN_API_KEY, PRIVATE_KEY, RELAYER_API_KEY, RELAYER_PRIVATE_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 medium

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

medium@anthropic-ai/sdk@0.82.0GHSA-p7fg-763f-g4gf

Claude SDK for TypeScript has Insecure Default File Permissions in Local Filesystem Memory Tool

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.
configAMOY_RPC_URL"": "https://rpc-amoy.polygon.technology",
🔐 secretANTHROPIC_API_KEYsk-ant-... # Claude API (for task evaluation)
configAUTO_APPROVE_LIMIT_BRONZE
configAUTO_APPROVE_LIMIT_GOLD
configAUTO_APPROVE_LIMIT_PLATINUM
configAUTO_APPROVE_LIMIT_SILVER
configBOUNTY_ADMIN_ADDRESS
configBOUNTY_ESCROW_ADDRESS
configBOUNTY_EXPIRY_DAYS
configCHAIN_ID80002 # 80002=Amoy, 137=Mainnet
🔐 secretDEPLOYER_PRIVATE_KEY
configESCROW_WALLET_ADDRESS
configGAS_MAX_FEE_PER_GAS
configGAS_MAX_PRIORITY_FEE_PER_GAS
configHUMAN_APPROVAL_THRESHOLD_JPYC
configINSECURE_TEST_BYPASS_APPROVALSEC-3: =false by default — demo-mode auto-skip removed
configJPYC_ADDRESS
configJPYC_ADDRESS_AMOY
configJPYC_CONTRACT_ADDRESS0x431D5dfF03120AFA4bDf332c61A6e1766eF37BF # JPYC v2 ERC-20
configMAX_FEE_PER_GAS
configMAX_PRIORITY_FEE_PER_GAS
configNEGOTIATION_TTL_HOURS
🔐 secretPOLYGONSCAN_API_KEY
configPOLYGON_RPC_URL
🔐 secretPRIVATE_KEY
🔐 secretRELAYER_API_KEY
🔐 secretRELAYER_PRIVATE_KEY
configRELAYER_PROVIDER
configRELAYER_URL
configSBT_CONTRACT_ADDRESS
configSBT_CONTRACT_ADDRESS_AMOY0x... # TrustSBT on Amoy (after deploy)
configTRUST_SCORE_REGISTRY_ADDRESS
configVITE_ALCHEMY_RPC_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_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

19/19 tools missing one or more hints — get_sbt_profile (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); evaluate_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); propose_negotiation (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 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 handlers catch errors

Only 0/19 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 3/19 tools referenced in tests (16%)

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

Production dependencies are patched

1 medium severity in production deps

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

Dependency freshness

1/7 production deps stale: keccak256@2022-05-07 (4.1y)

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/ackey-web-jpyc-commerce-mcp-1sshrc)](https://m8ven.ai/mcp/ackey-web-jpyc-commerce-mcp-1sshrc)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 767e11353ef82236904f3d7afc67931e2f676009
code hash: 3339ad8e00d9d71a7ab8fd1e13027467177be4126c3c4d839e50d6c6b3fe04d2
verified: 6/24/2026, 10:24:57 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