NexaLayer

Name: NexaLayer
Author: NexaLayer

by NexaLayerversion 0.2.0i★ –iRuns on your computer

Registry nameio.github.NexaLayer/nexalayer

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Clinics & health
You need to fill in: NEXALAYER_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: NEXALAYER_API_KEY, NEXALAYER_BASE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "nexalayer": {
      "command": "npx",
      "args": [
        "-y",
        "@nexalayer/mcp"
      ],
      "env": {
        "NEXALAYER_API_KEY": "your-value",
        "NEXALAYER_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add nexalayer --env NEXALAYER_API_KEY=your-value --env NEXALAYER_BASE_URL=your-value -- npx -y @nexalayer/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "nexalayer": {
      "command": "npx",
      "args": [
        "-y",
        "@nexalayer/mcp"
      ],
      "env": {
        "NEXALAYER_API_KEY": "your-value",
        "NEXALAYER_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nexalayer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@nexalayer/mcp"
      ],
      "env": {
        "NEXALAYER_API_KEY": "your-value",
        "NEXALAYER_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

NEXALAYER_API_KEY secret required env
NexaLayer API key requested at https://nexalayer.net/agents?source=mcp-registry
NEXALAYER_BASE_URL env
Optional API base URL. Defaults to https://api.nexalayer.net/v1

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account NexaLayer, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

More stars than 0% of the other 865 servers in this category
Published to the registry more recently than 60% of the other 865 servers in this category
Basic checks equal to or better than 100% of the other 865 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is NexaLayer safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: NEXALAYER_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 19 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated 5 days ago

Install

FHIR MCP Server

by wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 8 days ago

Install

Google Health MCP

by davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

Runs on your computer★ 79MITUpdated 4 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

NexaLayer MCP Server

This directory contains the MCP server package and implementation. For the repository overview, installation options, complete 16-tool catalog, and backend relationship, see the root README.

Connect an MCP client to NexaLayer products, sessions, health, usage, and spend controls.

"mcpServers": { "nexalayer": { "command": "npx", "args": ["-y", "@nexalayer/mcp"], "env": { "NEXALAYER_API_KEY": "agk_your_key" } } } }

The server writes protocol messages only to stdout. API errors go through MCP tool results. Tool annotations mark reads, paid writes, policy changes, and destructive cleanup so compatible clients can apply approval policies.

Tools

Read: products and exact prices, session detail, health, usage, budget, alerts, balance, and transactions.
Paid write: create or rotate a Session. Use a unique idempotency_key and owner approval.
Policy write: change API-Key and daily budget limits. Require owner approval.
Cleanup: terminate a Session when the task ends. Early termination does not imply a refund. If the upstream is down, billing stops at the first terminate attempt and NexaLayer retries the release in the background.
Support (no charge): nexalayer_check_status, nexalayer_known_issues, nexalayer_report_issue, and nexalayer_get_ticket.

nexalayer_list_products returns a compact, cursor-paginated catalog. It defaults to 20 currently available products, supports type, country, in_stock, limit, and cursor, and excludes internal pricing and supplier fields.

nexalayer_create_session incurs charges against the account balance. Read the current quote and budget, then obtain owner approval before calling it. POST /sessions does not honor include_credentials and omits proxy credentials. PRICE_MISMATCH (409): re-read prices, retry once. BUDGET_EXCEEDED and INSUFFICIENT_BALANCE (402): ask the owner, don't retry.

nexalayer_get_session and nexalayer_rotate_session accept optional include_credentials (default false) and pass it to the API. Credentials are omitted unless include_credentials=true; never log them.

Always read nexalayer_list_products before purchase because it returns the current openAgent-backed quote and availability. Exclusive static proxy sessions are $1.43–$5.86/month (launch pricing, live API authoritative).

nexalayer_list_products → nexalayer_get_budget → owner approval

→ nexalayer_create_session → nexalayer_get_session → health/usage → nexalayer_terminate_session

Common API error codes include AUTH_INVALID_KEY, INSUFFICIENT_BALANCE, BUDGET_EXCEEDED, PRICE_MISMATCH, IDEMPOTENCY_CONFLICT, and RATE_LIMIT_EXCEEDED.

PRICE_MISMATCH is HTTP 409: re-read prices, retry once. BUDGET_EXCEEDED and INSUFFICIENT_BALANCE are HTTP 402: ask the owner, don't retry.

Errors and support

Failed API calls return an MCP tool error (isError: true) with a one-line summary and the full NexaLayer error object in structuredContent.error: code, retryable, retry_after, suggested_action, side_effects, doc_url, known_issue_id, and request_id. Branch on those fields, not on the message text.

When an error is not self-explanatory:

follow error.suggested_action → nexalayer_check_status → nexalayer_known_issues(error_code)

→ nexalayer_report_issue → poll nexalayer_get_ticket after next_check_after_seconds

The server keeps the last 20 request ids and error codes it saw and attaches them to nexalayer_report_issue automatically, along with the MCP client name and package version. Never put API keys, proxy passwords, or full_url in a ticket. Response targets are early-access targets, not guarantees: S1 4h, S2 24h, S3 3 business days, S4 best effort. Human contact: support@nexalayer.net (Telegram @LEWISMIN).

Docker

Build the stdio MCP server from the repository root:

docker build -t nexalayer-mcp ./mcp

The container can start and expose its tool catalog without credentials, which allows MCP directories and clients to inspect it safely:

docker run -i --rm nexalayer-mcp

Pass the API Key only at runtime when calling NexaLayer tools:

docker run -i --rm \

-e NEXALAYER_API_KEY="$NEXALAYER_API_KEY" \ nexalayer-mcp

NEXALAYER_BASE_URL remains optional. The image uses stdio and does not expose a network port or contain credentials.

Request an API key and one-time trial credit at https://nexalayer.net/agents?source=mcp-readme.

NexaLayer

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Google Health MCP

README from the maker

NexaLayer MCP Server

Tools

Errors and support

Docker