Substreams Search

Search, inspect, and analyze Substreams packages from the substreams.dev registry — module graphs, protobuf types, and sink deployment commands.

This skill appears to implement the advertised features, but review these before installing/ running: - Verify source/packaging: npx will execute code published on npm. Check the npm package page and the GitHub repo (owner PaulieB14) to confirm the published code matches the repository and is from a trusted maintainer. - Python artifacts present: the bundle includes server.py and requirements.txt but the skill only declares Node as required. Ask the maintainer why a Python implementation is included or inspect the files locally — don't assume only Node code will run. - Network exposure: the server can open an HTTP/SSE endpoint (default port 3849). If you run this on a shared or publicly reachable host, ensure it binds to localhost or is behind a firewall so it cannot be accessed from the internet unintentionally. - Remote fetches: the tool fetches arbitrary .spkg URLs and scrapes substreams.dev HTML. These remote inputs could be malformed or hostile; consider running in a restricted environment or container, and avoid running as a privileged user. - Safer testing: inspect the repository code locally (build directory / installed package contents) before running npx, or run npx in a disposable container/VM. If you need higher assurance, request the maintainer to provide a signed release or verify the package integrity on npm/GitHub before use.

Type: OpenClaw Skill Name: substreams-search-mcp Version: 1.3.2 The skill bundle provides a legitimate MCP server for searching the Substreams package registry and inspecting blockchain data stream packages (.spkg files). It implements tools in both Python (server.py) and TypeScript (src/index.ts) that perform web scraping of substreams.dev and utilize the @substreams/core library to parse protobuf metadata. While it includes functionality to generate CLI deployment commands and starts a local HTTP server for SSE transport (port 3849), these behaviors are clearly documented in SKILL.md and README.md and align with the stated purpose of assisting developers in the Substreams ecosystem.