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

C
Emerging
74/100
7 days ago

hilan-mcp

An MCP server that lets AI assistants pull payslips and Form 106 from any Hilan (Hilanet) tenant, using a headless browser and Hilan's internal endpoints to provide structured data and PDFs.

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

udah1

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
🚨
Known vulnerabilities in dependencies: 1 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: HILAN_DB_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@1.6.1GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configCOMPANY_CODEis used, in this order — COMPANY_URL → COMPANY_TENANT → :
configCOMPANY_TENANTis used, in this order — COMPANY_URL → → COMPANY_CODE:
configCOMPANY_URLis used, in this order — → COMPANY_TENANT → COMPANY_CODE:
🔐 secretHILAN_DB_KEY2. env var — set it in the server's env block (see
configHILAN_UPDATE_CHECK_STATE_DIR
configXDG_DATA_HOME
// quality suggestions

Dependencies

9 runtime dependencies (6 dev), 1 flagged: playwright

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

13/13 tools missing one or more hints — dismissUpdateNotice (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); listTenants (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); syncPayslips (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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

11/13 tool handlers declare input schemas (85%)

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

Tool test coverage

Only 3/13 tools referenced in tests (23%)

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

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 5 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/udah1/hilan-mcp)](https://m8ven.ai/mcp/udah1/hilan-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b1c2ac36492efac7098b35c06874ae2cd0ef0efa
code hash: d5d3c3e2157a9863d37402f006e2fb0b12339498312c2bd5c738171c76fce17d
verified: 9/4/2026, 5:45:31 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