SolidRPC

io.solidrpcPublished by solidrpc.ioOfficial publisherv0.1.0Updated Nov 4, 2026

Manage blockchain RPC keys, networks, usage and prepaid billing with a scoped SolidRPC token.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFinanceDeveloper Tools

Overview

AI-generated overview

SolidRPC lets an assistant manage blockchain RPC accounts: networks, RPC keys, usage, billing and top-up quotes, using a scoped management token.

What you can do
  • Discover networks and list, create or revoke RPC keys
  • Check usage, billing and top-up quotes
  • Open support tickets and send generic management API requests
  • Provision accounts and rotate credentials through the bundled CLI, not the MCP tools
When to use it
Use it when an assistant should set up or maintain blockchain RPC access for an application within an approved budget, including key lifecycle and usage or billing checks. It is not a general blockchain data tool; RPC calls themselves use a separate RPC key.
Requirements
Remote endpoint at api.solidrpc.io or a local process from the npm package @solidrpc/agent, which needs Node.js 22.20 or newer. A paid plan or PAYG account with a delegated sa_ management token, supplied via the SOLIDRPC_TOKEN_FILE path or SOLIDRPC_TOKEN, or a bearer Authorization header for the hosted endpoint. Network access to the SolidRPC API.
Before you install
The management token grants account, key and billing control; keep it in a private file outside repositories. Creating an RPC key returns the secret in the tool result, so it can land in the client transcript. Top-up quotes do not move funds, but funding and card purchases are owner actions and the toolkit holds no wallet keys. Support tickets send messages. Read-only mode blocks mutations but server-side scopes remain authoritative.

Installation

