LIMU Portal MCP (gochi20/limuMCP) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
1 month ago

LIMU Portal MCP

MCP server for LIMU Portal that provides read-only and controlled write access to operational and finance data, including clients, cargo, shipments, budgets, requisitions, payment vouchers, and reports.

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

gochi20

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

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

// key findings
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: LIMU_ADMIN_PASSWORD, LIMU_ADMIN_TOKEN, LIMU_DB_PASSWORD, LIMU_OAUTH_CLIENT_SECRET
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.
configLIMU_ADMIN_EMAILThe registration script needs either LIMU_ADMIN_TOKEN or /LIMU_ADMIN_PASSWORD in local .env. Do not set those admin credentials in Vercel.
🔐 secretLIMU_ADMIN_PASSWORDThe registration script needs either LIMU_ADMIN_TOKEN or LIMU_ADMIN_EMAIL/ in local .env. Do not set those admin credentials in Vercel.
🔐 secretLIMU_ADMIN_TOKENThe registration script needs either or LIMU_ADMIN_EMAIL/LIMU_ADMIN_PASSWORD in local .env. Do not set those admin credentials in Vercel.
configLIMU_DB_CONNECTION_LIMIT
configLIMU_DB_HOST"": "127.0.0.1",
configLIMU_DB_NAME"": "limutradee",
🔐 secretLIMU_DB_PASSWORD
configLIMU_DB_PORT"": "3306",
configLIMU_DB_SOCKET
configLIMU_DB_USER"": "root",
configLIMU_MCP_DEFAULT_LIMIT
configLIMU_MCP_MAX_LIMIT
configLIMU_OAUTH_CLIENT_IDlimu-vercel-mcp
configLIMU_OAUTH_CLIENT_NAME
🔐 secretLIMU_OAUTH_CLIENT_SECRET
configLIMU_OAUTH_REDIRECT_URI
configLIMU_OAUTH_REDIRECT_URIS
configLIMU_PORTAL_BASE_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

10/10 tools missing one or more hints — limu_health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); limu_get_clients (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); limu_get_client (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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

5/10 tool handlers declare input schemas (50%)

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

Tool handlers catch errors

Only 0/10 tool handlers wrap calls in try/catch (0%)

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/gochi20-limumcp-1wm813)](https://m8ven.ai/mcp/gochi20-limumcp-1wm813)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 40f7b48c9a9b0eed3c85ecd944c273ab49f11f2b
code hash: f657e321577c52c31fd46b4cca2883a0275d9fdc57d3f8bcbe61b10da564d683
verified: 7/9/2026, 10:00:25 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