rgo-trading-api (bhdhiman/rgo-trading-api) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 6 tools. No publisher has claimed this listing.

C
Limited view
71/100

rgo-trading-api

Enables AI assistants to read positions, deals, and orders from the RGO trading platform via natural language, with optional trading capabilities when explicitly enabled.

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

bhdhiman

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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 2 credentials: RGO_DEALER_PASSWORD, RGO_API_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.
configRGO_LICENSE_IDYour license id
configRGO_TIMEOUT
configRGO_DEALER_USERNAME/ RGO_DEALER_PASSWORD Dealer login (for the read JWT)
🔐 secretRGO_DEALER_PASSWORDRGO_DEALER_USERNAME / Dealer login (for the read JWT)
configRGO_API_USERNAME/ RGO_API_PASSWORD Header credentials for order writes
🔐 secretRGO_API_PASSWORDRGO_API_USERNAME / Header credentials for order writes
configRGO_CLIENT_BASEClient API base URL, e.g. https://api.YOUR_DOMAIN:6017/clientapi
configRGO_DEALER_BASE_READDealer read base URL (e.g. port 9016)
configRGO_DEALER_BASE_WRITEDealer write base URL (may use a different port, e.g. 6016)
configRGO_WS_URLRealtime WebSocket URL
configRGO_ALLOW_TRADINGbehind a config flag () and is off by default. Reads
// 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 — get_deals (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_pending_orders (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_positions (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.

Tool inputs are validated

3/6 tool handlers declare input schemas (50%)

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

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 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/bhdhiman/rgo-trading-api)](https://m8ven.ai/mcp/bhdhiman/rgo-trading-api)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e862487ced5b4f03a13867a61bb945f5abb45a1d
code hash: 9307865d17e4bd025c2058b4bc5e3b13b4181ca266cce66fd8ca7808b995e422
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