Blockfill

services.quantechPublished by quantech.servicesv1.2.1Updated Oct 24, 2026

Local-first crypto perp/spot execution (TWAP/maker) across 11 venues; keys stay on your machine.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Blockfill is a local-first MCP server for crypto perpetual and spot order execution, including TWAP and maker strategies, across 11 venues, with keys kept on a

What you can do
Place and manage crypto perpetual and spot orders across 11 trading venues, including TWAP and maker execution styles, from an assistant on the user's machine. The server runs locally over stdio, so trading credentials are described as staying on the user's machine rather than passing through a hosted service. No individual tools are listed in the supplied material, so the exact operations available are not documented here.
When to use it
Useful when an assistant should help execute or schedule crypto perpetual and spot trades across multiple venues and the user wants a local-first setup where keys remain on their own machine. Not intended for general market data, portfolio analysis, or non-crypto trading.
Requirements
Runs as a local process on the user's machine via uvx from the blockfill PyPI package, so Python and uv/uvx are needed. Desktop only; no web execution. No authentication, environment variables, or headers are declared in the manifest, though trading venues will presumably require their own account credentials.
Before you install
This server places real crypto trades, so mistakes or unintended orders can move or lose money. It handles exchange API keys and possibly wallet-related credentials; the manifest declares no environment variables, so how keys are supplied is unclear and should be verified before use. Orders write to live exchange accounts and may be irreversible.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.1LatestSep 16, 2026

Score

25% 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 days25 pts

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

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

  • License10 pts

    Declare a license in the repository or the registry entry.