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

Back to MCP Trust IndexM8ven
C
Emerging
74/100
8 days ago

Juspay MCP Tools

Enables AI agents to interact with Juspay's payment processing APIs and merchant dashboard for managing orders, transactions, refunds, customers, gateways, and reporting through natural language.

→ juspay/juspay-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

juspay

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
🚨
Secret credentials may flow to a network call
8 flows detected: JUSPAY_AI_STUDIO_TOKEN, JUSPAY_WEB_LOGIN_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 8 credentials: JUSPAY_WEB_LOGIN_TOKEN, PP_AI_STUDIO_API_KEY, PP_AI_STUDIO_TOKEN, JUSPAY_AI_STUDIO_TOKEN, JUSPAY_API_KEY, CLI_ANALYTICS_INGEST_TOKEN, OAUTH_CLIENT_SECRET, OAUTH_DEV_TEST_TOKEN
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.
configJUSPAY_MCP_TYPE
🔐 secretJUSPAY_WEB_LOGIN_TOKEN
configJUSPAY_MERCHANT_ID
configJUSPAY_ENV
configPP_AI_STUDIO_BASE_URL
configJUSPAY_AI_STUDIO_BASE_URL
🔐 secretPP_AI_STUDIO_API_KEY
🔐 secretPP_AI_STUDIO_TOKEN
🔐 secretJUSPAY_AI_STUDIO_TOKEN
configJUSPAY_PROD_BASE_URL
configJUSPAY_SANDBOX_BASE_URL
configINCLUDE_RESPONSE_SCHEMA
🔐 secretJUSPAY_API_KEY
configDEPLOYMENT_ENV
configCLI_ANALYTICS_KMS_REGION
configAWS_REGION
🔐 secretCLI_ANALYTICS_INGEST_TOKEN
configCLI_ANALYTICS_INGEST_URL
configMCP_SERVER_URL
configPORTAL_BASE_URL
configOAUTH_CLIENT_ID
🔐 secretOAUTH_CLIENT_SECRET
configOAUTH_STATE_TTL_SECONDS
configOAUTH_VALIDATION_CACHE_TTL_SECONDS
🔐 secretOAUTH_DEV_TEST_TOKEN
configOAUTH_DEV_TEST_MERCHANT_ID
// 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

6/6 tools missing one or more hints — handle_tool_calls (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_131 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); handle_tool_calls (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +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.

Secrets not logged

4 secret values sent to logger.info

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/juspay/juspay-mcp)](https://m8ven.ai/mcp/juspay/juspay-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: cff2a5dec74964dbfae592aa74f7e511d37af207
code hash: 92776767532374f2a35859592c461e214ab6921267ad726c682ca268609d0327
verified: 9/2/2026, 8:02:49 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