Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.udah1/hilan-mcp

NPM · HILAN-MCP

Pull Hilan (Hilanet / חילן, חילנט) payslips and Form 106 into any AI assistant.

Available components

0 this week 80 Trust /100

Last scanned (15 hours ago)

Scores higher than 66% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 67 of 178 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1189 tokens (~108/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 4 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/hilan-mcp@0.3.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 178 packages
Packages resolved 178
Deprecated 2
Stale 65
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,189 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
describeTable ~35

Get columns and indexes for a table (payslips or form106 only)

NameTypeReqDescription
tablestringyesTable to describe

No output schema declared.

No examples provided.

dismissUpdateNotice ~87

Call this after the user declines an update offered via an "_updateNotice" field on a previous tool response, passing that same version string, so hilan-mcp stops mentioning that specific version. It will still notify about a newer version later.

NameTypeReqDescription
versionstringyesThe version string from the _updateNotice you want to dismiss, e.g. "0.2.0"

No output schema declared.

No examples provided.

downloadCombinedPayslipsPdf ~187

Downloads ONE PDF covering every payslip in a date range (instead of one file per month) — handy for printing/sharing a multi-year span at once. Automatically splits into multiple files for very long ranges (Hilan's combined-PDF endpoint has a practical ceiling of roughly 12-15 years per file due to a URL-length limit on their end).

NameTypeReqDescription
fromMonthstringyesStart of the range (inclusive), "MM_YYYY" or "MM/YYYY", e.g. "01/2020"
tenantstring–Tenant subdomain, e.g. "amdocs". Optional if this server has COMPANY_URL / COMPANY_TENANT / COMPANY_CODE set in its env
toMonthstringyesEnd of the range (inclusive), "MM_YYYY" or "MM/YYYY", e.g. "12/2025"

No output schema declared.

No examples provided.

getPersonalDetails ~88

Logs in and fetches personal details (name, national ID, birthdate, address, phone, email, work start date, job type). This is a live lookup, not stored in the local database.

NameTypeReqDescription
tenantstring–Tenant subdomain, e.g. "amdocs". Optional if this server has COMPANY_URL / COMPANY_TENANT / COMPANY_CODE set in its env

No output schema declared.

No examples provided.

getSalaryTrends ~232

Computes salary growth trends from locally-synced payslips (no live login needed): yearly average Bruto/Neto, year-over-year % change between adjacent years, CAGR between the first and last full (12-month) calendar year, overall growth (first vs. last synced month), and notable jumps (>=10% YoY change in Bruto). Prefer this over raw `query` for "how has my salary grown" style questions — it also groups/sorts by actual calendar year, which plain `period` text sorting gets wrong across years (e.g. "01_2011" sorts before "02_2010").

NameTypeReqDescription
fromYearinteger–Only include calendar years >= this (e.g. 2015). Defaults to the earliest synced year.
tenantstring–Tenant subdomain, e.g. "amdocs". Optional if this server has COMPANY_URL / COMPANY_TENANT / COMPANY_CODE set in its env
toYearinteger–Only include calendar years <= this (e.g. 2024). Defaults to the latest synced year.

No output schema declared.

No examples provided.

listTables ~29

List queryable tables (payslips, form106 — credentials/sessions are never exposed here)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

listTenants ~19

List configured Hilan tenants (no secrets returned)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

query ~58

Execute a SELECT-only SQL query against payslips/form106 (allowlisted; credentials/sessions/tenants are never reachable)

NameTypeReqDescription
sqlstringyesSQL SELECT query, e.g. "SELECT * FROM payslips ORDER BY period DESC"

No output schema declared.

No examples provided.

resyncPayslipMonth ~186

Re-fetch a single specific month (structured data, and by default the PDF too), overwriting whatever is already stored for it. Use this to retry one bad/truncated PDF, or to quickly check one month's numbers, instead of re-running syncPayslips over the whole history.

NameTypeReqDescription
periodstringyesThe month to resync, as "MM_YYYY" (matches the stored period key) or "MM/YYYY", e.g. "10_2019" or "10/2019"
skipPdfboolean–If true, only fetch the structured Bruto/Neto/parts data and skip the PDF — fast, no browser download. Default false.
tenantstring–Tenant subdomain, e.g. "amdocs". Optional if this server has COMPANY_URL / COMPANY_TENANT / COMPANY_CODE set in its env

No output schema declared.

No examples provided.

syncForm106 ~98

Log into a Hilan tenant and download Form 106 (annual tax summary) for a given year, or the default year

NameTypeReqDescription
tenantstring–Tenant subdomain, e.g. "amdocs". Optional if this server has COMPANY_URL / COMPANY_TENANT / COMPANY_CODE set in its env
yearstring–Tax year, e.g. "2025" (defaults to the tenant's current default year)

No output schema declared.

No examples provided.

syncPayslips ~170

Log into a Hilan tenant (using previously ingested credentials) and sync recent payslips (structured Bruto/Neto/parts + PDF)

NameTypeReqDescription
monthsBackinteger–How many recent months to sync (default 3). The tenant itself caps how far back its payslip archive actually goes — this is just a sanity ceiling, not a real limit.
skipPdfboolean–If true, only fetch/store the structured Bruto/Neto/parts data and skip downloading PDFs — much faster for quick numeric questions. Any previously-downloaded PDF for a month is left untouched. Defaul…
tenantstring–Tenant subdomain, e.g. "amdocs". Optional if this server has COMPANY_URL / COMPANY_TENANT / COMPANY_CODE set in its env

No output schema declared.

No examples provided.

Install

How do I install the io.github.udah1/hilan-mcp server?

io.github.udah1/hilan-mcp runs locally as an npm package, launched with npx -y hilan-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · hilan-mcp

# add to Claude Code
claude mcp add udah1-hilan-mcp -- npx -y hilan-mcp
Common questions

What is the io.github.udah1/hilan-mcp server?

io.github.udah1/hilan-mcp is listed in the public MCP registry as io.github.udah1/hilan-mcp. Pull Hilan (Hilanet / חילן, חילנט) payslips and Form 106 into any AI assistant. This page covers its npm package (hilan-mcp).

Is the io.github.udah1/hilan-mcp server safe to use?

io.github.udah1/hilan-mcp scores 80 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.udah1/hilan-mcp server expose?

io.github.udah1/hilan-mcp exposes 11 tools: dismissUpdateNotice, listTenants, syncPayslips, downloadCombinedPayslipsPdf, getPersonalDetails, and 6 more. Their descriptions and schemas cost roughly 1,189 tokens of context every time the server is loaded.

Is the io.github.udah1/hilan-mcp server still maintained?

io.github.udah1/hilan-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.udah1/hilan-mcp server under?

io.github.udah1/hilan-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.udah1/hilan-mcp server?

VerifyMCP ran 16 checks on io.github.udah1/hilan-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.