Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

PubFi MCP

by helixboxversion 0.3.3i★ –iRuns in the cloud
Registry nameai.pubfi/mcp

Install

Overview

Description from the maker (original English)

Use MCP 2026-07-28 discovery or 2025-11-25 initialize to list and execute PubFi routes.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Other
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http pubfi https://mcp.pubfi.ai --header 'Authorization: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pubfi": {
      "url": "https://mcp.pubfi.ai",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "pubfi": {
      "type": "http",
      "url": "https://mcp.pubfi.ai",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret HTTP header
    PubFi API key as a Bearer token. Optional for public capability list/get calls; required for route execution unless the client uses the accountless x402 lane. Example: Bearer .

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain pubfi.ai (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32509 servers in this category
  • Published to the registry more recently than 78% of the other 32509 servers in this category
  • Basic checks equal to or better than 100% of the other 32509 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is PubFi MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.3) reached the registry 9 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Fomu MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Fomu MCP

by gabrielmahia

Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

PubFi MCP Stdio Bridge Smoke Fixture

This public example is a local, dependency-free MCP-compatible stdio bridge and smoke fixture for the PubFi hosted MCP endpoint. Run it with Node.js 24.19.0 or a later Node.js 24 release.

The bridge forwards modern server/discover, list, and tools/call requests to the Rust MCP endpoint instead of synthesizing a second handshake, running a retired TypeScript route-tool implementation, or creating one public tool per provider. Every request carries complete MCP 2026-07-28 metadata and the bridge mirrors the standard HTTP routing headers. PubFi does not create protocol sessions. The bridge itself accepts only modern input; clients that need MCP 2025-11-25 initialize-era compatibility connect directly to the same hosted endpoint.

For hosted authenticated use, configure an MCP client for PubFi's Streamable HTTP endpoint at https://mcp.pubfi.ai. The hosted authenticated service uses four fixed Registry v2 tools. Catalog list/detail reads are public. Exact execution on this root requires a PubFi API key or OAuth access token. Eligible accountless x402 execution uses https://mcp.pubfi.ai/x402 without a Bearer credential. Upstream provider credentials stay server-side.

Tools

  • pubfi.capabilities.list
  • pubfi.capabilities.get
  • pubfi.route.execute
  • pubfi.substrate.runtime_upgrade.verify

pubfi.capabilities.list enumerates compact summaries with an opaque generation-bound cursor. pubfi.capabilities.get returns the full typed contract for one exact capability id. The client agent selects the capability; PubFi does not rank candidates or infer intent. Executable paths, methods, matchers, schemas, method-specific PubFi pricing, and readiness come only from the installed signed Registry generation.

Run In Staging

From the repository root:

export STG_PUBFI_API_KEY='<Staging PubFi API key>'

export PUBFI_MCP_ENDPOINT='https://mcp-stg.pubfi.ai' node examples/agents/pubfi-route-tools-mcp/server.ts

Example MCP client config:

{

"mcpServers": { "pubfi-route-tools": { "command": "node", "args": ["examples/agents/pubfi-route-tools-mcp/server.ts"] } } }

Start the client from an environment that supplies these variables, or use its secret-store integration. Do not put the key in a tracked configuration file.

Move To Production

Create a separate Production key and use the exact Production endpoint:

export PROD_PUBFI_API_KEY='<Production PubFi API key>'

export PUBFI_MCP_ENDPOINT='https://mcp.pubfi.ai' node examples/agents/pubfi-route-tools-mcp/server.ts

The client configuration above uses the same local command. Do not send a Staging key to the Production endpoint.

Smoke

node examples/agents/pubfi-route-tools-mcp/smoke_pubfi_route_tools_mcp.ts

node --test examples/agents/pubfi-route-tools-mcp/bridge-response.test.ts \ examples/agents/pubfi-route-tools-mcp/endpoint-policy.test.ts

For an authenticated Staging smoke:

export STG_PUBFI_API_KEY='<Staging PubFi API key>'

export PUBFI_MCP_ENDPOINT='https://mcp-stg.pubfi.ai' node examples/agents/pubfi-route-tools-mcp/smoke_pubfi_route_tools_mcp.ts

Without the endpoint-selected caller key, the smoke verifies modern discovery, the fixed tool list, complete catalog pagination, exact capability detail, and the execution credential gate. With STG_PUBFI_API_KEY for staging MCP endpoints or PROD_PUBFI_API_KEY for production MCP endpoints, the same catalog reads remain public. For a deliberate live request, set PUBFI_MCP_EXECUTE_LIVE=1, PUBFI_MCP_SMOKE_RAW_PATH, and PUBFI_MCP_SMOKE_METHOD from the current catalog. Optional PUBFI_MCP_SMOKE_QUERY and PUBFI_MCP_SMOKE_BODY supply the exact route input. PUBFI_MCP_SMOKE_BODY is the exact compact ASCII request body (for example, {"limit":10}), not a nested MCP JSON value. The smoke never invents a provider route or capability id.

See the Staging guide for login, key creation, HTTP checks, the Base Sepolia test boundary, and the Production transition.

For accountless payment, use an official x402 MCP client. An unsigned eligible pubfi.route.execute call on https://mcp-stg.pubfi.ai/x402 or https://mcp.pubfi.ai/x402 returns PaymentRequired in the MCP tool result. The retry carries the x402 V2 payment object at params._meta["x402/payment"]; the settled result carries result._meta["x402/payment-response"]. Do not pass a PubFi API key, private key, or PAYMENT-SIGNATURE HTTP header in this flow.

The stdio bridge accepts only the exact production and staging roots (https://mcp.pubfi.ai and https://mcp-stg.pubfi.ai). It rejects userinfo, ports, alternate paths, query strings, fragments, lookalike hosts, and redirects before forwarding a scoped caller key. PUBFI_MCP_ORIGIN is not a supported alias.

The hosted deploy-equivalent smoke is included in:

npm run smoke:mcp-e2e --workspace apps/web -- --json

npm run smoke:mcp-e2e --workspace apps/web -- --execute-live --json

Execution Boundary

pubfi.route.execute accepts an exact raw_path and method selected after list/detail catalog reads. The Rust Data Plane resolves that pair through the installed Registry v2 matcher and uses the same typed executor, credential authority, Credit accounting, generation, and fail-closed readiness state as the HTTP gateway. A blocked or absent current-catalog route remains non-executable. This bridge does not add provider branches, capability ranking, compatibility route ids, supplier procurement, automatic payment, or a second catalog authority.

Ask PopNx