Connects Claude to L2BEAT's Layer 2 ecosystem data through five focused tools: list and fetch project details (risks, stages, milestones, contracts), query TVS breakdowns by token category, pull historical TVS time series, and retrieve daily transaction counts with UOPS metrics where available. Part of the Pipeworx gateway infrastructure, so you can either point directly at the L2BEAT endpoint or use the unified gateway with ask_pipeworx for natural language queries that auto-route to the right tool. Useful when you're analyzing rollup economics, comparing L2 adoption trends, or auditing bridge contracts and need structured data instead of scraping dashboards.
L2BEAT MCP — Layer 2 ecosystem analytics
Part of Pipeworx — an MCP gateway connecting AI agents to 673+ live data sources.
| Tool | Description |
|---|---|
list_projects | List all L2BEAT-tracked projects (rollups, validiums, optimiums, sidechains). |
get_project | Full project record by slug — risks, stage, milestones, contracts. |
tvs_breakdown | TVS breakdown by token category and project today. |
tvs_history | Historical TVS time series. |
activity | Daily transaction counts (and UOPS where available). |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"l2beat": {
"url": "https://gateway.pipeworx.io/l2beat/mcp"
}
}
}
Or connect to the full Pipeworx gateway for access to all 673+ data sources:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Instead of calling tools directly, you can ask questions in plain English:
ask_pipeworx({ question: "your question about L2beat data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
io.github.infoinlet-marketplace/mcp-observability
betterdb-inc/monitor
com.mcparmory/datadog
thotischner/observability-mcp
io.github.tantiope/datadog-mcp
io.github.us-all/datadog