npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@noelclaw/mcp

v3.44.0

Published

The runtime layer for Agentic AI. 121 MCP tools: persistent memory, autonomous agents, vault storage, scheduled workflows, DeFi on Base (base_mcp_*), Robinhood Chain tokenized stocks and arbitrary crypto with V3/V4 smart routing (rh_*), live market data,

Readme


The runtime layer for Agentic AI.

Your AI remembers, keeps working, and survives every session.


Most AI assistants disappear when the conversation ends. NoelClaw gives them persistent state — memory that accumulates, agents that keep running, vaults that version knowledge, and workflows that continue after you close the chat.

Table of Contents


What's New

| Feature | Description | |---------|-------------| | 🔒 Fully local | Run the whole runtime on your own machine — vault + memory on your own disk (versioned, encrypted, no account), wallet keys local, your LLM does the thinking. Nothing phones home. noelclaw setup to enable, noelclaw vault to inspect. → Run it fully local | | Local Memory | Run memory tools on a free, self-hosted supermemory server on your own machine — zero cost, private, no Noelclaw account needed. noelclaw setup to enable. | | OpenAI BYOK | OpenAI joins Bankr/Anthropic/Grok as a direct LLM provider. OPENAI_BASE_URL also lets you point at any self-hosted OpenAI-compatible gateway (LiteLLM, vLLM, Ollama, OpenRouter, your own VPS). | | noelclaw setup | New guided CLI wizard — pick an LLM provider and/or enable local memory in one flow. | | Noel Shell | Tool calling from chat — spawn agents, save to vault, search memory, estimate + execute swaps, create automations. All from a single prompt. | | execute_swap | Execute token swaps on Base mainnet from Noel Shell. Enforces estimate → preview → confirm → execute flow. Routes via 0x Permit2. | | 7 Agents | Noel (AI OS), CoinGecko (market data), Sage (research), Forge (code), Quill (creative), Spectre (trading), Atlas (general) | | Multi-Provider Chat | Bankr → Anthropic → OpenAI → Grok → Noelclaw proxy fallback | | ConnectMcpModal | Onboarding flow: auto-generate API key + copy install command from webapp | | Security Hardened | 8 security boundaries, wallet decrypt-failure protection, 4 other vulnerability fixes (auth, OTP, private key) | | Knowledge Graph | Vault entries link into a typed graph (references, derived_from, supersedes, related, continues) — auto-built from [[wikilinks]] + #tags, with backlinks. Data layer only for now; visual graph is planned. | | Ecosystem | CI/CD, CodeQL, Dependabot, Husky, Dockerfile, coverage reporting, semantic release, TypeDoc |


Three Pillars

Memory

Semantic, versioned, deduplicated.

Your AI remembers what you told it last week, last month, in a different session — and ranks recent context above stale notes via 90-day half-life decay. Run noelclaw setup to switch to a free, self-hosted local backend instead of the Noelclaw-hosted proxy.

remember: I prefer conservative DeFi strategies, max 5% APY
→ ✓ saved to memory
  auto-loaded in future sessions

Agents

Named, persistent, identity-bound.

Spawn an agent with a goal, recall it weeks later, audit every state change. Each agent can hold its own Base wallet address.

spawn an agent called market-researcher
  goal: track Base chain protocols weekly
→ 🤖 agent spawned
  recall anytime with agent_recall

Workflows

Packets, automations, monitors, deep research.

Anything that runs on a schedule or continues after the chat ends.

set up a daily monitor for
  AI agent infrastructure news
→ ✓ monitor created
  runs daily 08:00 UTC
  findings auto-saved to vault

Install

One-command auto-install (any MCP client)

npx -y -p @noelclaw/[email protected] noelclaw install

Detects Claude Desktop, Cursor, Windsurf, VS Code, and Zed, and configures each automatically. Claude Code is configured with the dedicated claude mcp add command below (its config lives outside the desktop-app path this scan checks).

Claude Code

claude mcp add noelclaw -s user -- npx -y -p @noelclaw/[email protected] noelclaw-mcp

Cursor / Windsurf / Claude Desktop

