# b1-mcp-server for SAP B1 (npm · b1-mcp-server)

MCP server for SAP Business One database (HANA / MS SQL) and Service Layer operations

- Trust score: 76/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `b1-mcp-server`: 76/100 (this document), [markdown](https://verifymcp.io/servers/bersimao-b1-mcp-server/b1-mcp-server.md), [page](https://verifymcp.io/servers/bersimao-b1-mcp-server/b1-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `b1-mcp-server`
- Version: `1.6.0`
- 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**: 98/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.
  - 54 of 165 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1354 tokens (~193/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_sql" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the b1-mcp-server for SAP B1 server?

b1-mcp-server for SAP B1 runs locally as an npm package, launched with npx -y b1-mcp-server. 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 bersimao-b1-mcp-server -- npx -y b1-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "bersimao-b1-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "b1-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bersimao-b1-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "b1-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add bersimao-b1-mcp-server -- npx -y b1-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bersimao-b1-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "b1-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bersimao-b1-mcp-server --command npx --arg -y --arg b1-mcp-server
```

### Hermes

```yaml
mcp_servers:
  bersimao-b1-mcp-server:
    command: "npx"
    args: ["-y", "b1-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "bersimao-b1-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "b1-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add bersimao-b1-mcp-server -t stdio -c npx -a -y b1-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "bersimao-b1-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "b1-mcp-server"
      ]
    }
  }
}
```

## 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 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 60, −9)

- [security regression] Malware scan: pass → unverified
- [security improvement] CVE-2023-54404 no longer affects this package
- [security improvement] Known CVEs: fail → pass
- [functional] Package version: 1.5.2 → 1.6.0

### 2026-10-31 (score 69, +1)

- [security improvement] CVE-2026-109461 no longer affects this package

### 2026-10-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 67, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 51, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 1.5.1 → 1.5.2

### 2026-10-25 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `connect_database` (~194 tokens)

Switch the active database and Service Layer connection to a different SAP Business One environment.
Searches connection profiles by ID or database name (case-insensitive). Partial matches are only accepted when they resolve to a single profile.

Each profile can include DirectDb (DB) credentials, Service Layer (SL) credentials, or both.
When switching environments, each stale or non-matching side is disconnected before replacement; a healthy side that still matches the selected profile remains active.
If only one side connects successfully, it remains active - retry the failed side after fixing credentials.
Tracks failed login attempts per profile and warns about account lockout risk under the configured login policy.

Available profiles:
  (no profiles loaded)

Use "list" as the query to reload and list all available profiles.

Input parameters:

- `query` (string, required): The database identifier to connect to. Can be the profile ID or database name. Use "list" to see all available profiles.

### `execute_sql` (~264 tokens)

Execute a raw SQL statement against the currently connected database. All SQL, whether written by the user or generated by you, goes through the same server-side validation.

IMPORTANT: Before calling this tool, you MUST confirm which database the user intends to query. If the user has not explicitly stated the target database in their message, ASK them first. Do NOT assume the currently connected database is the intended target.

READ-ONLY: only SELECT (and read-only DO BEGIN...END blocks) execute. Data-changing statements are blocked server-side.

If the user needs a write (INSERT/UPDATE/DELETE), do NOT call this tool — generate the SQL and give it to the user to run in a real DB client (HANA Studio / DBeaver / hdbsql), where a human can review the statement and control its transaction handling.

Rules enforced server-side:
\- READ-ONLY: INSERT/UPDATE/DELETE/DROP are blocked for everyone — no confirmation bypass.
\- Direct EXEC/EXECUTE/CALL: blocked (stored procedures are disabled).
\- CREATE/ALTER: blocked.
\- MS SQL pass-through (OPENQUERY/OPENROWSET/OPENDATASOURCE): blocked.

Input parameters:

- `query` (string, required): The SQL statement to execute (SELECT only — read-only server)

### `get_schema_info` (~149 tokens)

Retrieve metadata about tables, columns, or procedures in the currently connected database.
Read-only. Use this to explore the schema before writing queries.
For "columns": provide the table name in "filter". For "tables"/"procedures": filter is optional (LIKE pattern).

IMPORTANT: Before calling this tool, you MUST confirm which database the user intends to query. If the user has not explicitly stated the target database in their message, ASK them first. Do NOT assume the currently connected database is the intended target.

Input parameters:

- `filter` (string): For columns: table name (required). For tables/procedures: optional LIKE pattern.
- `objectType` (string, required): Type of metadata to retrieve

### `execute_service_layer` (~121 tokens)

Execute a read-only OData GET against the currently connected SAP Business One Service Layer. Writes go through execute_service_layer_write.

Denied when the connected profile's slAllowedMethods (printed by connect_database) omits GET. Query options are allowed; absolute URLs, Login/Logout and $batch are denied.

Input parameters:

- `method` (string): Always GET. PATCH, POST and DELETE go through execute_service_layer_write
- `url` (string, required): Relative OData endpoint without the configured /b1s/v1/ or /b1s/v2/ root

### `execute_service_layer_write` (~355 tokens)

Execute a guarded OData write (PATCH, POST or DELETE) against the currently connected SAP Business One Service Layer. These are real writes to the company database.

The verb must be in the connected profile's slAllowedMethods, and database must equal the connected Service Layer database exactly — connect_database prints both. A mismatch is denied.

Approval follows the profile's slWriteApproval, also printed by connect_database. "elicitation" (default): the server asks the user through an MCP approval form; clients without form elicitation cannot write. "client" or "none": the server executes after this client's own permission prompt, honoured only for Claude Code. On a "none" profile, prefer execute_service_layer_write_unattended, which does the same write without any approval; use this tool there only when the user asks to confirm the write. MCP_DRY_RUN previews but never executes a write, and MCP_SL_WRITES_ENABLED=false disables every write globally.

PATCH and DELETE accept one directly keyed entity endpoint only. POST accepts an entity set, a service operation, or one action on a keyed entity (Orders(12)/Close). Query options, navigation paths, absolute URLs, Login/Logout and $batch are denied.

Input parameters:

- `body` (object): JSON object: required and non-empty for PATCH, optional for POST, forbidden for DELETE
- `database` (string, required): Connected company database exactly as connect_database prints it; shown to the approver and checked by the server
- `method` (string, required): Must also be allowed by the connected profile's slAllowedMethods
- `url` (string, required): Relative OData endpoint without the configured /b1s/v1/ or /b1s/v2/ root

### `execute_service_layer_write_unattended` (~223 tokens)

Execute a guarded OData write (PATCH, POST or DELETE) with NO approval of any kind, for development companies. Denied unless the connected profile has slWriteApproval "none" (printed by connect_database); otherwise use execute_service_layer_write. These are real writes to the company database.

Every other rule of execute_service_layer_write applies unchanged: database must equal the connected Service Layer database, the verb must be in slAllowedMethods, the same endpoint shapes are enforced, MCP_DRY_RUN previews and MCP_SL_WRITES_ENABLED=false disables it.

Input parameters:

- `body` (object): JSON object: required and non-empty for PATCH, optional for POST, forbidden for DELETE
- `database` (string, required): Connected company database exactly as connect_database prints it; shown to the approver and checked by the server
- `method` (string, required): Must also be allowed by the connected profile's slAllowedMethods
- `url` (string, required): Relative OData endpoint without the configured /b1s/v1/ or /b1s/v2/ root

### `check_connection` (~48 tokens)

Check if the database and Service Layer connections are active and alive.
Pings DirectDb (SELECT query) and Service Layer (GET request) independently.
No parameters required. Reports status for both connections.

## Diagnostics

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

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 60
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67
- 2026-10-27: 67
- 2026-10-26: 51
- 2026-10-25: 66
- 2026-10-24: 65
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 68

## Common questions

### What is the b1-mcp-server for SAP B1 server?

b1-mcp-server for SAP B1 is listed in the public MCP registry as io.github.bersimao/b1-mcp-server. MCP server for SAP Business One database (HANA / MS SQL) and Service Layer operations. This page covers its npm package (b1-mcp-server).

### Is the b1-mcp-server for SAP B1 server safe to use?

b1-mcp-server for SAP B1 scores 76 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. 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 b1-mcp-server for SAP B1 server expose?

b1-mcp-server for SAP B1 exposes 7 tools: connect_database, execute_sql, get_schema_info, execute_service_layer, execute_service_layer_write, and 2 more. Their descriptions and schemas cost roughly 1,354 tokens of context every time the server is loaded.

### Is the b1-mcp-server for SAP B1 server still maintained?

b1-mcp-server for SAP B1 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 b1-mcp-server for SAP B1 server under?

b1-mcp-server for SAP B1 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/b1-mcp-server
- Socket report: https://socket.dev/npm/package/b1-mcp-server
- Repository: https://github.com/bersimao/b1-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/bersimao-b1-mcp-server/b1-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/bersimao-b1-mcp-server/b1-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/bersimao-b1-mcp-server/b1-mcp-server