Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
320 AI models + 2,720 pay-per-call APIs. x402 USDC on Base or Solana, no API key.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.jarvisclaw.ai/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"jarvisclaw": {
"command": "npx",
"args": [
"-y",
"jarvisclaw-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add --transport http jarvisclaw https://api.jarvisclaw.ai/mcpclaude mcp add jarvisclaw -- npx -y jarvisclaw-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"jarvisclaw": {
"url": "https://api.jarvisclaw.ai/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"jarvisclaw": {
"command": "npx",
"args": [
"-y",
"jarvisclaw-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"jarvisclaw": {
"type": "http",
"url": "https://api.jarvisclaw.ai/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"jarvisclaw": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jarvisclaw-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.jarvisclaw.ai/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 api-jarvisclaw 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.1.0)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
283 AI models and 2,720 pay-per-call APIs through one MCP server. Settles in USDC on Base or Solana over x402 — no account, no API key, no subscription.
Three ways to reach a service:
chat tool, or auto to let the router pick.web_search, image_generation, translation…) and AIP resolves it to a provider, so the caller never has to know the URL layout.Counts move as the catalogue changes; list_models, search_apis and aip_list_intents are the live answer.
Run this package. It presents itself to your client as a normal stdio MCP server, forwards every request to the gateway, and when a call needs paying it signs the x402 payment on your machine and retries. Your private key is never transmitted — only the signed payment payload is.
JARVISCLAW_WALLET_KEY=0xyourkey npx jarvisclaw-mcp
Claude Desktop / Cursor, Base wallet:
{
"mcpServers": { "jarvisclaw": { "command": "npx", "args": ["-y", "jarvisclaw-mcp"], "env": { "JARVISCLAW_WALLET_KEY": "0xYOUR_BASE_PRIVATE_KEY", "JARVISCLAW_CHAIN": "base" } } } }
Solana wallet:
{
"mcpServers": { "jarvisclaw": { "command": "npx", "args": ["-y", "jarvisclaw-mcp"], "env": { "JARVISCLAW_WALLET_KEY": "YOUR_SOLANA_BS58_SECRET_KEY", "JARVISCLAW_CHAIN": "solana" } } } }
For Claude Code, Cursor, or any client with Streamable HTTP transport. One less hop, but there is no wallet in this path: free tools work, and paid tools need a pre-paid API key, because nothing here can sign a payment.
{
"mcpServers": { "jarvisclaw": { "type": "url", "url": "https://api.jarvisclaw.ai/mcp", "headers": { "Authorization": "Bearer sk-your-api-key" } } } }
Without the header the same URL still lists the catalogue for free; paid tools answer with an x402 quote that you would have to sign yourself.
| Variable | Required | Default | Description |
|---|---|---|---|
JARVISCLAW_WALLET_KEY | for paid tools | — | Base private key (0x… hex) or Solana secret key (base58). Used only for local signing. |
JARVISCLAW_CHAIN | no | base | base or solana. Which option to sign when the server offers both. |
JARVISCLAW_MCP_URL | no | https://api.jarvisclaw.ai/mcp | Remote MCP endpoint. |
JARVISCLAW_SOLANA_RPC | no | public mainnet RPC | Custom Solana RPC (recommended — the public one is rate-limited). |
JARVISCLAW_API_KEY | no | — | Optional API key sent as Authorization: Bearer. Free tools need no credential. |
| Tool | What it does | Billed |
|---|---|---|
list_models | Every model available, with the IDs to pass to chat | free |
search_apis | Search the 2,720-endpoint marketplace; each hit carries its path and price | free |
aip_list_intents | Browse the intent types AIP can route | free |
aip_estimate_cost | Price an intent before committing to it | free |
chat | Any model, OpenAI-compatible | paid |
get_api_detail | Full spec for a marketplace API: pricing, method, exact request | paid |
discover_agents | Find other agents registered on the gateway | paid |
aip_resolve | Rank providers for an intent, priced, before you spend | paid |
aip_execute_with_budget | Run a task end to end under a spending cap you set | paid |
Free tools answer without credentials, so you can list the catalogue before deciding to pay for anything. Protocol methods (initialize, tools/list, resources/list) are free too.
| Method | Header | When |
|---|---|---|
| x402 USDC | PAYMENT-SIGNATURE | No account. Wallet settles on Base or Solana. |
| API key | Authorization: Bearer sk-… | Pre-paid account. |
A paid tool called without either does not fail — it answers with an x402 quote:
tools/call → 402 with payment terms (amount, asset, payTo, network)
→ this proxy signs a USDC authorization locally → retry with PAYMENT-SIGNATURE → result
With JARVISCLAW_WALLET_KEY set, all three steps happen inside this process and your client just sees the result. Without it, the quote is passed through to your client unanswered.
Both chains are live, which most x402 sellers cannot say: settle wherever the agent already holds USDC rather than bridging to reach one gateway. Every paid response carries an EIP-712 signed settlement receipt that a third party can verify offline — recompute the hashes, recover the signer, check the tx on-chain — without trusting us.
npm audit reports 3 moderate advisories reachable through @solana/web3.js (itself, plus jayson and uuid). 1.98.4 is the latest release and is inside the flagged range, so there is no version to move to; npm's suggested "fix" is a downgrade to 0.0.3, which is not a real option. Tracked, not resolved.
This applies to Base-only users too: @solana/web3.js is a static import in the entry module, so it loads whatever JARVISCLAW_CHAIN is set to (measured: 6 module resolutions on the Base path). Only the signer *object* is constructed lazily.
npm install
npm run build # tsc → dist/ npm test # bun test — x402 signer unit tests
MIT