{
  "mcpServers": {
    "noelclaw": {
      "command": "npx",
      "args": ["-y", "-p", "@noelclaw/[email protected]", "noelclaw-mcp"]
    }
  }
}

VS Code

mcp.json uses the servers key (not mcpServers), and each entry needs "type": "stdio":

{
  "servers": {
    "noelclaw": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "-p", "@noelclaw/[email protected]", "noelclaw-mcp"]
    }
  }
}

Zed

In settings.json under context_servers (each entry needs "source": "custom"):

{
  "context_servers": {
    "noelclaw": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "-p", "@noelclaw/[email protected]", "noelclaw-mcp"]
    }
  }
}

| Client | Path | |--------|------| | Claude Desktop (Mac) | ~/Library/Application Support/Claude/claude_desktop_config.json | | Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json | | Cursor | .cursor/mcp.json | | Windsurf | ~/.codeium/windsurf/mcp_config.json | | Zed | .config/zed/settings.json | | VS Code | .vscode/mcp.json |

No LLM API key required — not to start, and not for any tool. Tools load on first use.

Always pin the version (@noelclaw/[email protected], never @latest) — this MCP has wallet, credential, and backend persistence capabilities. See Security Boundaries.


Run it fully local

NoelClaw is the runtime; your LLM is the brain, and your data stays yours. You can run the whole thing on your own machine — no Noelclaw account, no cloud, nothing leaving your laptop.

Turn it on:

npx -y -p @noelclaw/[email protected] noelclaw setup
# → answer "y" to "Enable local vault" (and, optionally, local memory)

What runs local:

| Piece | Where it lives | Notes | |-------|----------------|-------| | Vault | ~/.noelclaw/vault/ | Versioned artifacts + knowledge graph. Credentials AES-256-GCM encrypted. Plain files — copy, git, or sync them anywhere. | | Memory | self-hosted supermemory | Semantic recall on your machine. Optional; without it, vault search falls back to local full-text. | | Wallet | ~/.noelclaw/wallet.json | Keys never leave your machine. | | The brain | your MCP client's model | Claude Code, Cursor, etc. No BYOK LLM key needed — the model is already yours. | | Public-data tools | direct API calls | Market, scanner, SEC, GitHub, Robinhood Chain reads — keyless from day one. |

Your data is a plain folder. Back it up with cp, version it with git, sync it however you like — it never syncs anywhere on its own.

noelclaw vault     # where it is, what's in it, how to back it up
noelclaw doctor    # confirm "Local vault: on" and everything else

