Bitpoort

com.bitpoortPublished by bitpoort.comOfficial publisherv3.4.1Updated Oct 27, 2026

On-chain blockchain data for AI agents across Ethereum, Bitcoin, and Hyperliquid.

VerifiedSSEWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint giving AI assistants on-chain blockchain data for Ethereum, Bitcoin and Hyperliquid.

What you can do
  • Provides on-chain blockchain data for Ethereum, Bitcoin and Hyperliquid to an assistant.
  • No tool list is published, so the exact queries available are not documented here.
  • Access is authenticated per request with an API key header.
When to use it
Worth adding when an assistant needs on-chain data from Ethereum, Bitcoin or Hyperliquid, for example to look up blockchain activity while answering questions or building analyses.
Requirements
A remote SSE endpoint at bitpoort.com; no local package or runtime is needed. A required API key sent in the X-API-Key header, obtained by registering on the provider's site, which the manifest says includes a starting credit.
Before you install
The API key is a secret sent in the X-API-Key header; keep it out of shared logs and configs. The manifest mentions a starting credit, so usage may be metered or paid beyond it. No tool list or documentation is provided, so review what the server can do before relying on it.

Installation

In SourceWeft

  1. Open Bitpoort in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via SSE. 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/com.bitpoort%2Fon-chain-data/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": {
    "bitpoort": {
      "type": "sse",
      "url": "https://bitpoort.com/mcp/sse",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

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

Version history

1
  1. v3.4.1LatestSep 16, 2026

Score

56% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.