Back to MCP Trust Indexm8ven
C
Limited view
67/100
14 days ago

sap_parent_mcp

→ gymishra/sap_parent_mcp· listed on github_code

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

gymishra

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
🚨
Secret credentials may flow to a network call
2 flows detected: OKTA_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 5 credentials: OKTA_CLIENT_SECRET, SAP_BEARER_TOKEN, CALM_CLIENT_SECRET, SF_CLIENT_SECRET, CALM_API_KEY
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.
configAGENTCORE_ARN
configAWS_REGION
configOKTA_CLIENT_ID
🔐 secretOKTA_CLIENT_SECRET
configOKTA_DOMAIN
configSAP_BASE_URL
🔐 secretSAP_BEARER_TOKEN
configCALM_TENANT
configCALM_REGION
configCALM_TOKEN_URL
configCALM_CLIENT_ID
🔐 secretCALM_CLIENT_SECRET
configSF_COMPANY_ID
configSF_TOKEN_URL
configSF_DC
configSF_CLIENT_ID
🔐 secretSF_CLIENT_SECRET
configCALM_TOKEN_ENDPOINT
configCALM_API
configCALM_REPORTER
configADT_AGENT_URL
configODATA_AGENT_URL
configCALM_AGENT_URL
configSF_AGENT_URL
configGENERATOR_AGENT_URL
configOKTA_AUTH_SERVER
configOKTA_SCOPES
configOKTA_REDIRECT_URI
configAGENTCORE_ARN_SSM_PARAM
configCALM_SANDBOX
🔐 secretCALM_API_KEY
configLOCAL_MCP_URL
configAGENTCORE_RUNTIME_ARN
configLOCAL_AGENT_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

165/165 tools missing one or more hints — get_business_partners (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_business_partner_by_id (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_sales_orders (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +162 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 inputs are validated

84/94 tool handlers declare input schemas (89%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

55/94 tool handlers wrap calls in try/catch (59%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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 6 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/gymishra-sap-parent-mcp-1aiwy0)](https://m8ven.ai/mcp/gymishra-sap-parent-mcp-1aiwy0)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 32c5c51c17f13b2050f86e1a8a0db565218a621b
code hash: 487925e3a014c23fdbca4bc5e9fb0ab31e01d2d39c0db6d5f1dd2d8b047330e2
verified: 8/8/2026, 8:17:28 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