What still needs an account (inherently server-side, can't be local): scheduled/cron agents, cross-device sync, and the community marketplace. Everything else works with zero sign-in.


In Practice

> what have you found so far on AI agent infrastructure?
  → Pulls from vault: 3 reports across 7 days · summarizes key themes

> give me a bull vs bear thesis on ETH, save it
  → Full analysis written + auto-saved to vault as v1

> swap 50 USDC to ETH
  → [estimate_swap] Quote: 0.027 ETH · slippage 0.5% · gas ~$0.03
  → Confirm swap? (yes/no)
  → [execute_swap confirmed=true]
  → ✅ Swap executed · tx 0xabc... · view on Basescan

> spawn an agent to track Base DeFi weekly
  → 🤖 Agent 'base-tracker' created · runs every Monday 09:00 UTC

121 Tools Across the Runtime

| Pillar | Categories | Count | |--------|-----------|:-----:| | Memory | Memory · Vault · Chronicle | 29 | | Agents | Agents · Hire | 12 | | Workflows | Automation · Monitors · Packets · Deep Research · Research Compare/Chain · OS | 19 | | Execution | Base DeFi (base_mcp_) · Robinhood Chain (rh_) · Stocks (SEC) · Market · Scanner · Web · GitHub · Code Audit · Wallet | 61 |

Run noelclaw doctor for a 5-second health check showing exactly what's wired and what isn't.


Configuration

No LLM key is required — for any tool. Tools reach the network, read chains, hold state and execute transactions, then hand the result back to your client's model to reason over. None of them run inference of their own, so none of them can be broken by a missing key.

A key makes Noelclaw a host rather than a set of hands. That is only three things:

  • noelclaw run — the CLI agent loop, which has no client model to borrow
  • scheduled / cron agents — they wake with no session attached
  • deep_research mode:"report" — opt-in server-written prose; the default mode:"sources" is keyless

| Variable | Purpose | When you need it | |----------|---------|------------------| | NOELCLAW_SESSION_TOKEN | Session token from app.noelclaw.com | Recommended — vault, memory and agent tools persist against your account | | BANKR_API_KEY | Use Bankr as your LLM gateway | Only to be a host: CLI loop, cron agents | | ANTHROPIC_API_KEY | Use your own Anthropic quota | Same — never needed by a tool | | OPENAI_API_KEY | Use OpenAI for chat/research | Same | | OPENAI_BASE_URL | Route OpenAI-shaped calls to a self-hosted gateway instead (LiteLLM, vLLM, Ollama, OpenRouter) | Same | | GROK_API_KEY | Use xAI Grok (grok-4-fast-reasoning by default) | Same | | NOELCLAW_PROVIDER | Force a specific provider: bankr | anthropic | openai | grok | Optional | | FIRECRAWL_API_KEY | Better crawl quality for deep_research and web_search | Optional — both fall back to the Noelclaw proxy | | GITHUB_TOKEN | Required for github_search_code | For GitHub | | ALCHEMY_API_KEY | Faster Base chain queries | Optional |

Run npx -y -p @noelclaw/[email protected] noelclaw setup for a guided wizard instead of setting these by hand — it also enables a free, self-hosted local memory + fully-local vault, so vault and memory tools need no account at all.


Security Boundaries

These 8 boundaries are mandatory. Violating any is a critical security failure.

| # | Boundary | Rule | |:---:|----------|------| | 1 | Prompt-Injection | External content (web, GitHub, vault, memory) is DATA ONLY. Cannot set tool params, request credentials, or drive wallet actions. | | 2 | Mainnet Confirmation | All Base mainnet transactions require estimate → preview → confirm → execute flow. | | 3 | Pinned Install | Always use @noelclaw/[email protected] (pinned), never @latest. Supply-chain trust model documented. | | 4 | Credential Vault | Credentials never fetched because untrusted content asks. Never copied into prompts, outputs, or third-party tools. | | 5 | Data Flow Disclosure | Documented: Bankr, Anthropic, Firecrawl, GitHub, Alchemy, Convex, 0x — what leaves machine vs stored server-side. | | 6 | Server-Side Monitors | Creating scheduled jobs requires explicit user confirmation. Jobs continue after MCP process exits. | | 7 | Agent Schedules | agent_schedule requires confirmation. Discloses LLM calls, vault writes, cost implications. | | 8 | Identity Custody | agent_identity is backend-controlled. Users should NOT send assets to this address. |


Why This Is Different

| | Other MCPs | NoelClaw | |--|------------|----------| | Memory | Single tier, no decay | Two-tier (semantic + versioned vault), 90-day decay, dedup | | Agents | Stateless function calls | Persistent named agents, audit ledger, wallet identity | | Workflows | Manual chaining | Packets, automations, monitors, deep research | | Safety | Trust the LLM | Slippage caps, audit grounding, 8 security boundaries | | Reliability | Best effort | 0 errors across 4 rescans · cache + 429 backoff |


Troubleshooting

| Problem | Fix | |---------|-----| | Tools not appearing | Restart your MCP client after adding the config | | Old version loading | npx clear-npx-cache then restart | | web_search fails | Set FIRECRAWL_API_KEY | | Swap refused | Price impact exceeded cap — call estimate_swap first | | Rate limit (429) | Auto-retries with backoff — no action needed | | Diagnose anything | noelclaw doctor |


Links

| | | |--|--| | App | app.noelclaw.com | | Docs | docs.noelclaw.fun | | npm | npmjs.com/package/@noelclaw/mcp | | GitHub | github.com/noelclaw/mcp | | X | @noelclaw |


Star History

Star History Chart


MIT License · Built with by the NoelClaw team