Cambrian API

Name: Cambrian API
Author: cambriannetwork

作者：cambriannetwork版本 1.9.0i★ –i电脑或云端

注册名称io.github.cambriannetwork/cambrian-api

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: stdio, Streamable HTTP
分类: 其他
你需要填写：CAMBRIAN_API_KEY, Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： CAMBRIAN_API_KEY, Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接
npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

或者在你的电脑上运行

claude mcp add cambrian-api --env CAMBRIAN_API_KEY=your-value -- npx -y cambrian-api-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "cambrian-api": {
      "url": "https://mcp.cambrian.org/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "cambrian-api": {
      "type": "http",
      "url": "https://mcp.cambrian.org/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

CAMBRIAN_API_KEY 机密必填 env
Your Cambrian API key.
Authorization 机密必填 HTTP header
Bearer token in the form: Bearer

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 cambriannetwork 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32583 个服务器的 0%
发布到注册中心的时间比此分类中其他 32583 个服务器的 58% 更新
基础检查结果等于或优于此分类中其他 32583 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Cambrian API 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：CAMBRIAN_API_KEY, Authorization

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.9.0）于29天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, sync. labs

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211昨天更新

安装

sync. labs

作者：synchronicity-labs

Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.

电脑或云端今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

sync. labs

作者的 README

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