Agent skill

Blockrun Upgrade

by BlockRunAI in BlockRunAI/blockrun-mcp

A skill your agent uses when the BlockRun MCP server prints 'Update available', when asked to upgrade, update, or pin @blockrun/mcp, when a fix 'should be in the new version' but the client still…

MITAuto-check passedAgent Workflows

Install Blockrun Upgrade

skills CLI
$ npx skills add BlockRunAI/blockrun-mcp --skill blockrun-upgrade -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install BlockRunAI/blockrun-mcp blockrun-upgrade --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/BlockRunAI/blockrun-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/blockrun-upgrade .claude/skills/blockrun-upgrade && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
blockrun-upgrade
GitHub stars
392
Token cost
~1.6k tokens
SKILL.md length
649 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the BlockRun MCP server prints 'Update available', when asked to upgrade, update, or pin @blockrun/mcp, when a fix 'should be in the new version' but the client still…

  • Works in 5 steps: Read how it was installed → Upgrade → Prove the version → …
  • The BlockRun MCP server prints Update available
  • SKILL.md covers 1. Read how it was installed, 2. Upgrade, 3. Prove the version and 4. What can break, plus 3 more sections
  • Calls claude, npx and npm; needs BLOCKRUN_WALLET_KEY

What it does

Blockrun Upgrade is an agent skill from BlockRunAI/blockrun-mcp. Use when the BlockRun MCP server prints 'Update available', when asked to upgrade, update, or pin @blockrun/mcp, when a fix 'should be in the new version' but the client still runs the old one, when refreshing skills that were copied into a project, or when rolling back to a previous version.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Live data for AI agents — search, research, markets, crypto, X/Twitter. Pay-per-call via x402 micropayments. The licence is MIT.

When your agent uses it

  • The BlockRun MCP server prints Update available
  • Asked to upgrade
  • Pin @blockrun/mcp
  • A fix should be in the new version but the client still runs the old one

Example prompts

  • “Update available”
  • “should be in the new version”
  • “/blockrun-upgrade”

Requirements

  • Node.js
  • A credential in BLOCKRUN_WALLET_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Read how it was installed
  2. Upgrade
  3. Prove the version
  4. What can break
  5. Refresh copied skills

What it can do on your machine

Read from SKILL.md and the folder at commit e9b2bd5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • claude
    • npx
    • npm
    • codex

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • npmjs.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • BLOCKRUN_WALLET_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Blockrun Upgrade loads about 1.6k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 649 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from BlockRunAI/blockrun-mcp at commit e9b2bd5, republished under its MIT licence (© BlockRunAI). 649 words, ~1,602 tokens.

