meegle-cli-mcp (yingcaihuang/meegle-cli-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 34 tools. No publisher has claimed this listing.

C
Caution
74/100
1 month ago

meegle-cli-mcp

Enables interaction with Meegle project management via local CLI, supporting work items, views, charts, teams, and workflows through natural language in MCP clients like VS Code.

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

yingcaihuang

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
19 tools describe read intent but their handlers mutate — auth_status (line 70: spawn('meegle', args, {); project_search (line 70: spawn('meegle', args, {); workitem_meta_types (line 70: spawn('meegle', args, {)
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// 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

34/34 tools missing one or more hints — auth_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); project_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); workitem_meta_types (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +31 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

19 tools describe read intent but their handlers mutate — auth_status (line 70: spawn('meegle', args, {); project_search (line 70: spawn('meegle', args, {); workitem_meta_types (line 70: spawn('meegle', args, {)

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

Tool inputs are validated

33/34 tool handlers declare input schemas (97%)

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

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.

Tool description accuracy

16 tools have description/behavior mismatches: workitem_meta_types: description implies read-only but handler writes/deletes/executes; workitem_meta_fields: description implies read-only but handler writes/deletes/executes; workitem_discover_status_values: 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/yingcaihuang/meegle-cli-mcp?variant=verified)](https://m8ven.ai/mcp/yingcaihuang/meegle-cli-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 58a0374ae44596261a48c9f3bee71339a23b722b
code hash: 1def7cba380840c9720a578870e6bed3eab21444772bb420aee25e5088bc756a
verified: 7/26/2026, 8:40: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