# L2beat (npm · @pipeworx/mcp-l2beat)

L2BEAT MCP — Layer 2 ecosystem analytics

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-l2beat/l2beat-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-l2beat/l2beat-mcp)
- npm · `@pipeworx/mcp-l2beat`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-l2beat/pipeworx-mcp-l2beat.md), [page](https://verifymcp.io/servers/pipeworx-io-l2beat/pipeworx-mcp-l2beat)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-l2beat`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-l2beat).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 634 tokens (~126/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the L2beat MCP server?

L2beat runs locally as an npm package, launched with npx -y @pipeworx/mcp-l2beat. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-l2beat -- npx -y @pipeworx/mcp-l2beat
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-l2beat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-l2beat"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-l2beat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-l2beat"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-l2beat -- npx -y @pipeworx/mcp-l2beat
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-l2beat": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-l2beat"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-l2beat --command npx --arg -y --arg @pipeworx/mcp-l2beat
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-l2beat:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-l2beat"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-l2beat": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-l2beat"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-l2beat -t stdio -c npx -a -y @pipeworx/mcp-l2beat
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-l2beat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-l2beat"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 66, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (5)

### `list_projects` (~257 tokens)

Rank Ethereum layer 2 networks by Total Value Secured (TVS) in USD, largest first. Answers "which L2 has the most value secured / is the biggest L2", and gives the top-10 leaderboard of rollups, validiums, optimiums and sidechains. Each row returns rank, project name, L2BEAT slug, category (Optimistic Rollup / ZK Rollup / Validium / Other), layer type, host chain, decentralisation stage, tvs_usd, the 7-day TVS change, and the TVS split across native, canonical, external, ether, stablecoin and BTC holdings. Covers every project L2BEAT tracks; use limit to widen the leaderboard.

Input parameters:

- `category` (string): Keep only one category, e.g. "Optimistic Rollup", "ZK Rollup", "Validium".
- `include_archived` (boolean): Set true to also rank projects L2BEAT has archived (default false).
- `include_chart` (boolean): Set true to append the 124-point ecosystem-wide TVS time series (default false).
- `limit` (number): How many top-ranked projects to return (default 25, max 200).

### `get_project` (~49 tokens)

Full project record by slug — risks, stage, milestones, contracts.

Input parameters:

- `slug` (string, required): L2BEAT slug (e.g. "arbitrum", "optimism", "base")

### `tvs_breakdown` (~62 tokens)

Total Value Secured (TVS) breakdown by token category (canonical, external, native) for a specific L2 project slug or all projects; returns today's snapshot from L2BEAT.

Input parameters:

- `slug` (string): Specific project (default: all)

### `tvs_history` (~106 tokens)

Historical Total Value Secured (TVS) time series for an L2 project or all projects; accepts range (7d/30d/90d/180d/1y/max, default 30d) and optional project slug.

Input parameters:

- `range` (string): 7d | 30d | 90d | 180d | 1y | max (default 30d)
- `slug` (string): Specific project (default: all projects aggregate)

### `activity` (~106 tokens)

Daily transaction count (and UOPS where available) time series for an L2 project or all projects; accepts slug and range (7d/30d/90d/180d/1y/max, default 30d) from L2BEAT.

Input parameters:

- `range` (string): 7d | 30d | 90d | 180d | 1y | max (default 30d)
- `slug` (string): Specific project (default: all)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-l2beat/pipeworx-mcp-l2beat#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 66
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the L2beat MCP server?

L2beat is an MCP server listed in the public MCP registry as io.github.pipeworx-io/l2beat. L2BEAT MCP, Layer 2 ecosystem analytics. This page covers its npm package (@pipeworx/mcp-l2beat).

### Is the L2beat MCP server safe to use?

L2beat scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the L2beat MCP server expose?

L2beat exposes 5 tools: list_projects, get_project, tvs_breakdown, tvs_history, activity. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.

### Is the L2beat MCP server still maintained?

L2beat is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the L2beat MCP server under?

L2beat declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-l2beat
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-l2beat
- Repository: https://github.com/pipeworx-io/mcp-l2beat
- Website: https://pipeworx.io/packs/l2beat
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-l2beat/pipeworx-mcp-l2beat.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-l2beat/pipeworx-mcp-l2beat.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-l2beat/pipeworx-mcp-l2beat