Wolfpack Intelligence

io.github.rok-labsPublished by GitHub account rok-labsv2.1.0Updated Oct 27, 2026

On-chain security and market intelligence for trading agents on Base.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint offering on-chain security and market intelligence for trading agents on the Base network.

What you can do
  • Provides on-chain security and market intelligence for trading agents on Base.
  • No tool list, instructions or README were supplied, so the specific actions the assistant can take are not documented here.
  • The only stated purpose is supplying security and market data about Base on-chain activity to trading agents.
When to use it
Consider it when an assistant or trading agent needs on-chain security and market context for the Base network and you are comfortable relying on a hosted third-party endpoint with undocumented tools.
Requirements
A remote streamable HTTP endpoint at api.wolfpack.roklabs.dev; no packages, environment variables, headers or authentication are declared. Network access to that host is required.
Before you install
The server is hosted by a third party and its tools are not documented, so what data it sends or receives is unclear. No authentication is declared, so requests may be unauthenticated. Treat any market or security signals as unverified input, not trading advice.

Installation

In SourceWeft

  1. Open Wolfpack Intelligence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rok-labs%2Fwolfpack-intelligence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "wolfpack-intelligence": {
      "type": "http",
      "url": "https://api.wolfpack.roklabs.dev/api/v1/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.1.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.