# ONRC trade register (npm · @foreverworks/mcp-onrc)

Follow your filings at Romania's trade register, with their documents, fee notes and invoices.

- Trust score: 81/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@foreverworks/mcp-onrc`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-foreverworks-onrc/foreverworks-mcp-onrc.md), [page](https://verifymcp.io/servers/com-foreverworks-onrc/foreverworks-mcp-onrc)

## Channel facts

- Registry: `npm`
- Package: `@foreverworks/mcp-onrc`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 7 of 23 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to foreverworks/mcps).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 888 tokens (~98/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add com-foreverworks-onrc -- npx -y @foreverworks/mcp-onrc
```

### Cursor

```json
{
  "mcpServers": {
    "com-foreverworks-onrc": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-onrc"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-foreverworks-onrc": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-onrc"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-foreverworks-onrc -- npx -y @foreverworks/mcp-onrc
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-foreverworks-onrc": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@foreverworks/mcp-onrc"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-foreverworks-onrc --command npx --arg -y --arg @foreverworks/mcp-onrc
```

### Hermes

```yaml
mcp_servers:
  com-foreverworks-onrc:
    command: "npx"
    args: ["-y", "@foreverworks/mcp-onrc"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-foreverworks-onrc": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@foreverworks/mcp-onrc"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-foreverworks-onrc -t stdio -c npx -a -y @foreverworks/mcp-onrc
```

### Other

```json
{
  "mcpServers": {
    "com-foreverworks-onrc": {
      "command": "npx",
      "args": [
        "-y",
        "@foreverworks/mcp-onrc"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.88
- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 70)

First indexed and scored.

## MCP tools (9)

### `begin_login` (~84 tokens)

Begin login

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.

### `complete_login` (~88 tokens)

Complete login

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.

Input parameters:

- `redirect_url` (string, required): The whole address the browser landed on after the login.

### `get_request` (~83 tokens)

Get filing

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).

Input parameters:

- `id` (string, required): The filing's id (a UUID), from list_requests.

### `health` (~36 tokens)

Health

Whether this server is configured and holds a portal session (none, present, expired). No network. Run it before concluding the server is broken.

### `list_calculation_notes` (~122 tokens)

List calculation notes

"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.

Input parameters:

- `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.

### `list_invoices` (~110 tokens)

List invoices

"Facturile mele": the invoices the office issued for paid fees, with total, what was paid and what is outstanding.

Input parameters:

- `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.

### `list_requests` (~158 tokens)

List filings

"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.

Input parameters:

- `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.

### `logout` (~39 tokens)

Logout

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.

### `session_status` (~72 tokens)

Session status

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.

Input parameters:

- `probe` (boolean): Refresh once to prove the session still works.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-foreverworks-onrc/foreverworks-mcp-onrc#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 70

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@foreverworks/mcp-onrc
- Socket report: https://socket.dev/npm/package/@foreverworks/mcp-onrc
- Repository: https://github.com/foreverworks/mcps
- Website: https://foreverworks.github.io/mcps/servers/onrc/
- Changelog RSS feed: https://verifymcp.io/servers/com-foreverworks-onrc/foreverworks-mcp-onrc.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-foreverworks-onrc/foreverworks-mcp-onrc.json
- HTML version of this page: https://verifymcp.io/servers/com-foreverworks-onrc/foreverworks-mcp-onrc