Kimai (jdlar) MCP Server
@jdlar/kimai-mcp
npm
v1.0.0
Published by @jdlar — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Kimai time-tracking — expose your Kimai instance as Model Context Protocol tools
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 44
Each tool and what it can reach — statically extracted from the published source.
kimai-add-team-activityno sensitive capabilitykimai-add-team-customerno sensitive capabilitykimai-add-team-memberno sensitive capabilitykimai-add-team-projectno sensitive capabilitykimai-create-activityno sensitive capabilitykimai-create-customerno sensitive capabilitykimai-create-projectno sensitive capabilitykimai-create-tagno sensitive capabilitykimai-create-teamno sensitive capabilitykimai-create-timesheetno sensitive capability
Show 34 more tools ↓
kimai-delete-tagno sensitive capabilitykimai-delete-teamno sensitive capabilitykimai-delete-timesheetno sensitive capabilitykimai-duplicate-timesheetno sensitive capabilitykimai-get-active-timesheetsno sensitive capabilitykimai-get-activityno sensitive capabilitykimai-get-customerno sensitive capabilitykimai-get-meno sensitive capabilitykimai-get-projectno sensitive capabilitykimai-get-recent-timesheetsno sensitive capabilitykimai-get-teamno sensitive capabilitykimai-get-timesheetno sensitive capabilitykimai-get-timesheet-configno sensitive capabilitykimai-get-userno sensitive capabilitykimai-get-versionno sensitive capabilitykimai-list-activitiesno sensitive capabilitykimai-list-customersno sensitive capabilitykimai-list-projectsno sensitive capabilitykimai-list-tagsno sensitive capabilitykimai-list-teamsno sensitive capabilitykimai-list-timesheetsno sensitive capabilitykimai-list-usersno sensitive capabilitykimai-pingno sensitive capabilitykimai-remove-team-activityno sensitive capabilitykimai-remove-team-customerno sensitive capabilitykimai-remove-team-memberno sensitive capabilitykimai-remove-team-projectno sensitive capabilitykimai-restart-timesheetno sensitive capabilitykimai-stop-timesheetno sensitive capabilitykimai-update-activityno sensitive capabilitykimai-update-customerno sensitive capabilitykimai-update-projectno sensitive capabilitykimai-update-teamno sensitive capabilitykimai-update-timesheetno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (44 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 99/100 | 0 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @jdlar/kimai-mcp --onlineOther implementations of Kimai 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
MCP server for read-only access to Kimai time-tracking instances.
MCP server for Kimai time-tracking API integration
More in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.