Peil
PYPI · PEIL-MCP
Log hours, draft invoices and check where you stand — finance for Dutch freelancers.
Available components
Last scanned (10 hours ago)
Scores higher than 57% of PyPI servers
Category Finance and Payments
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 41 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1939 tokens (~80/item across 24 items; 24 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_invoice" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 25 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
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- Provenance in Provenance & TransparencyBuild provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale.
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 →
Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.
Repository
- Registry says
https://github.com/Luminc/peil-mcp- Package shows
Luminc/invoice-app
The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale. See the evidence →
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.
- 21 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 0
- Stability: 0.97 → pass security
- 19 Nov 26 0
- Stability: pass → 0.97 functional
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 12 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.
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 pypi/peil-mcp@0.1.5
Provenance Repository mismatch
The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.
| Result | Repository mismatch |
|---|---|
| Ecosystem | pypi |
| Reason | Repository mismatch |
| Discovered via | Registry attestation endpoint |
| Source repo | Luminc/invoice-app |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Luminc/invoice-app/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.1.5 |
| Rekor log index | 3185798389 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:206b9f124b58ccd08512af57be9674d33308856c1e14a0076d675756fb9f5713 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
archive_invoice ~33
Archive an invoice (hidden from default views, kept for records). Requires invoices:write.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
cancel_scheduled_send ~28
Cancel a previously scheduled send. Requires invoices:send.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_client ~59
Create a new client. Requires clients:write. Set a default_rate so hours logged for this client aren't billed at €0.
| Name | Type | Req | Description |
|---|---|---|---|
| default_rate | – | – | – |
| – | – | – | |
| name | string | yes | – |
| payment_terms_days | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_expense ~126
Add a one-off business expense, as on the receipt: the total paid and the Dutch btw in it. `category` is a key or label (e.g. "travel", "Software en abonnementen"); equipment from €450 excl. btw is written off over five years automatically. Requires the expenses:write permission. Restate the values to the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| date | string | yes | – |
| name | string | yes | – |
| notes | – | – | – |
| total | number | yes | – |
| vat | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_client ~46
Delete a client. Destructive — confirm first. Blocked (409) if the client has projects or sent/paid invoices. Requires clients:write.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_hours ~52
Delete a time entry. Destructive — confirm with the user first. Entries on a sent/paid/archived invoice are blocked server-side. Requires timesheet:write.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_invoice ~50
Delete an invoice. Destructive — confirm first. Paid invoices can't be deleted (archive instead); sent invoices are blocked unless the user is sure. Requires invoices:write.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
draft_invoice ~109
Create a DRAFT invoice from a client's unbilled hours in a period. Nothing is sent to the client — the user reviews the draft in Peil (or asks explicitly to send it via send_invoice). Grouping: 'summary' (one line per description), 'by_project', or 'per_day'. Requires invoices:write.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| grouping | string | – | – |
| period_end | string | yes | – |
| period_start | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
edit_hours ~93
Edit an existing time entry. Only the fields you pass are changed. Confirm with the user before editing an entry that's already on a sent/paid invoice (the server blocks it with INVOICE_LOCK). Requires timesheet:write.
| Name | Type | Req | Description |
|---|---|---|---|
| client | – | – | – |
| date | – | – | – |
| description | – | – | – |
| entry_id | integer | yes | – |
| hours | – | – | – |
| project | – | – | – |
| rate | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_client_details ~29
Show a client's details, including whether a default rate is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_reminder_copy ~20
Show the user's custom reminder email copy and schedule.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_clients ~23
List the user's clients (names to use with the other Peil tools).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_expenses ~52
List the one-off expenses of a year (default: this year), newest first. Monthly costs (rent, AOV, pension) live in Peil's cost list, not here.
| Name | Type | Req | Description |
|---|---|---|---|
| year | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_invoices ~35
List invoices, most recent first. Optionally filter by status and/or client.
| Name | Type | Req | Description |
|---|---|---|---|
| client | – | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_unbilled ~41
List billable hours not yet on any invoice, grouped per client.
| Name | Type | Req | Description |
|---|---|---|---|
| client | – | – | – |
| period_end | – | – | – |
| period_start | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
log_hours ~89
Log worked hours for a client in Peil's timesheet. Omit `rate` to use the client's default rate. `date` is ISO YYYY-MM-DD. Requires the timesheet:write key permission.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| date | string | yes | – |
| description | string | yes | – |
| hours | number | yes | – |
| project | – | – | – |
| rate | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
orientation_snapshot ~24
Where does the user stand financially? Outstanding, overdue, drafts, YTD.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
schedule_send ~87
Schedule a DRAFT invoice to be emailed at a future time. Client-facing. `scheduled_at` is an ISO datetime (e.g. 2026-07-20T09:00:00). Only call this when the user has explicitly confirmed sending this invoice at this time. Requires invoices:send.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | – |
| scheduled_at | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
send_invoice ~63
Send an invoice to the client BY EMAIL. Irreversible and client-facing. `invoice` is a numeric id or invoice number. Only call this when the user has explicitly confirmed sending this specific invoice. Requires invoices:send.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
send_reminder ~56
Email a payment reminder for a sent/overdue invoice. Irreversible, client-facing. Only call this when the user has explicitly confirmed reminding about this specific invoice. Requires invoices:send.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_invoice_status ~72
Change an invoice's status (e.g. mark paid). Requires invoices:write. `invoice` is a numeric id or invoice number. This does NOT email anyone — it only records the status. Use send_invoice to actually email the client.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | – |
| status | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_reminder_copy ~105
Set the reminder email copy for one tone/language. Requires invoices:write. Tones: pre_due (before due date), overdue (0–7 days late), formal (>7 days). Other tones/languages are preserved. Use {invoice_number}, {total_amount}, {due_date} placeholders as in Peil's editor.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| lang | string | – | – |
| subject | string | yes | – |
| tone | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_client ~55
Update a client's details. Only the fields you pass change. Requires clients:write.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| default_rate | – | – | – |
| – | – | – | |
| name | – | – | – |
| payment_terms_days | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_invoice ~66
Update safe invoice fields (due date, payment date, notes). Requires invoices:write. Line items and amounts are not edited here — redraft from hours for those.
| Name | Type | Req | Description |
|---|---|---|---|
| due_date | – | – | – |
| invoice | string | yes | – |
| notes | – | – | – |
| payment_date | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Peil MCP server?
Peil runs locally as a PyPI package, launched with uvx peil-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · peil-mcp
claude mcp add app-peil-peil-mcp -- uvx peil-mcp
What is the Peil MCP server?
Peil is an MCP server listed in the public MCP registry as app.peil/peil-mcp. Log hours, draft invoices and check where you stand, finance for Dutch freelancers. This page covers its PyPI package (peil-mcp).
Is the Peil MCP server safe to use?
Peil scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 Peil MCP server expose?
Peil exposes 24 tools: list_clients, log_hours, list_unbilled, draft_invoice, send_invoice, and 19 more. Their descriptions and schemas cost roughly 1,413 tokens of context every time the server is loaded.
Is the Peil MCP server still maintained?
Peil 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 Peil MCP server under?
Peil 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 Peil MCP server?
VerifyMCP ran 14 checks on Peil, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about Peil: Malware scan and Provenance. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.