NexaLayer
NPM · @NEXALAYER/MCP
Managed proxy sessions, health, rotation, usage, and spend controls for AI agents.
Available components
Last scanned (20 minutes ago)
Scores higher than 65% of npm servers
Category Cloud Infrastructure
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to NexaLayer/nexalayer-agent). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1156 tokens (~72/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 4% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +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.
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/@nexalayer/mcp@0.2.0
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 | NexaLayer/nexalayer-agent |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/NexaLayer/nexalayer-agent/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.2.0 |
| Rekor log index | 3319066728 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:75699c210138a5cb3914fe03642e5337ec7890d09bd740ac3fcb5077f80ca03ef8d71daa970451b26cb1cb94769f47fce4fce43e274409f38f7c56435 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
nexalayer_check_status ~97
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nexalayer_create_session ~164
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).
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | – |
| duration | integer | – | – |
| idempotency_key | string | yes | – |
| product_no | string | yes | – |
| protocol | string | – | – |
| quantity | integer | – | – |
| session_type | string | yes | – |
No output schema declared.
No examples provided.
nexalayer_get_balance ~21
Read the current account balance and trial-credit state.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nexalayer_get_budget ~26
Read spend limits, current spend, pause state, and next daily reset.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nexalayer_get_session ~48
Read one session's status and proxy endpoint. Credentials are omitted unless include_credentials=true; never log them.
| Name | Type | Req | Description |
|---|---|---|---|
| include_credentials | boolean | – | – |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
nexalayer_get_ticket ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
nexalayer_known_issues ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | – |
| error_code | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
nexalayer_list_products ~59
List a compact catalog of current products and prices before purchasing.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| cursor | string | – | – |
| in_stock | boolean | – | – |
| limit | integer | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
nexalayer_list_transactions ~34
List billing transactions for audit and reconciliation.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| page_size | integer | – | – |
No output schema declared.
No examples provided.
nexalayer_report_issue ~275
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actual | string | – | – |
| category | string | yes | – |
| 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 | yes | – |
| tool | string | – | The NexaLayer tool that failed, e.g. nexalayer_terminate_session |
No output schema declared.
No examples provided.
nexalayer_rotate_session ~67
Rotate a dynamic session after health or telemetry recommends rotation. Credentials are omitted unless include_credentials=true; never log them.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| include_credentials | boolean | – | – |
| reason | string | – | – |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
nexalayer_session_health ~29
Read health score and rotation recommendation for a session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
nexalayer_session_usage ~28
Read traffic and request usage for a session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
nexalayer_set_budget ~81
Set key and daily spend limits. This is a consequential write and should require owner approval.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_thresholds | array | – | – |
| daily_limit_usd | – | – | – |
| idempotency_key | string | yes | – |
| key_limit_usd | – | – | – |
| pause_on_exceed | boolean | – | – |
| paused | boolean | – | – |
No output schema declared.
No examples provided.
nexalayer_terminate_session ~39
Terminate a session and release its underlying network resource. Early termination does not imply a refund.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
nexalayer_usage_alerts ~18
Read actionable budget threshold alerts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
npm · @nexalayer/mcp
claude mcp add nexalayer-nexalayer -- npx -y @nexalayer/mcp
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.