# NexaLayer (npm · @nexalayer/mcp)

Managed proxy sessions, health, rotation, usage, and spend controls for AI agents.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@nexalayer/mcp`
- Version: `0.2.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**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to NexaLayer/nexalayer-agent).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1156 tokens (~72/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 68/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 4% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 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 NexaLayer MCP server?

NexaLayer runs locally as an npm package, launched with npx -y @nexalayer/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 nexalayer-nexalayer -- npx -y @nexalayer/mcp
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add nexalayer-nexalayer -- npx -y @nexalayer/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add nexalayer-nexalayer --command npx --arg -y --arg @nexalayer/mcp
```

### Hermes

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

### Netclaw

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

### Vellum

```bash
assistant mcp add nexalayer-nexalayer -t stdio -c npx -a -y @nexalayer/mcp
```

### Other

```json
{
  "mcpServers": {
    "nexalayer-nexalayer": {
      "command": "npx",
      "args": [
        "-y",
        "@nexalayer/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-05 (score 80, +1)

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

### 2026-11-03 (score 79, +1)

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

### 2026-11-01 (score 78, +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-10-30 (score 77, +1)

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

### 2026-10-28 (score 76, +1)

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

### 2026-10-26 (score 75, +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-24 (score 74, −4)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-21 (score 78, +1)

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

## MCP tools (16)

### `nexalayer_list_products` (~59 tokens)

List a compact catalog of current products and prices before purchasing.

Input parameters:

- `country` (string)
- `cursor` (string)
- `in_stock` (boolean)
- `limit` (integer)
- `type` (string)

### `nexalayer_create_session` (~164 tokens)

Create a paid network session. This action incurs charges against the account balance. Configure a budget first and obtain owner approval for autonomous spend. The create API does not honor include_credentials and omits proxy credentials; read the session with include_credentials=true. Credentials are omitted unless include_credentials=true; never log them. PRICE_MISMATCH (409: re-read prices, retry once). BUDGET_EXCEEDED and INSUFFICIENT_BALANCE (402: ask the owner, don't retry).

Input parameters:

- `country_code` (string)
- `duration` (integer)
- `idempotency_key` (string, required)
- `product_no` (string, required)
- `protocol` (string)
- `quantity` (integer)
- `session_type` (string, required)

### `nexalayer_get_session` (~48 tokens)

Read one session's status and proxy endpoint. Credentials are omitted unless include_credentials=true; never log them.

Input parameters:

- `include_credentials` (boolean)
- `session_id` (string, required)

### `nexalayer_rotate_session` (~67 tokens)

Rotate a dynamic session after health or telemetry recommends rotation. Credentials are omitted unless include_credentials=true; never log them.

Input parameters:

- `idempotency_key` (string, required)
- `include_credentials` (boolean)
- `reason` (string)
- `session_id` (string, required)

### `nexalayer_terminate_session` (~39 tokens)

Terminate a session and release its underlying network resource. Early termination does not imply a refund.

Input parameters:

- `session_id` (string, required)

### `nexalayer_session_health` (~29 tokens)

Read health score and rotation recommendation for a session.

Input parameters:

- `session_id` (string, required)

### `nexalayer_session_usage` (~28 tokens)

Read traffic and request usage for a session.

Input parameters:

- `session_id` (string, required)

### `nexalayer_get_budget` (~26 tokens)

Read spend limits, current spend, pause state, and next daily reset.

### `nexalayer_set_budget` (~81 tokens)

Set key and daily spend limits. This is a consequential write and should require owner approval.

Input parameters:

- `alert_thresholds` (array)
- `daily_limit_usd`
- `idempotency_key` (string, required)
- `key_limit_usd`
- `pause_on_exceed` (boolean)
- `paused` (boolean)

### `nexalayer_usage_alerts` (~18 tokens)

Read actionable budget threshold alerts.

### `nexalayer_get_balance` (~21 tokens)

Read the current account balance and trial-credit state.

### `nexalayer_list_transactions` (~34 tokens)

List billing transactions for audit and reconciliation.

Input parameters:

- `page` (integer)
- `page_size` (integer)

### `nexalayer_check_status` (~97 tokens)

Check NexaLayer service status before retrying or filing a ticket. Returns each component (api, sessions, billing, catalog, upstream_network) as operational, degraded_performance, partial_outage, major_outage, or under_maintenance, plus active incidents and recent incident history. If the component your call depends on is not operational, wait and retry later instead of reporting an issue. No API key needed; no charge.

### `nexalayer_known_issues` (~93 tokens)

List known issues with machine-runnable workaround steps. Call this with the error_code from a failed tool call (for example UPSTREAM_UNAVAILABLE or BACKEND_ERROR) before filing a ticket; if an issue matches, run its workaround.steps instead of reporting. No API key needed; no charge.

Input parameters:

- `component` (string)
- `error_code` (string)
- `status` (string)

### `nexalayer_report_issue` (~275 tokens)

File a support ticket with NexaLayer. Use only after following the error's suggested_action and checking nexalayer_check_status and nexalayer_known_issues. Recent request_ids and error codes seen by this MCP server are attached automatically, so you do not need to copy them. The server assigns severity (S1 outage or wrong billing, S2 broken with no workaround, S3 bug with a workaround, S4 question or feature request). Returns ticket_id and next_check_after_seconds; poll with nexalayer_get_ticket. Never include API keys, proxy passwords, or full_url: they are redacted and the ticket is escalated as a security issue. No charge.

Input parameters:

- `actual` (string)
- `category` (string, required)
- `desired_outcome` (string)
- `error_codes` (array)
- `expected` (string)
- `idempotency_key` (string): Reuse the same key when retrying so only one ticket is filed
- `known_issue_id` (string)
- `request_ids` (array)
- `session_id` (string)
- `severity_claimed` (string)
- `summary` (string, required)
- `tool` (string): The NexaLayer tool that failed, e.g. nexalayer_terminate_session

### `nexalayer_get_ticket` (~77 tokens)

Read a NexaLayer support ticket: status (received, triaged, needs_info, in_progress, awaiting_approval, workaround_available, resolved, closed), severity, events, matched known issue with workaround steps, and resolution. Poll no sooner than next_check_after_seconds. No charge.

Input parameters:

- `ticket_id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 38

## Common questions

### What is the NexaLayer MCP server?

NexaLayer is an MCP server listed in the public MCP registry as io.github.NexaLayer/nexalayer. Managed proxy sessions, health, rotation, usage, and spend controls for AI agents. This page covers its npm package (@nexalayer/mcp).

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

NexaLayer scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 NexaLayer MCP server expose?

NexaLayer exposes 16 tools: nexalayer_list_products, nexalayer_create_session, nexalayer_get_session, nexalayer_rotate_session, nexalayer_terminate_session, and 11 more. Their descriptions and schemas cost roughly 1,156 tokens of context every time the server is loaded.

### Is the NexaLayer MCP server still maintained?

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

NexaLayer 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/@nexalayer/mcp
- Socket report: https://socket.dev/npm/package/@nexalayer/mcp
- Repository: https://github.com/NexaLayer/nexalayer-agent
- Website: https://nexalayer.net/agents
- Changelog RSS feed: https://verifymcp.io/servers/nexalayer-nexalayer/nexalayer-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/nexalayer-nexalayer/nexalayer-mcp.json
- HTML version of this page: https://verifymcp.io/servers/nexalayer-nexalayer/nexalayer-mcp