C
Emerging
74/100
11 days ago

OpenRoost

MCP server for agents to play videogames

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

theReuben

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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
35 tools verified — handlers match their declared behaviour
15 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.
// 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.
configMC_HOST
configMC_PORT
configMC_USERNAME
configMC_VERSION
configMC_VIEWER_PORT
configOPENROOST_STATE_FILE
// quality suggestions

All four hints declared on every tool

35/35 tools missing one or more hints — attack_entity (missing: readOnlyHint, idempotentHint, openWorldHint); cancel_task (missing: readOnlyHint, openWorldHint); check_inventory (missing: destructiveHint, idempotentHint, openWorldHint), +32 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

30/35 tool handlers declare input schemas (86%)

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

Tool handlers catch errors

Only 17/35 tool handlers wrap calls in try/catch (49%)

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

README present

No README found

Add a README.md describing the server and its tools.

License file

No license file

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

Dependency freshness

1/9 production deps stale: mineflayer-pathfinder@2023-09-04 (2.9y)

Domain consistency

npm scope @openroost doesn't match GitHub owner thereuben

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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/thereuben-openroost-jbpogk)](https://m8ven.ai/mcp/thereuben-openroost-jbpogk)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1caff7b00f1a5a1428f3fb15358da401d9d08fa3
code hash: c6123f32858915eb15a242a571e53797c08326e594b21f812271fd9f992f78a3
verified: 8/8/2026, 7:43:41 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