ONRC trade register
NPM · @FOREVERWORKS/MCP-ONRC
Follow your filings at Romania's trade register, with their documents, fee notes and invoices.
Available components
Last scanned (2 hours ago)
Scores higher than 69% of npm servers
Category Documents and Files
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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 7 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to foreverworks/mcps). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 888 tokens (~98/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.88 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 70
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@foreverworks/mcp-onrc@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | foreverworks/mcps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/foreverworks/mcps/.github/workflows/release.yml@refs/tags/release-2026-11-03.2 |
| Rekor log index | 3658018607 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c494bdc57008fafee12d1b652f7dffc4592f195c173f0579861aca095d288b224df5a178e2c69aabad3f634ed4b4c7caa2c0eaae128f006e993f46ef5 |
Background: How many MCP packages publish verified provenance →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 7 |
| 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 →
begin_login Begin login ~84
Start signing in: answers with a URL the USER opens in the browser where they are already signed in to myportal.onrc.ro (Keycloak answers from that sign-in; no password or code is typed), and the redirect it ends on. Pass that address to complete_login. Open for 15 minutes; beginning again replaces it. Call this whenever a tool answers needs_login.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
complete_login Complete login ~88
Finish a begun login from the address the browser landed on (it carries code=... and state=...). Exchanges the code and stores the session in the service's own state; answers with who signed in and when the session expires. The code dies within a minute of being issued, so pass it at once.
| Name | Type | Req | Description |
|---|---|---|---|
| redirect_url | string | yes | The whole address the browser landed on after the login. |
No output schema declared.
No examples provided.
get_request Get filing ~83
One filing: its status in the office's words, the two terms (resolutionDue: by when the registrar decides; releaseDue: when the documents are released), whether files are ready to download, and the documents in its file (the signed application, resolutions, certificates once issued).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The filing's id (a UUID), from list_requests. |
No output schema declared.
No examples provided.
health Health ~36
Whether this server is configured and holds a portal session (none, present, expired). No network. Run it before concluding the server is broken.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_calculation_notes List calculation notes ~122
"Notele mele de calcul": the fee notes the office issued for the filings, with amount, status and the date to pay by. A filing with no fee has none.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day of the window, YYYY-MM-DD (Bucharest). Default: 365 days ago. |
| page | integer | – | Page, from 0, newest first. |
| size | integer | – | – |
| to | string | – | Last day of the window, YYYY-MM-DD (Bucharest). Default: today in Bucharest. |
No output schema declared.
No examples provided.
list_invoices List invoices ~110
"Facturile mele": the invoices the office issued for paid fees, with total, what was paid and what is outstanding.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day of the window, YYYY-MM-DD (Bucharest). Default: 365 days ago. |
| page | integer | – | Page, from 0, newest first. |
| size | integer | – | – |
| to | string | – | Last day of the window, YYYY-MM-DD (Bucharest). Default: today in Bucharest. |
No output schema declared.
No examples provided.
list_requests List filings ~158
"Cererile mele": the filings made from this portal account (a mențiune, an înmatriculare, a certificat constatator), newest first, with the portal number, the trade register number, the status (WORKING: still at the office), the company and whether a calculation note or an invoice exists. The id is what get_request takes.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | First day of the window, YYYY-MM-DD (Bucharest). Default: 365 days ago. |
| page | integer | – | Page, from 0, newest first. |
| size | integer | – | – |
| to | string | – | Last day of the window, YYYY-MM-DD (Bucharest). Default: today in Bucharest. |
No output schema declared.
No examples provided.
logout Logout ~39
Forget the stored session and tell Keycloak it is over. The user's own browser sign-in is not touched. Reads will answer needs_login until the next login.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
session_status Session status ~72
Is a portal account signed in through this server: who, when the access and refresh tokens expire, and what to do if not. With probe, refreshes once to prove the session is still honoured by Keycloak. Never shows a token.
| Name | Type | Req | Description |
|---|---|---|---|
| probe | boolean | – | Refresh once to prove the session still works. |
No output schema declared.
No examples provided.
How do I install the ONRC trade register MCP server?
ONRC trade register runs locally as an npm package, launched with npx -y @foreverworks/mcp-onrc. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @foreverworks/mcp-onrc
claude mcp add com-foreverworks-onrc -- npx -y @foreverworks/mcp-onrc
What is the ONRC trade register MCP server?
ONRC trade register is an MCP server listed in the public MCP registry as com.foreverworks/onrc. Follow your filings at Romania's trade register, with their documents, fee notes and invoices. This page covers its npm package (@foreverworks/mcp-onrc).
Is the ONRC trade register MCP server safe to use?
ONRC trade register scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 ONRC trade register MCP server expose?
ONRC trade register exposes 9 tools: begin_login, complete_login, get_request, health, list_calculation_notes, and 4 more. Their descriptions and schemas cost roughly 792 tokens of context every time the server is loaded.
Is the ONRC trade register MCP server still maintained?
ONRC trade register is still listed as active in the MCP registry. We last reached this channel on 5 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 ONRC trade register MCP server under?
ONRC trade register declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.