Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
eToll (rovinietă) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Check your cars' rovinietă on eToll, read its invoices, and buy a vignette you pay by card yourself.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user etoll-rovinieta-mcp '--' npx -y @foreverworks/mcp-etoll
# 2 — ask your agent for something these tools do
# health, session_status, begin_login and 12 more
eToll (rovinietă) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts eToll (rovinietă) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user etoll-rovinieta-mcp '--' npx -y @foreverworks/mcp-etollReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take ETOLL_USERNAME (The e-mail address or phone number you sign in to eToll with; leave empty to sign in through the browser instead.), ETOLL_PASSWORD_FILE (Path of a file holding only your eToll password; leave empty to sign in through the browser instead.) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Whether this server is configured: the eToll session it holds (none, present, expired), how it signed in, and where a password comes from if one is configured (never the password).
No parameter schema on file.
Is an eToll account signed in through this server: who, when the tokens expire, and what to do if not. With probe, refreshes once (or signs in with the configured
| Parameter | Type | Required | Notes |
|---|---|---|---|
| probe | boolean | no | Refresh, or sign in with the password, once to prove the session works. |
Sign in through the browser, for an account without a password configured here: answers with a URL the USER opens and signs in to eToll at
No parameter schema on file.
Finish a begun browser sign-in from the address the browser landed on (it carries code=... and state=...). Exchanges the code and stores the session in the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| redirect_url | string | yes | The whole address the browser landed on after signing in. |
Forget the stored session and tell Keycloak it is over. The user's own browser sign-in is not touched. With a password configured, the next call signs in again.
No parameter schema on file.
What a rovinietă costs for one vehicle from a start date: one option per duration (1 day to 12 months), each with its exact price in RON and the period it covers,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vehicle | yes | — | |
| start_date | yes | — |
Order the quoted vignette and hand over eToll's card payment page on euplatesc.ro; the USER pays there, nothing is paid here. The user confirms one line first
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | yes | — | |
| billing_id | yes | — |
An order placed by place_order: pending (not paid yet, with its payment page), paid, expired or cancelled, and its vignettes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | yes | — |
Drop an unpaid order (one place_order made, or one eToll names as already open for the same vignette). Safe to call twice. A paid order is refused: refunds go through eToll. An order eToll will not delete is refused with ORDER_NOT_DELETABLE, since it may be paid.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | yes | — |
The cars on the eToll account, each with its rovinietă: valid until which day (Bucharest), how many days are left, and the periods eToll says a new one may
No parameter schema on file.
The account's vignettes and other tolls (bridge passes), newest first, one page at a time: status, vehicle, period, price in RON, serial.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Only tolls in this status: ACTIVE (valid now or later), EXPIRED, and so on. An unpaid order is not a toll yet; get_order reads one. |
| plate | string | no | Only tolls for this plate number (spaces and dashes do not matter). |
| cursor | string | no | next_cursor from the previous page. |
| size | yes | — |
The invoices eToll issued for what the account paid, in a window of days (the last year by default): series and number, date, buyer, total in RON. The id is what download_invoice takes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | yes | — | |
| to | yes | — | |
| page | yes | — | |
| size | yes | — |
Save an invoice's PDF in this server's outbox; answers its path, SHA-256 and size, never the bytes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_id | yes | — |
What eToll has told the account (a vignette about to end, a payment received), and how many are unread.
No parameter schema on file.
CNAIR's public status page for eToll: each component (the portal, payments, the API), open incidents and planned maintenance. Needs no account.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install eToll (rovinietă) or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (15 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>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| health | no tags | |
| session_status | no tags | |
| begin_login | no tags | |
| complete_login | no tags | |
| logout | no tags | |
| quote_vignette | no tags | |
| place_order | no tags | |
| get_order | no tags | |
| cancel_order | no tags | |
| list_vehicles | no tags | |
| list_tolls | no tags | |
| list_invoices | no tags | |
| download_invoice | untrusted-input | untrusted-input: keyword "download" |
| notifications | no tags | |
| service_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish eToll (rovinietă) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.