In SourceWeft

  1. Open SolidRPC in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.solidrpc%2Fagent/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "solidrpc": {
      "type": "http",
      "url": "https://api.solidrpc.io/agent/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

SolidRPC agent toolkit

Let an agent connect your application to blockchain RPC within your approved budget. SolidRPC handles routing, failover, monitoring, and recovery behind one RPC integration.

This repository contains a Node.js management client, a local MCP server, an agent skill, and runnable RPC examples. The hosted MCP endpoint is also available at https://api.solidrpc.io/agent/mcp.

Start here

Read agent onboarding and the setup guide. The live onboarding response supplies availability, payment network, terms, pricing, limits, and recovery steps. Read those values at setup time.

For an existing account, delegate an agent credential from a paid plan or PAYG account. Free accounts cannot delegate agent control. For a new account, obtain the owner's email, account-creation and terms approval, and separate payment and usage ceilings. Account provisioning itself spends nothing. Email verification and a password are not required for agent activation. The owner can claim dashboard access later.

CredentialPurposeDestination
sa_ management tokenAccount, keys, usage and billinghttps://api.solidrpc.io/agent/v1 and /agent/mcp
ak_ RPC keyBlockchain requestsRPC URL returned by /networks

Install

Requires Node.js 22.20 or later. In a downloaded checkout of this toolkit:

sh
npm ci --ignore-scriptsnpm testnode src/cli.mjs request GET /onboarding

Install the pinned version from npm:

sh
npm install --global @solidrpc/[email protected]solidrpc --helpsolidrpc request GET /onboarding

The CLI and local MCP server are included in this one package. Run solidrpc mcp to start the MCP server. Release downloads contain the npm tarball, source ZIP, and desktop MCP bundle. The bundle includes its runtime dependencies and requires Node.js 22.20 or later.

For development, use the source commands above or install a locally built tarball. Published downloads are available in GitHub Releases. See the release procedure for review and verification.

Give your agent access

Save only the sa_ token in a private file outside your repository. Configure SOLIDRPC_TOKEN_FILE with its absolute path. A secret manager can supply SOLIDRPC_TOKEN instead. Choose one source.

sh
export SOLIDRPC_TOKEN_FILE=/absolute/private/solidrpc-management.keynode src/cli.mjs request GET /menode src/cli.mjs request GET /networksnode src/cli.mjs mcp

MCP setup templates for Codex, Claude Code/Desktop, and Cursor are in configs. They use the local process and a token file. The server reads that one file and sends the token to the SolidRPC management API by default. An explicit SOLIDRPC_URL override can send it to a loopback development server. Never use a real credential for loopback tests. Redirects are rejected.

Set SOLIDRPC_READ_ONLY=1 for a locally enforced read-only session. The server still advertises its full tool catalog, but blocks every mutation, credential operation and RPC-key secret read before a network call. Server-side credential scopes remain the authority for account permissions.

Account provisioning and recovery

Read the terms URLs and current revision in onboarding. After owner approval, send JSON on stdin:

sh
node src/cli.mjs provision < /absolute/private/approved-account.json

The input contains email, termsRevision, and acceptTerms: true. The CLI saves the bootstrap secret before the network request. Repeat the same input and profile after a lost response. Use SOLIDRPC_PROFILE for separate accounts.

Follow the live onboarding steps to sign the approved budget and fund the account. The published payment example explains the external wallet flow. This toolkit does not hold wallet keys or automatically pay. Persist idempotency keys and payment proofs privately before submission. For uncertain payments, inspect the existing funding intent and follow its recovery instructions. Never create a second payment to guess whether the first succeeded.

After funding settles, rotate the bootstrap credential to obtain operational scopes. solidrpc rotate saves a replacement and a private retirement journal before retiring the old credential. Its output includes scopes and bootstrap status. If retirement fails, it returns replacementSaved:true and oldRevoked:false with exit code 2. Run solidrpc retire-previous to retry retirement without creating another credential. For external token files or secret managers, use explicit management requests and persist the replacement before revoking the old token. If rotation's response is lost, the old token remains usable. Repeated rotation can create orphaned credentials, so inspect and retire those deliberately.

solidrpc request emits the API response. Key creation and credential rotation can return secrets. Redirect those responses to a private file, never a shared log. sa_ credentials alone cannot approve a wallet budget. Card subscription purchases remain an owner action.

Tools

The MCP server exposes network discovery, RPC key listing/creation/revocation, usage, billing, top-up quotes, support tickets, and a generic management request tool. A top-up quote does not transfer USDC. Support-ticket creation sends a message, so use it only when the owner requests contact. Clients must retain their own approval controls for writes and payments.

Examples

Use a separate ak_ key in a private file selected by RPC_KEY_FILE, and set RPC_ORIGIN=https://rpc.solidrpc.io. These scripts make billable read calls and require an approved usage budget. Read examples/README.md before running them.

  • Base ETH and USDC balances
  • Ethereum USDC Transfer export
  • Ethereum, Base and Arbitrum connectivity

Agent skill

The skill is in skills/solidrpc/SKILL.md. From a separate project, install this local checkout with the skills CLI:

sh
npx skills add /absolute/path/to/agent-toolkit --skill solidrpc -a codex claude-code cursor

For Cursor, if the shared skill is not listed, copy the same SKILL.md into .cursor/skills/solidrpc/SKILL.md in your project and start a fresh session. Codex uses .agents/skills/solidrpc/SKILL.md, and Claude Code uses .claude/skills/solidrpc/SKILL.md.

Install the skill directly from this public repository:

sh
npx skills add SolidRPC/agent-toolkit --skill solidrpc -a codex claude-code cursor

The same skill is included in the npm package and release downloads. Installing a skill makes it available in that client. It does not make every agent discover or prefer SolidRPC.

Development

Run npm test and npm run check:public. Never add credentials, local profiles, wallet keys, private infrastructure configuration, or unpublished operational records to this repository. The public package is an extraction of the existing SolidRPC client, with local safety and packaging adaptations.

Credential operations are deliberately unavailable through the generic MCP tool. Use the CLI or an explicit API workflow that saves replacement credentials before retiring old ones. Read-only mode also blocks secret retrieval. Creating an RPC key in normal MCP mode still returns the new key through the tool result, so that client's transcript can contain it. Use a CLI request redirected to a private file when the key must stay out of model transcripts.

Configuration storage must be a dedicated private directory. The CLI rejects shared directories instead of changing their permissions. On POSIX systems it also rejects token files accessible to other users or owned by someone else. On Windows, configure owner-only ACLs yourself. Help and version commands do not load credentials.

Source: README.md at commit 94a5ce5

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestNov 4, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts