ChainFX Capability Network

io.github.techleadevelopersPublished by GitHub account techleadevelopersv1.6.3Updated Oct 24, 2026

Agent Pay and planning graph for stablecoin commerce.

The publisher's own server: Physical Capability Cloud

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for an agent pay and planning graph for stablecoin commerce, with optional discovery and API-key-gated purchases and payments.

What you can do
  • Discovery of the ChainFX capability network without credentials.
  • Purchases, execution and private status checks using a ChainFX API key.
  • Machine-to-machine payments over stablecoins.
  • Planning-graph support for stablecoin commerce workflows.
When to use it
Consider it when an assistant needs to discover capabilities in the ChainFX network or carry out stablecoin-based purchases, execution and machine-to-machine payments on the user's behalf.
Requirements
Remote streamable HTTP endpoint at api.chainfx.store; no local runtime or package. A ChainFX API key sent as a Bearer token in the Authorization header is required for purchases, execution, private status and M2M payments; discovery works without it.
Before you install
The server handles payments and purchases with stablecoins, so connected assistants may spend funds. The Authorization header carries a ChainFX API key that should be scoped and kept secret. No tool list is published, so the exact write and payment actions are not documented here.

Installation

In SourceWeft

  1. Open ChainFX Capability Network 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.techleadevelopers%2Fchainfx-mcp/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": {
    "chainfx-capability-network": {
      "type": "http",
      "url": "https://api.chainfx.store/mcp/initialize"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.6.3LatestSep 16, 2026

Score

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

Other Capability integrations