Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
320 AI models + 2,720 pay-per-call APIs. x402 USDC on Base or Solana, no API key.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.jarvisclaw.ai/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"jarvisclaw": {
"command": "npx",
"args": [
"-y",
"jarvisclaw-mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http jarvisclaw https://api.jarvisclaw.ai/mcpclaude mcp add jarvisclaw -- npx -y jarvisclaw-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"jarvisclaw": {
"url": "https://api.jarvisclaw.ai/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"jarvisclaw": {
"command": "npx",
"args": [
"-y",
"jarvisclaw-mcp"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"jarvisclaw": {
"type": "http",
"url": "https://api.jarvisclaw.ai/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"jarvisclaw": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jarvisclaw-mcp"
]
}
}
}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.
ChatGPT connects only to servers on the internet:
https://api.jarvisclaw.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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
The registry name was verified with the GitHub account api-jarvisclaw, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 3 months ago.
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.
In the same category: Context7, Codebase Memory, Exa
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
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
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.
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.
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