@one-source/mcp 5.0.2 → 5.0.4

package/README.md

@@ -101,14 +101,19 @@ All blockchain API tools accept an optional `network` parameter:
 
 ## Authentication
 
-Blockchain API tools require authentication. Two options are available — API key takes priority if both are set.
+Blockchain API tools require authentication. Two options are available — if both are set, API key takes priority.
 
 | Method | Variable | Description |
 |--------|----------|-------------|
 | API key | `ONESOURCE_API_KEY` | Unlimited calls, no per-call cost |
-| x402 micropayments | `X402_PRIVATE_KEY` | Pay-per-call via USDC on Base |
+| x402 micropayments | `X402_PRIVATE_KEY` | Pay-per-call via USDC on Base, no account required |
 
-### Option 1: API Key (recommended)
+### Option 1: API Key
+
+1. Go to [app.onesource.io](https://app.onesource.io) and create an account.
+2. Subscribe to a developer plan (Stripe checkout).
+3. Navigate to **API Keys** and generate a key.
+4. Copy the key — it starts with `sk_`.
 
 #### Claude Code
 
@@ -138,16 +143,19 @@ claude mcp add onesource -e ONESOURCE_API_KEY=<key> -- npx -y @one-source/mcp@la
 ONESOURCE_API_KEY=<key> npx -y @one-source/mcp@latest
 ```
 
+After adding, reload the MCP server and call `1s_setup_check` — it should show `Status: Configured (API key)`.
+
 ### Option 2: x402 Micropayments
 
-1. **Get an EVM private key** — export from MetaMask, Coinbase Wallet, or generate one. The key is a 64-character hex string. The `0x` prefix is optional — both formats are accepted.
-2. **Fund the wallet with USDC on Base** — bridge or transfer USDC to the derived wallet address on [Base](https://base.org).
-3. **Pass the key to the server:**
+Pay-per-call via USDC on Base using [x402](https://github.com/coinbase/x402). No account required — just an EVM wallet funded with USDC. The server handles payments transparently.
+
+1. **Get an EVM private key** — export from MetaMask, Coinbase Wallet, or generate a fresh one. The key is a 64-character hex string. The `0x` prefix is optional — both formats are accepted.
+2. **Pass the key to the server:**
 
 #### Claude Code
 
 ```bash
-claude mcp add onesource -e X402_PRIVATE_KEY=0x... -- npx -y @one-source/mcp@latest
+claude mcp add onesource -e X402_PRIVATE_KEY=<key> -- npx -y @one-source/mcp@latest
 ```
 
 #### Claude Desktop / Cursor
@@ -159,7 +167,7 @@ claude mcp add onesource -e X402_PRIVATE_KEY=0x... -- npx -y @one-source/mcp@lat
       "command": "npx",
       "args": ["-y", "@one-source/mcp@latest"],
       "env": {
-        "X402_PRIVATE_KEY": "0x..."
+        "X402_PRIVATE_KEY": "<key>"
       }
     }
   }
@@ -169,9 +177,13 @@ claude mcp add onesource -e X402_PRIVATE_KEY=0x... -- npx -y @one-source/mcp@lat
 #### Any MCP Client (stdio)
 
 ```bash
-X402_PRIVATE_KEY=0x... npx -y @one-source/mcp@latest
+X402_PRIVATE_KEY=<key> npx -y @one-source/mcp@latest
 ```
 
+3. **Reload and find your wallet address** — reload the MCP server, then call `1s_setup_check`. It will show the wallet address derived from your key under "Wallet address".
+4. **Fund that address with USDC on Base** — send USDC to the address shown, on the [Base](https://base.org) network. A few dollars ($1–5 USDC) is enough for hundreds of calls. Bridge from Ethereum mainnet if needed using the [Base Bridge](https://bridge.base.org).
+5. **Verify** — call `1s_network_info` for ethereum. If it returns chain data, payments are working.
+
 ### Security
 
 Never commit keys to source control. Use environment variables, a `.env` file (excluded from git), or a secrets manager.

package/README.npm.md

@@ -101,14 +101,19 @@ All blockchain API tools accept an optional `network` parameter:
 
 ## Authentication
 
-Blockchain API tools require authentication. Two options are available — API key takes priority if both are set.
+Blockchain API tools require authentication. Two options are available — if both are set, API key takes priority.
 
 | Method | Variable | Description |
 |--------|----------|-------------|
 | API key | `ONESOURCE_API_KEY` | Unlimited calls, no per-call cost |
-| x402 micropayments | `X402_PRIVATE_KEY` | Pay-per-call via USDC on Base |
+| x402 micropayments | `X402_PRIVATE_KEY` | Pay-per-call via USDC on Base, no account required |
 
-### Option 1: API Key (recommended)
+### Option 1: API Key
+
+1. Go to [app.onesource.io](https://app.onesource.io) and create an account.
+2. Subscribe to a developer plan (Stripe checkout).
+3. Navigate to **API Keys** and generate a key.
+4. Copy the key — it starts with `sk_`.
 
 #### Claude Code
 
@@ -138,16 +143,19 @@ claude mcp add onesource -e ONESOURCE_API_KEY=<key> -- npx -y @one-source/mcp@la
 ONESOURCE_API_KEY=<key> npx -y @one-source/mcp@latest
 ```
 
+After adding, reload the MCP server and call `1s_setup_check` — it should show `Status: Configured (API key)`.
+
 ### Option 2: x402 Micropayments
 
-1. **Get an EVM private key** — export from MetaMask, Coinbase Wallet, or generate one. The key is a 64-character hex string. The `0x` prefix is optional — both formats are accepted.
-2. **Fund the wallet with USDC on Base** — bridge or transfer USDC to the derived wallet address on [Base](https://base.org).
-3. **Pass the key to the server:**
+Pay-per-call via USDC on Base using [x402](https://github.com/coinbase/x402). No account required — just an EVM wallet funded with USDC. The server handles payments transparently.
+
+1. **Get an EVM private key** — export from MetaMask, Coinbase Wallet, or generate a fresh one. The key is a 64-character hex string. The `0x` prefix is optional — both formats are accepted.
+2. **Pass the key to the server:**
 
 #### Claude Code
 
 ```bash
-claude mcp add onesource -e X402_PRIVATE_KEY=0x... -- npx -y @one-source/mcp@latest
+claude mcp add onesource -e X402_PRIVATE_KEY=<key> -- npx -y @one-source/mcp@latest
 ```
 
 #### Claude Desktop / Cursor
@@ -159,7 +167,7 @@ claude mcp add onesource -e X402_PRIVATE_KEY=0x... -- npx -y @one-source/mcp@lat
       "command": "npx",
       "args": ["-y", "@one-source/mcp@latest"],
       "env": {
-        "X402_PRIVATE_KEY": "0x..."
+        "X402_PRIVATE_KEY": "<key>"
       }
     }
   }
@@ -169,9 +177,13 @@ claude mcp add onesource -e X402_PRIVATE_KEY=0x... -- npx -y @one-source/mcp@lat
 #### Any MCP Client (stdio)
 
 ```bash
-X402_PRIVATE_KEY=0x... npx -y @one-source/mcp@latest
+X402_PRIVATE_KEY=<key> npx -y @one-source/mcp@latest
 ```
 
+3. **Reload and find your wallet address** — reload the MCP server, then call `1s_setup_check`. It will show the wallet address derived from your key under "Wallet address".
+4. **Fund that address with USDC on Base** — send USDC to the address shown, on the [Base](https://base.org) network. A few dollars ($1–5 USDC) is enough for hundreds of calls. Bridge from Ethereum mainnet if needed using the [Base Bridge](https://bridge.base.org).
+5. **Verify** — call `1s_network_info` for ethereum. If it returns chain data, payments are working.
+
 ### Security
 
 Never commit keys to source control. Use environment variables, a `.env` file (excluded from git), or a secrets manager.

package/README.repo.md

@@ -101,16 +101,19 @@ All blockchain API tools accept an optional `network` parameter:
 
 ## Authentication
 
-Blockchain API tools require authentication. Two options are available — API key takes priority if both are set.
+Blockchain API tools require authentication. Two options are available — if both are set, API key takes priority.
 
 | Method | Variable | Description |
 |--------|----------|-------------|
 | API key | `ONESOURCE_API_KEY` | Unlimited calls, no per-call cost |
-| x402 micropayments | `X402_PRIVATE_KEY` | Pay-per-call via USDC on Base |
+| x402 micropayments | `X402_PRIVATE_KEY` | Pay-per-call via USDC on Base, no account required |
 
-### Option 1: API Key (recommended)
+### Option 1: API Key
 
-Set `ONESOURCE_API_KEY` with your OneSource API key.
+1. Go to [app.onesource.io](https://app.onesource.io) and create an account.
+2. Subscribe to a developer plan (Stripe checkout).
+3. Navigate to **API Keys** and generate a key.
+4. Copy the key — it starts with `sk_`.
 
 #### Claude Code
 
@@ -142,18 +145,22 @@ Add the `env` block to your MCP config:
 ONESOURCE_API_KEY=<key> npx -y @one-source/mcp@latest
 ```
 
+After adding, reload the MCP server and call `1s_setup_check` — it should show `Status: Configured (API key)`.
+
 ### Option 2: x402 Micropayments
 
-Blockchain API endpoints are priced in USDC on Base via [x402](https://github.com/coinbase/x402). When you set `X402_PRIVATE_KEY`, the server automatically handles payments — tool calls that return HTTP 402 are paid and retried without any extra work from the agent.
+Blockchain API endpoints are priced in USDC on Base via [x402](https://github.com/coinbase/x402). When you set `X402_PRIVATE_KEY`, the server automatically handles payments — tool calls are paid and retried transparently without any extra work from the agent.
 
-1. **Get an EVM private key** — export one from MetaMask, Coinbase Wallet, or any EVM wallet. The key is a 64-character hex string. The `0x` prefix is optional — both formats are accepted.
-2. **Fund the wallet with USDC on Base** — the wallet address derived from the key must hold USDC on the [Base](https://base.org) network. Bridge or transfer USDC to it.
-3. **Pass the key to the server** using one of the methods below.
+1. **Get an EVM private key** — export one from MetaMask, Coinbase Wallet, or any EVM wallet, or generate a fresh one. The key is a 64-character hex string. The `0x` prefix is optional — both formats are accepted.
+2. **Pass the key to the server** using one of the methods below.
+3. **Reload and find your wallet address** — reload the MCP server, then call `1s_setup_check`. It will show the wallet address derived from your key under "Wallet address".
+4. **Fund that address with USDC on Base** — send USDC to the address shown in `1s_setup_check`, on the [Base](https://base.org) network. A few dollars ($1–5 USDC) is enough for hundreds of calls. If your USDC is on Ethereum mainnet, bridge it using the [Base Bridge](https://bridge.base.org).
+5. **Verify** — call `1s_network_info` for ethereum. If it returns chain data (block number, gas price), x402 payments are working end-to-end.
 
 #### Claude Code
 
 ```bash
-claude mcp add onesource -e X402_PRIVATE_KEY=0x... -- npx -y @one-source/mcp@latest
+claude mcp add onesource -e X402_PRIVATE_KEY=<key> -- npx -y @one-source/mcp@latest
 ```
 
 #### Claude Desktop / Cursor
@@ -167,7 +174,7 @@ Add the `env` block to your MCP config:
       "command": "npx",
       "args": ["-y", "@one-source/mcp@latest"],
       "env": {
-        "X402_PRIVATE_KEY": "0x..."
+        "X402_PRIVATE_KEY": "<key>"
       }
     }
   }
@@ -177,7 +184,7 @@ Add the `env` block to your MCP config:
 #### Any MCP Client (stdio)
 
 ```bash
-X402_PRIVATE_KEY=0x... npx -y @one-source/mcp@latest
+X402_PRIVATE_KEY=<key> npx -y @one-source/mcp@latest
 ```
 
 ### Config File Locations

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@one-source/mcp",
   "mcpName": "io.onesource/mcp",
-  "version": "5.0.2",
+  "version": "5.0.4",
   "type": "module",
   "description": "Unified MCP server for OneSource — 24 tools for blockchain data",
   "bin": {

package/skills/onesource-mcp-setup/SKILL.md

@@ -1,23 +1,23 @@
 ---
 name: onesource-mcp-setup
 description: >-
-  Guide for installing and configuring the OneSource MCP server with x402
-  payments. Covers installation, version checking, wallet setup, USDC
+  Guide for installing and configuring the OneSource MCP server. Covers both
+  authentication options (API key and x402 micropayments), wallet setup, USDC
   funding on Base, and verification. Use when a user needs help setting up
-  OneSource MCP or configuring x402 payments.
+  OneSource MCP or configuring either auth method.
 ---
 
 # OneSource MCP Setup Guide
 
-OneSource MCP provides 24 tools for blockchain data and live chain queries. Blockchain API tools require authentication — either an API key (`ONESOURCE_API_KEY`) or x402 micropayments in USDC on the Base network (`X402_PRIVATE_KEY`).
+OneSource MCP provides 24 tools for blockchain data and live chain queries. Blockchain API tools require authentication — either an API key (`ONESOURCE_API_KEY`) or x402 micropayments in USDC on the Base network (`X402_PRIVATE_KEY`). If both are set, API key takes priority.
 
 ## Before You Start
 
-**Always call `1s_setup_check` before using any other OneSource tools.** This checks the installed version against the latest release and reports x402 payment status.
+**Always call `1s_setup_check` before using any other OneSource tools.** This checks the installed version against the latest release and reports authentication status.
 
 - **If an update is available:** Tell the user and help them update before proceeding. Run `npx -y @one-source/mcp@latest` to get the latest version. The update takes effect on the next session — the user will need to restart their MCP client.
 - **If `1s_setup_check` is not available:** The MCP is either not installed or running a version before this tool existed. Help the user install or update using the instructions in Step 2 below.
-- **If x402 is not configured:** The tool will include setup instructions. Walk the user through them before attempting paid API calls.
+- **If auth is not configured:** The tool will include setup instructions. Walk the user through them before attempting API calls.
 
 Do not skip this step — outdated versions may be missing tools, fixes, or protocol changes.
 
@@ -25,8 +25,8 @@ Do not skip this step — outdated versions may be missing tools, fixes, or prot
 
 Call the `1s_setup_check` tool. It reports:
 - Server version (current vs latest)
-- Whether x402 payments are configured
-- Wallet address (if configured)
+- Which auth method is active (API key, x402), or whether auth is not yet configured
+- Wallet address (if x402 is configured)
 - API backend connectivity
 
 If the tool is not available, the MCP is not installed — go to Step 2.
@@ -70,7 +70,57 @@ npm view @one-source/mcp version
 
 To update, reinstall with `@latest` or clear the npx cache: `npx -y @one-source/mcp@latest`.
 
-## Step 3: Get an EVM Private Key
+## Step 3: Configure Authentication
+
+Choose one option. If both are set, API key takes priority.
+
+### Option A: API Key
+
+1. Go to [app.onesource.io](https://app.onesource.io) and create an account.
+2. Subscribe to a developer plan (Stripe checkout).
+3. Navigate to **API Keys** and generate a key.
+4. Copy the key — it starts with `sk_`.
+
+#### Claude Code
+
+```bash
+claude mcp remove onesource
+claude mcp add onesource -e ONESOURCE_API_KEY=<key> -- npx -y @one-source/mcp@latest
+```
+
+#### Claude Desktop / Cursor
+
+Add the `env` block to your MCP config:
+
+```json
+{
+  "mcpServers": {
+    "onesource": {
+      "command": "npx",
+      "args": ["-y", "@one-source/mcp@latest"],
+      "env": {
+        "ONESOURCE_API_KEY": "<key>"
+      }
+    }
+  }
+}
+```
+
+#### Any MCP Client (stdio)
+
+```bash
+ONESOURCE_API_KEY=<key> npx -y @one-source/mcp@latest
+```
+
+After adding the key, reload the MCP server (run `/reload-plugins` in Claude Code, or restart Claude Desktop / Cursor), then call `1s_setup_check`. It should show `Status: Configured (API key)`. You're done — skip to Step 7 to verify a live tool call.
+
+---
+
+### Option B: x402 Micropayments
+
+Pay-per-call using USDC on Base. No account required — just an EVM wallet funded with USDC. The server handles payments transparently. Continue with Steps 3B through 6 below.
+
+## Step 3B: Get an EVM Private Key
 
 The `X402_PRIVATE_KEY` is an EVM wallet private key — the same kind used by MetaMask, Coinbase Wallet, or Foundry. It is a 64-character hex string. The `0x` prefix is optional — both formats are accepted.
 
@@ -104,7 +154,7 @@ cast wallet new
 
 **Important:** Use a dedicated wallet for MCP payments — do not use your primary wallet with large holdings. Transfer only what you need.
 
-## Step 4: Set the Private Key
+## Step 4: Set the Private Key (x402)
 
 ### Claude Code
 
@@ -215,27 +265,32 @@ After setting the variable, restart your MCP client and run `1s_setup_check` to
 - Use environment variables, a `.env` file (excluded from git), or a secrets manager.
 - Use a dedicated wallet with minimal funds — only what you need for API calls.
 
-## Step 5: Fund the Wallet with USDC on Base
+## Step 5: Find Your Wallet Address (x402)
+
+After setting the key and reloading the MCP server:
+
+1. Call `1s_setup_check` — it shows the wallet address derived from your key under "Wallet address". This is the address you need to fund.
+2. Alternatively, import the key into MetaMask to see the address.
+
+## Step 6: Fund the Wallet with USDC on Base (x402)
 
 The wallet must hold **USDC on the Base network** (not Ethereum mainnet, not other tokens).
 
-1. Get the wallet address — call `1s_setup_check` (it shows the address after you set the key), or import the key into MetaMask to see it.
-2. Send USDC to that address **on the Base network**.
-3. A few dollars ($1–5 USDC) is enough for hundreds of API calls.
+1. Send USDC to the wallet address from Step 5 **on the Base network**.
+2. A few dollars ($1–5 USDC) is enough for hundreds of API calls.
 
-If you have USDC on Ethereum mainnet, bridge it to Base using the [Base Bridge](https://bridge.base.org) or any cross-chain bridge that supports Base.
+If your USDC is on Ethereum mainnet, bridge it to Base using the [Base Bridge](https://bridge.base.org) or any cross-chain bridge that supports Base.
 
-## Step 6: Verify
+## Step 7: Verify
 
-After setting the key, reload and verify:
+After setting your auth (either option) and reloading:
 
-1. **Reload the MCP server** — In Claude Code, run `/reload-plugins` to pick up config changes without restarting the session.
-2. **Check MCP connection** — Run `/mcp` to confirm the `onesource` server is connected.
-3. **Run `1s_setup_check`** — You should see:
-   - **x402 status:** Configured
-   - **Wallet address:** Your wallet address
+1. **Check MCP connection** — Run `/mcp` to confirm the `onesource` server is connected.
+2. **Run `1s_setup_check`** — You should see:
+   - **Authentication:** `Configured (API key)` or `Configured (x402)` — not "Not configured"
+   - **Wallet address:** Your wallet address (x402 only)
    - **API backend:** Reachable
-4. **Test a paid tool** — Try `1s_network_info` to confirm payments work end-to-end.
+3. **Test a live tool** — Call `1s_network_info` for ethereum. If it returns a block number and gas price, auth is working end-to-end.
 
 > **Tip:** If you edited the config file manually (instead of using `claude mcp add`), you must run `/reload-plugins` for changes to take effect. Restarting Claude Code also works.
 
@@ -244,9 +299,10 @@ After setting the key, reload and verify:
 | Problem | Solution |
 |---------|----------|
 | `1s_setup_check` shows "Not configured" | Most common cause: config was changed but the MCP server wasn't reloaded. Run `/reload-plugins` in Claude Code, or restart Claude Desktop / Cursor. If the key still isn't reaching the server, try setting it as an environment variable directly — see **Alternative: Set the Key as an Environment Variable** above. |
+| `1s_setup_check` shows API key configured but tools return 402 | The key may be invalid or the account may not have a developer plan. Verify the key at app.onesource.io. |
 | "MCP server onesource already exists" error | Run `claude mcp remove onesource` first, then re-add it with your updated config. |
 | Config changed but nothing happened | Run `/reload-plugins` in Claude Code to reload MCP servers, then `/mcp` to check connection status. |
-| Tool returns HTTP 402 error | x402 is not configured, or the wallet has insufficient USDC on Base. |
+| Tool returns HTTP 402 error (x402 path) | x402 is not configured, or the wallet has insufficient USDC on Base. Check `1s_setup_check` for wallet address and balance. |
 | "x402 setup failed" in server logs | The private key format is wrong. It must be a 64-character hex string (with or without `0x` prefix). |
 | Key is set but wallet shows 0 USDC | Make sure USDC is on the **Base** network, not Ethereum mainnet or another chain. |
 | Tools work but results seem stale | Check `1s_setup_check` for version — you may need to update to the latest. |