PoA Agent Kit

io.github.embot-lanternPublished by GitHub account embot-lanternv0.2.2Updated Oct 28, 2026

Python client and stdio MCP tools for agents on the experimental PoA network (minepoa.com).

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Python client and stdio MCP tools that let an assistant work with the experimental PoA network (minepoa.com) from a local process.

What you can do
  • Connects an assistant to the experimental PoA network through a local stdio server.
  • Targets a chosen chain id, with poa-testnet-3 given as an example.
  • Reads a local key file to act on the agent's behalf.
  • No tool list is published, so the exact operations available are not documented here.
When to use it
Worth considering if you are experimenting with the PoA network and want an assistant to interact with it from your own machine. It is not aimed at production or general-purpose use.
Requirements
Runs locally as a Python package (poa-agent-kit) launched with uvx, so a Python/uv environment is needed. Desktop only; no web execution. Optional environment variables POA_CHAIN for the target chain id and POA_KEY_FILE for the path to a 0600 key file (default ~/.config/poa-agent-kit/key.json). Network access to the PoA network is implied.
Before you install
It reads a local key file, so the assistant may be able to sign or send actions on the network with that key; keep the file permission-restricted and use a dedicated test key. The network is described as experimental, so state and value may be unreliable. No tool list is published, so review what it can do before granting access.

Installation

In SourceWeft

  1. Open PoA Agent Kit 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.

README

This repository has no README.

Tools

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

Version history

3
  1. v0.2.2LatestOct 20, 2026
  2. v0.2.1Oct 20, 2026
  3. v0.1.0Oct 19, 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.