Cambrian API

Name: Cambrian API
Author: cambriannetwork

by cambriannetworkversion 1.9.0i★ –iComputer or cloud

Registry nameio.github.cambriannetwork/cambrian-api

Install

Overview

Description from the maker (original English)

Cambrian API MCP: Solana and EVM DeFi data, Deep42 social intelligence, and perpetual risk analysis.

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: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: CAMBRIAN_API_KEY, Authorization

Install

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

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: CAMBRIAN_API_KEY, Authorization

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

You need

Runs in the cloudNothing to install; it connects over the internet
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 …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

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

{
  "mcpServers": {
    "cambrian-api": {
      "command": "npx",
      "args": [
        "-y",
        "cambrian-api-mcp"
      ],
      "env": {
        "CAMBRIAN_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http cambrian-api https://mcp.cambrian.org/mcp --header 'Authorization: your-value'

Or run it on your computer

claude mcp add cambrian-api --env CAMBRIAN_API_KEY=your-value -- npx -y cambrian-api-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": {
    "cambrian-api": {
      "url": "https://mcp.cambrian.org/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "cambrian-api": {
      "command": "npx",
      "args": [
        "-y",
        "cambrian-api-mcp"
      ],
      "env": {
        "CAMBRIAN_API_KEY": "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": {
    "cambrian-api": {
      "type": "http",
      "url": "https://mcp.cambrian.org/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "cambrian-api": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "cambrian-api-mcp"
      ],
      "env": {
        "CAMBRIAN_API_KEY": "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 address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

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

Values you fill in

CAMBRIAN_API_KEY secret required env
Your Cambrian API key.
Authorization secret required HTTP header
Bearer token in the form: Bearer

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

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account cambriannetwork, 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 checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32572 servers in this category
Published to the registry more recently than 58% of the other 32572 servers in this category
Basic checks equal to or better than 100% of the other 32572 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 Cambrian API 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: CAMBRIAN_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

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

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, AvaHR

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

AvaHR

by avahr.com

Read hiring data and create inactive assessment and questionnaire drafts for human review.

Runs in the cloudUpdated today

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.

Cambrian API MCP

Model Context Protocol server for the Cambrian API. It exposes the same product surface as the cambrian CLI for agents that need live DeFi, social intelligence, risk, and API documentation tools.

Every call needs a Cambrian API key supplied by the caller. The hosted server and local package both require one; the server never ships or proxies a shared key. Create a key at https://console.cambrian.org/. For x402 pay-per-call access without an API key, use cambrian pay --help; MCP transport still requires a caller-supplied key.

What You Get

a progressive default profile with one concise tool per public Cambrian API endpoint
compact and full profiles for clients with different tool-loading behavior
a composite workflow tool for Solana token snapshots
cambrian_docs for live endpoint and guide docs from https://docs.cambrian.org/llms.txt
stdio transport for local MCP clients
Streamable HTTP transport for hosted and self-hosted deployments

Tool Profiles

Profile	stdio	HTTP	Tool metadata
Progressive (default)	no flag, or `--profile progressive`	`/mcp`	Direct endpoint tools with types, required fields, scalar enums, OpenAPI defaults, numeric bounds, and array item types.
Compact	`--profile compact`	`/mcp/compact`	Three tools: `cambrian_docs`, `cambrian_call`, and `cambrian_solana_token_snapshot`.
Full	`--profile full`	`/mcp/full`	Direct endpoint tools with complete request descriptions, defaults, constraints, and response-size controls.

All profiles use the same progressive documentation flow. cambrian_docs returns the request schema by default. Set detail to response for response fields. The response view also includes the request schema. Set detail to full only for examples and all endpoint prose. The full profile does not preload response documentation for every endpoint.

Progressive omits repeated endpoint descriptions, long patterns, large array enums, and parameter prose. Call cambrian_docs for these details.

Progressive also omits offset, order_asc, and order_desc. These three are the same on every endpoint that has them, and Progressive already strips the per-endpoint sortable-column enum, so repeating them adds about 10 kB to the tool list and tells the agent nothing. The server instructions name them once, and every endpoint still accepts them. limit stays, with its maximum, because it is how an agent bounds a response.

Toolsets

The whole catalog is 159 tools. An agent that only asks about Solana still pays for 116 EVM tools it will never call. Use --toolsets to load only what you need.

Toolset	Tools
`solana`	`cambrian_solana_*` and the Solana token snapshot
`evm`	`cambrian_base_`, `cambrian_ethereum_`, `cambrian_arbitrum_`, and `cambrian_robinhood_`
`deep42`	`cambrian_deep42_*`
`risk`	`cambrian_risk_*`

npx -y cambrian-api-mcp --toolsets solana,risk

CAMBRIAN_TOOLSETS=solana npx -y cambrian-api-mcp

Over HTTP, select per request: https://mcp.cambrian.org/mcp?toolsets=solana.

Omit the option, or pass all, to get every tool. cambrian_docs is always present, so a narrowed client can still discover and read about any endpoint.

Progressive tools/list sizes:

Selection	Tools	Bytes
default (all)	159	39,571
`evm`	117	28,158
`solana`	37	10,904
`deep42`	6	3,663
`risk`	2	2,093

How MCP Clients Load Tools

The MCP client receives the complete tools/list result for the selected profile. MCP does not control how much of that result enters the model context.

Claude Code normally loads tool names and server instructions first. It loads complete selected tool definitions after Tool Search. Codex can do the same when its Tool Search feature is available. Other clients can load every tool definition at the start.

The client loads the definition from the selected profile. It does not restore fields that Progressive omitted. Use cambrian_docs to load the complete request schema, response fields, and examples.

Agent Skill

New users and agent runtimes should start here: skills/cambrian-mcp/SKILL.md. It covers Cambrian API key auth, hosted and local client config, tool naming, cambrian_docs lookup, composite tools, response limits, and error handling in one document.

For the CLI instead of MCP, see the cambrian CLI skill.

Recommended Setup Through The CLI

The cambrian CLI prints and tests ready-to-use MCP client config:

npm install -g cambrian

cambrian mcp config --mode hosted cambrian mcp config --mode local cambrian mcp install --client claude --mode hosted cambrian mcp test --mode hosted

Local stdio

Run the published package directly:

export CAMBRIAN_API_KEY=<your-api-key>

npx -y cambrian-api-mcp

Select another profile only when your MCP client needs it:

npx -y cambrian-api-mcp --profile compact

npx -y cambrian-api-mcp --profile full

Narrow the catalog to the toolsets you need:

npx -y cambrian-api-mcp --toolsets solana,risk

Or install it globally:

npm install -g cambrian-api-mcp

export CAMBRIAN_API_KEY= cambrian-api-mcp

Hosted Streamable HTTP

Use the CLI to print the current hosted URL and client-specific config:

cambrian mcp config --mode hosted

Direct Claude setup:

claude mcp add --transport http cambrian \

https://mcp.cambrian.org/mcp \ --header "Authorization: Bearer YOUR_CAMBRIAN_API_KEY"

Codex config uses TOML:

[mcp_servers.cambrian]

url = "https://mcp.cambrian.org/mcp" bearer_token_env_var = "CAMBRIAN_API_KEY"

The default URL uses the progressive profile. Use https://mcp.cambrian.org/mcp/compact or https://mcp.cambrian.org/mcp/full for another profile.

HTTP requests must include one of:

Authorization: Bearer <CAMBRIAN_API_KEY>

X-Cambrian-Api-Key:

Self-Hosted HTTP

npm install

npm run build node dist/index.js --transport http --host 127.0.0.1 --port 8080

Health endpoint:

curl http://127.0.0.1:8080/health

For hosted deployments, bind to 0.0.0.0:

node dist/index.js --transport http --host 0.0.0.0 --port 8080

Tool Names

Tool names are canonical and prefixed with cambrian_.

Examples:

cambrian_base_dexes
cambrian_ethereum_dexes
cambrian_arbitrum_dexes
cambrian_robinhood_dexes
cambrian_solana_price_current
cambrian_deep42_social_data_alpha_tweet_detection
cambrian_risk_perp_risk_engine
cambrian_docs
cambrian_solana_token_snapshot

Call cambrian_docs without a path to discover the live root index, or use guides/ (for example, guides/x402) for any guide listed there. For an endpoint path, omit detail to get its request schema. Use detail: "response" for response fields and detail: "full" for examples and all endpoint prose.

Endpoint tools come from the same validated runtime registry as the CLI. MCP rechecks that local cache for each tool-list/tool-call request, while OpenAPI network attempts are coalesced and limited to once per source every 15 minutes. If runtime discovery is unavailable, the server uses the endpoint metadata bundled with the installed cambrian package (cambrian/metadata). Tool names, schemas, and argument validation come from cambrian/tools, so each tool sends the same request as the matching cambrian CLI command.

The API serves one generic /api/v1/evm/* surface whose chain_id parameter lists the chains each endpoint supports. The MCP turns that into one fixed-chain tool per supported chain, so an agent never has to remember a magic number and cannot aim an endpoint at a chain it rejects:

Chain	Id	Tool prefix
Base	`8453`	`cambrian_base_*`
Ethereum	`1`	`cambrian_ethereum_*`
Arbitrum	`42161`	`cambrian_arbitrum_*`
Robinhood Chain	`4663`	`cambrian_robinhood_*`

A tool appears for a chain if and only if that endpoint's own chain_id schema allows the chain — from its enum, a fixed minimum/maximum pair, or an exclusive bound. No allowlist and no per-endpoint special case: an endpoint the API widens to include another registered chain ID gains that chain's tools on the next metadata load. Base tools fix chain_id to 8453, Ethereum tools to 1, Arbitrum tools to 42161, and Robinhood tools to 4663.

cambrian_docs accepts an optional chain segment in an EVM path, by id or slug: evm/42161/dexes, evm/arbitrum/dexes, and evm/dexes all resolve the same endpoint, with the chain-scoped forms returning that chain's pinned schema. Robinhood paths also accept evm/4663/dexes and evm/robinhood/dexes.

The chain table comes from the cambrian CLI (EVM_CHAINS in cambrian/tools). src/server.ts adds only cambrian_docs path aliases. To add a chain, add it to the CLI, release the CLI, and bump cambrian here.

Development

npm ci

npm test npm run build npm pack --dry-run

The package depends on the published cambrian package for shared metadata and the API client. Publish cambrian first when changing both packages together, then refresh this package lock and deploy the MCP server through CI/CD.

Deployment

Deployments are handled by GitHub Actions and Cloud Run from the private source repository. Do not deploy manually.

The workflow:

installs dependencies
validates package.json#mcpName matches server.json#name
validates package.json#version matches server.json#version
builds and tests
builds the Docker image
deploys to Cloud Run
smoke-checks staging directly; production is smoke-tested through the public edge URL after DNS and certificate activation

Registry

The official MCP Registry publishes this server under:

io.github.cambriannetwork/cambrian-api

The manifest uses https://mcp.cambrian.org/mcp, which matches the production edge URL. The public release workflow publishes each new Registry version after npm publication.

Cambrian API

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

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 Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

AvaHR

README from the maker

Cambrian API MCP

What You Get

Tool Profiles

Toolsets

How MCP Clients Load Tools

Agent Skill

Recommended Setup Through The CLI

Local stdio

Hosted Streamable HTTP

Self-Hosted HTTP

Tool Names

Development

Deployment

Registry