# Cerver (npm · @cerver/mcp)

AI backend for your app: a chat per customer, replies with their cost, spend caps per project.

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

## Components

- npm · `@cerver/mcp`: 61/100 (this document), [markdown](https://verifymcp.io/servers/eyal-gor-cerver/cerver-mcp.md), [page](https://verifymcp.io/servers/eyal-gor-cerver/cerver-mcp)

## Channel facts

- Registry: `npm`
- Package: `@cerver/mcp`
- Version: `0.1.1`
- 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**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 187 tokens (~62/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Cerver MCP server?

Cerver runs locally as an npm package, launched with npx -y @cerver/mcp. 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 eyal-gor-cerver -- npx -y @cerver/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "eyal-gor-cerver": {
      "command": "npx",
      "args": [
        "-y",
        "@cerver/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "eyal-gor-cerver": {
      "command": "npx",
      "args": [
        "-y",
        "@cerver/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add eyal-gor-cerver -- npx -y @cerver/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add eyal-gor-cerver --command npx --arg -y --arg @cerver/mcp
```

### Hermes

```yaml
mcp_servers:
  eyal-gor-cerver:
    command: "npx"
    args: ["-y", "@cerver/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "eyal-gor-cerver": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@cerver/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add eyal-gor-cerver -t stdio -c npx -a -y @cerver/mcp
```

### Other

```json
{
  "mcpServers": {
    "eyal-gor-cerver": {
      "command": "npx",
      "args": [
        "-y",
        "@cerver/mcp"
      ]
    }
  }
}
```

## 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 61)

First indexed and scored.

## MCP tools (3)

### `open_chat` (~91 tokens)

Open a Cerver chat session for one of your end-customers. Returns a session_id to pass to send_message. Cerver stores the conversation and attributes cost to this customer.

Input parameters:

- `customer_id` (string, required): Your id for the end-customer this chat is for (e.g. 'cust_amy' or a UUID). Don't pass an email or a name. Cost is rolled up per customer_id.

### `send_message` (~72 tokens)

Send a message in a Cerver chat session and get the assistant's reply plus what the message cost.

Input parameters:

- `message` (string, required): The user's message.
- `model` (string): Optional model id. Defaults to a fast, cheap model.
- `session_id` (string, required): The session_id returned by open_chat.

### `whoami` (~24 tokens)

Show which Cerver project this key is bound to (project slug + scope).

## Diagnostics

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

## Score history

- 2026-11-05: 61
- 2026-11-04: 61

## Common questions

### What is the Cerver MCP server?

Cerver is an MCP server listed in the public MCP registry as io.github.eyal-gor/cerver. AI backend for your app: a chat per customer, replies with their cost, spend caps per project. This page covers its npm package (@cerver/mcp).

### Is the Cerver MCP server safe to use?

Cerver scores 61 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 Cerver MCP server expose?

Cerver exposes 3 tools: open_chat, send_message, whoami. Their descriptions and schemas cost roughly 187 tokens of context every time the server is loaded.

### Is the Cerver MCP server still maintained?

Cerver 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 Cerver MCP server under?

Cerver 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/@cerver/mcp
- Socket report: https://socket.dev/npm/package/@cerver/mcp
- Website: https://cerver.ai/quickstart
- Changelog RSS feed: https://verifymcp.io/servers/eyal-gor-cerver/cerver-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/eyal-gor-cerver/cerver-mcp.json
- HTML version of this page: https://verifymcp.io/servers/eyal-gor-cerver/cerver-mcp