Download SKILL.mdSave it as .claude/skills/blockrun-upgrade/SKILL.md (or your agent's skills folder).
name
blockrun-upgrade
description
Use when the BlockRun MCP server prints 'Update available', when asked to upgrade, update, or pin @blockrun/mcp, when a fix 'should be in the new version' but the client still runs the old one, when refreshing skills that were copied into a project, or when rolling back to a previous version.
triggers
update available blockrun, upgrade blockrun, update blockrun mcp, blockrun new version, still on old version, pin blockrun version, rollback blockrun, update…

Upgrading BlockRun MCP

The server is run by npx, so "upgrading" means making npx fetch a newer version and the client restart into it. Which of those two is the problem depends on how it was installed.

1. Read how it was installed

bash
claude mcp get blockrun          # registered command + args + env + scope
npm view @blockrun/mcp version   # what "latest" is on the registry right now
Registered specWhat happens at each client start
npx -y @blockrun/mcp@latestnpx re-resolves latest against the registry and downloads if newer. A client restart is the upgrade.
npx -y @blockrun/mcp (no tag)npx reuses whatever is in ~/.npm/_npx — the version from the day it was installed. Restarting changes nothing.
npx -y @blockrun/mcp@0.39.2Pinned on purpose. Only changes if you re-register.

The startup notice is the server telling you it is not on latest:

[BlockRun] Update available: v0.39.2 → v0.42.0
[BlockRun] Run: claude mcp add blockrun -s user -- npx -y @blockrun/mcp@latest

2. Upgrade

Registered with @latest: restart the client. Done. If the notice persists, the cache is stale or the registry was unreachable at start:

bash
rm -rf ~/.npm/_npx          # safe — it is only a download cache

then restart again.

Registered without a tag, or pinned: re-register with @latest. claude mcp add refuses a name that already exists, so remove first — at the scope claude mcp get reported — and carry every env var and flag it printed across, one -e each, flags after the package:

bash
claude mcp remove blockrun -s user
claude mcp add blockrun -s user \
  -e PATH="$PATH" -e BLOCKRUN_KEYCHAIN=auto -e BLOCKRUN_CONFIRM_SPEND=on \
  -- npx -y @blockrun/mcp@latest --profile trading

Codex: codex mcp remove blockrun then codex mcp add blockrun -- npx -y @blockrun/mcp@latest. JSON clients (Claude Desktop / Cursor / Windsurf): edit args to ["-y", "@blockrun/mcp@latest"].

Then quit and relaunch the client (Claude Code: /mcp reconnect blockrun respawns just this server). A running session keeps the old process until you do.

3. Prove the version

bash
npx -y @blockrun/mcp@latest --version     # what npx would launch now, e.g. 0.42.0

That proves what npx would launch. What the client is running is the server's startup line on stderr — BlockRun MCP Server started (v0.42.0) — stdio transport — 20 tools (Claude Code: claude --debug or the MCP log; /mcp shows connection status, not the version). If the two disagree, the client was not restarted; the stderr line wins. No Update available line after it = you are current.

Show full SKILL.md (344 more words)Show less

4. What can break

Read the CHANGELOG for the versions you are crossing: https://github.com/BlockRunAI/blockrun-mcp/blob/main/CHANGELOG.md. Each entry explains the behaviour change, not just the diff. Things that have changed across versions and are worth checking:

  • Tool set / profiles — --profile names and tool membership; a trimmed profile may gain or lose a tool.
  • Env-var semantics — the kind of change to look for: BLOCKRUN_KEYCHAIN arrived in 0.41; BLOCKRUN_CONFIRM_SPEND widened from one tool to all paid tools in 0.43. Read the entries for the versions you cross and re-check claude mcp get blockrun env against the README Configuration table.
  • Wallet file precedence — BLOCKRUN_WALLET_KEY → agent wallet.json → ~/.blockrun/.session. An upgrade never moves or rewrites the key; if a balance "disappears", the signer changed, not the funds. blockrun_wallet prints the address.
  • Polymarket approvals — new adapter grants are added over time. After an upgrade, blockrun_polymarket action:"setup" confirm:true once before trading: idempotent and gasless, but it signs on-chain approvals, so say so to the user before running it.

Your USDC and keys are in ~/.blockrun/, not in the package. Upgrading cannot lose them.

5. Refresh copied skills

Skills copied into a project or user directory do not update with the package. Marketplace-installed skills (/plugin marketplace add BlockRunAI/blockrun-mcp) refresh with /plugin marketplace update blockrun-mcp followed by /reload-plugins (or uninstall + /plugin install <skill>@blockrun-mcp). For copied ones, re-run the install with --force — it overwrites the files the package ships and leaves any other files in those directories alone:

bash
ls .claude/skills ~/.claude/skills 2>/dev/null                 # where were they copied?
npx -y @blockrun/mcp@latest skills list                       # what this version ships
npx -y @blockrun/mcp@latest skills install --force            # ./.claude/skills
npx -y @blockrun/mcp@latest skills install --global --force   # ~/.claude/skills

--force replaces the shipped files. If the user edited their copies, diff before overwriting: skills install --to /tmp/br-skills and diff -r /tmp/br-skills .claude/skills.

Rollback

Pin the previous version and restart:

bash
claude mcp remove blockrun -s user
claude mcp add blockrun -s user -e PATH="$PATH" -- npx -y @blockrun/mcp@0.41.1

Versions: https://www.npmjs.com/package/@blockrun/mcp?activeTab=versions. Report what broke at https://github.com/BlockRunAI/blockrun-mcp/issues with the two version numbers.

Common mistakes

MistakeReality
npm install -g @blockrun/mcp to upgradeThe client runs npx, which ignores the global install. Re-register instead.
Editing ~/.npm/_npx/**/package.jsonIt is a cache. Delete it, don't edit it.
Restarting only the terminalThe MCP process belongs to the client session. Restart the client (or /mcp reconnect in Claude Code).
Assuming the skills upgraded tooThey are files you copied. skills install --force.

© BlockRunAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/blockrun-upgrade of BlockRunAI/blockrun-mcp.

Open the folder on GitHubat commit e9b2bd5

Compare with similar skills

Blockrun Upgrade next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Blockrun Upgrade compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Blockrun Upgrade this skillBlockRunAI/blockrun-mcp392—~1.6kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Fastmcp Client CLIPrefectHQ/fastmcp28k1 repos~823Automated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Fastmcp Client CLI

    PrefectHQ/fastmcp

    Query and invoke tools on MCP servers using fastmcp list and fastmcp call.

    28k GitHub starsUsed in 1 repo~823 tokens
    Agent WorkflowsAuto-check passed
  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from BlockRunAI/blockrun-mcp

All 17 skills in this repo
  • Signal To Trade Demo

    BlockRunAI/blockrun-mcp

    Prepare or run a polished BlockRun trading demo that discovers a current Polymarket market, combines live price, probability history, smart-money, and liquidity evidence into a balanced signal…

    392 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Blockrun

    BlockRunAI/blockrun-mcp

    Pay-per-call access to AI models, real-time data, media generation and multi-chain RPC over x402 micropayments (USDC on Base or Solana), or a BlockRun account API key.

    392 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Blockrun Debug

    BlockRunAI/blockrun-mcp

    A skill your agent uses when the BlockRun MCP server (@blockrun/mcp) is installed but misbehaving — 'Failed to connect', spawn npx ENOENT, blockrun missing from claude mcp list, HTTP 402 /…

    392 GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Blockrun Setup

    BlockRunAI/blockrun-mcp

    A skill your agent uses when asked to install, add, configure, or set up the BlockRun MCP server (@blockrun/mcp) in Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, Grok or another MCP…

    392 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Crypto Data

    BlockRunAI/blockrun-mcp

    A skill your agent uses for any crypto data question — token/coin prices, FX, commodities, stocks, OHLC history, DEX pairs and liquidity, DeFi TVL, yield/APY pools, or raw JSON-RPC against a chain…

    392 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Decide

    BlockRunAI/blockrun-mcp

    A skill your agent uses when the user wants to try BlockRun's free typed-judgment endpoint (POST api.blockrun.ai/v1/decide, served by OpenJev) on their own data from Claude Code — yes/no, labelled…

    392 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Blockrun Upgrade

What does Blockrun Upgrade do?

A skill your agent uses when the BlockRun MCP server prints 'Update available', when asked to upgrade, update, or pin @blockrun/mcp, when a fix 'should be in the new version' but the client still…. Blockrun Upgrade is an agent skill from BlockRunAI/blockrun-mcp. Use when the BlockRun MCP server prints 'Update available', when asked to upgrade, update, or pin @blockrun/mcp, when a fix 'should be in the new version' but the client still runs the old one, when refreshing skills that were copied into a project, or when rolling back to a previous version.

When should I use Blockrun Upgrade?

Blockrun Upgrade fits situations like: the BlockRun MCP server prints Update available; asked to upgrade; pin @blockrun/mcp; A fix should be in the new version but the client still runs the old one.

How do I install Blockrun Upgrade in Claude Code?

Run `npx skills add BlockRunAI/blockrun-mcp --skill blockrun-upgrade -a claude-code`. Or copy the skill folder (skills/blockrun-upgrade in BlockRunAI/blockrun-mcp) into .claude/skills/blockrun-upgrade in your project. Claude Code loads it when a task matches its description.

How do I install Blockrun Upgrade in Codex?

Run `npx skills add BlockRunAI/blockrun-mcp --skill blockrun-upgrade -a codex`. Or copy the skill folder (skills/blockrun-upgrade in BlockRunAI/blockrun-mcp) into .agents/skills/blockrun-upgrade in your project. Codex loads it when a task matches its description.

Can I use Blockrun Upgrade in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BlockRunAI/blockrun-mcp --skill blockrun-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blockrun-upgrade, .gemini/skills/blockrun-upgrade, .github/skills/blockrun-upgrade and .opencode/skills/blockrun-upgrade in your project.

What does Blockrun Upgrade need to run?

Going by SKILL.md and its folder, Blockrun Upgrade needs the command-line tools its instructions call (claude, npx, npm and codex) and credentials named BLOCKRUN_WALLET_KEY. Our summary lists: Node.js; A credential in BLOCKRUN_WALLET_KEY.

Does Blockrun Upgrade access the network?

SKILL.md names 1 domain. As links in the text: npmjs.com. This is read from the text; nothing was executed.

Is Blockrun Upgrade safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Blockrun Upgrade use?

Blockrun Upgrade is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Blockrun Upgrade use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Blockrun Upgrade?

Skills that share tags, products or a category with Blockrun Upgrade: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Blockrun Upgrade?

BlockRunAI (a GitHub organization) maintains it in BlockRunAI/blockrun-mcp, which has 392 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.

Source: BlockRunAI/blockrun-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.