Oracle Readiness MCP Server (stockem76/OracleReadinessSrc) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 45 tools. No publisher has claimed this listing.

C
Emerging
74/100
1 month ago

Oracle Readiness MCP Server

Scrapes Oracle Cloud readiness pages and provides MCP tools to search, filter, compare, and report on features across HCM, ERP, SCM, and Service pillars.

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

stockem76

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
45 tools verified — handlers match their declared behaviour
17 read-only tools verified — handlers contain no write/delete/exec
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 4 credentials: MCP_TOKEN, READINESS_ADMIN_PASS, READINESS_TOKEN, GITHUB_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.
configMCP_MODE
configMCP_PORT
🔐 secretMCP_TOKEN
configREADINESS_SESSION_HOURS
🔐 secretREADINESS_ADMIN_PASS
configREADINESS_DATA_DIR/data Data directory for SQLite DB and reports
configREADINESS_REFRESH_HOURS6 Hours between background refreshes
configREADINESS_AUTOSTART_REFRESH1 Set to 0 to disable background refresh
configREADINESS_HTTP_HOST
configREADINESS_HTTP_PORT8080 HTTP port to bind
🔐 secretREADINESS_TOKENIf is set:
🔐 secretGITHUB_TOKEN
configAPP_URL
// quality suggestions

Tool annotations

22/45 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

44/45 tools missing one or more hints — list_releases (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_product_families (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_modules (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +41 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

42/45 tool handlers declare input schemas (93%)

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

Tool handlers catch errors

Only 7/45 tool handlers wrap calls in try/catch (16%)

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/stockem76/oraclereadinesssrc)](https://m8ven.ai/mcp/stockem76/oraclereadinesssrc)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6b74779f484370987a17353efc61c29c0f57b90d
code hash: b904bfce9975d498599e413e2ec1ceeb6ffbaaa811efb4b8f4973dd3fdb23fb9
verified: 7/25/2026, 8:33:26 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