Mcity Data Engine MCP Server (mcity/mcity_MSight_agent) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 30 tools. No publisher has claimed this listing.

D
Caution
58/100

Mcity Data Engine MCP Server

Enables natural language interaction with complex computer vision workflows such as auto-labeling, class mapping, and embedding selection through an LLM-agnostic MCP orchestration layer.

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

mcity

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
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — detect_fisheye_intrinsics (line 109: dest.write_text(json.dumps(intrinsics, indent=2)))
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 10 credentials: OPENAI_API_KEY, GROQ_API_KEY, GEMINI_API_KEY, ANTHROPIC_API_KEY, CVAT_ACCESS_TOKEN, LS_TOKEN, AWS_SECRET_ACCESS_KEY, HF_TOKEN, AWS_ACCESS_KEY, AWS_SECRET_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.
configCUDA_VISIBLE_DEVICES
configLLM_PROVIDER
configMSIGHT_DEMO_VIDEO_PATH
configMSIGHT_MAX_UPLOAD_BYTES
🔐 secretOPENAI_API_KEY
configOPENAI_MODEL
🔐 secretGROQ_API_KEY
configGROQ_MODEL
🔐 secretGEMINI_API_KEY
configGEMINI_MODEL
🔐 secretANTHROPIC_API_KEY
configCLAUDE_MODEL
configCVAT_URL
🔐 secretCVAT_ACCESS_TOKEN
configMDE_UPLOAD_ROOT
configLS_URL
🔐 secretLS_TOKEN
configMSIGHT_VISION_PATH
configMSIGHT_RECORDING_SAVE_DIR
configAWS_ACCESS_KEY_ID
🔐 secretAWS_SECRET_ACCESS_KEY
configS3_BUCKET_NAME
configAWS_DEFAULT_REGION
🔐 secretHF_TOKEN
🔐 secretAWS_ACCESS_KEY
🔐 secretAWS_SECRET_KEY
configREGION
configOPENAIAPIKEY
configHFTOKEN
configANTHROPICAPIKEY
configGEMINIAPIKEY
configGROQAPIKEY
configLSTOKEN
configLSURL
configCVATACCESSTOKEN
configROLE_ARN
configKEY_PAIR_NAME
configINSTANCE_TYPE
configREDIS_HOST
configREDIS_PORT
configREDIS_DB
configCALIBRATION_TUTORIAL_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

30/30 tools missing one or more hints — configure_auto_labeling (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_auto_labeling_hyperparams (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_msight_localization_config (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +27 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — run_data_ingest deletes at line 361 (backup_path.unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — detect_fisheye_intrinsics (line 109: dest.write_text(json.dumps(intrinsics, indent=2)))

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

Tool test coverage

16/30 tools referenced in tests (53%)

Write tests that reference each tool by name so every tool has at least one test.

Tool description accuracy

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