HUTB Simulator MCP Server (changchujun/MCP-) is an MCP server listed on the M8ven Trust Index. It scores 52 out of 100, grade D. It declares 28 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
52/100

HUTB Simulator MCP Server

Enables AI interaction with embodied humans, autonomous vehicles, and drones through the HUTB simulator. Supports voice/chat control, weather conditions, perspective switching, and recording features.

→ changchujun/MCP-· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

changchujun

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

Glamanot scored here

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
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — get_sumo_info (line 430: result = subprocess.run()
✅
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: GITHUB_TOKEN, DEEPSEEK_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.
🔐 secretGITHUB_TOKEN
configGITHUB_BASE_URL
🔐 secretDEEPSEEK_API_KEY
configDEEPSEEK_API_URL
configMCP_SERVER_NAME
configMCP_SERVER_VERSION
configLOG_LEVEL
configCACHE_TTL
configGITHUB_API_RATE_LIMIT
configGITHUB_API_TIMEOUT
configSUMO_HOME
configSUMO_MCP_TRACI_TIMEOUT_S
configSUMO_MCP_MAX_OUTPUT_CHARS
// 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

28/28 tools missing one or more hints — connect_carla (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); spawn_vehicle (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_weather (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — get_sumo_info (line 430: result = subprocess.run()

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

23/28 tool handlers declare input schemas (82%)

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

Tool handlers catch errors

Only 13/28 tool handlers wrap calls in try/catch (46%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

get_sumo_info: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 7 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 Verified](https://m8ven.ai/badge/mcp/changchujun/mcp-?variant=verified)](https://m8ven.ai/mcp/changchujun/mcp-)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: bb079c02df4fa6addc88dfd19fa266680f90c51b
code hash: b822f8e3e4245d59d0ff04babb4237a720639c1e6ccd3d9239cd8f39a2030afd
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