Connect PubFi and your agent gets 4 tools, among them pubfi.capabilities.get, pubfi.capabilities.list, pubfi.route.execute. It answers at https://mcp.pubfi.ai over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Use MCP 2026-07-28 server/discover to list PubFi capabilities and execute an exact route.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
pubfi.capabilities.get | Return the full typed request, response, metering, and readiness contract for one exact capability id from the installed Registry generation. Inputs: capability_id |
pubfi.capabilities.list | Enumerate the complete installed Registry v2 catalog as deterministic compact pages. The server does not rank, infer intent, or choose a capability. Inputs: limit, cursor, provider_key, method |
pubfi.route.execute | Execute one exact GET or POST path through the authenticated PubFi account lane and the same Registry v2 matcher and typed executor as the HTTP gateway. Append :free only when the capability catalog publishes that exact account-scoped free Inputs: raw_path, method, query, body, idempotency_key, request_id |
pubfi.substrate.runtime_upgrade.verify | Verify one reviewed Substrate System.apply_authorized_upgrade extrinsic through the authenticated account lane. Supply the expected Blake2b-256 hash of the FRAME System AuthorizedUpgrade code payload, not the active :code hash at the apply Inputs: network, extrinsic_index, extrinsic_hash, expected_authorized_code_hash, idempotency_key, request_id |
Every block below points at https://mcp.pubfi.ai. Pick your client and copy.
claude mcp add --transport http pubfi https://mcp.pubfi.ai
{
"mcpServers": {
"pubfi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.pubfi.ai"]
}
}
}{
"mcpServers": {
"pubfi": {
"url": "https://mcp.pubfi.ai"
}
}
}{
"servers": {
"pubfi": {
"type": "http",
"url": "https://mcp.pubfi.ai"
}
}
}{
"context_servers": {
"pubfi": {
"url": "https://mcp.pubfi.ai"
}
}
}{
"mcpServers": {
"pubfi": {
"serverUrl": "https://mcp.pubfi.ai"
}
}
}{
"mcpServers": {
"pubfi": {
"url": "https://mcp.pubfi.ai"
}
}
}name: PubFi
version: 0.0.1
schema: v1
mcpServers:
- name: PubFi
type: streamable-http
url: https://mcp.pubfi.ai{
"mcpServers": {
"pubfi": {
"httpUrl": "https://mcp.pubfi.ai"
}
}
}{
"mcpServers": {
"pubfi": {
"type": "http",
"url": "https://mcp.pubfi.ai"
}
}
}{
"mcpServers": {
"pubfi": {
"url": "https://mcp.pubfi.ai"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.pubfi.ai&type=streamable_http&id=pubfi&name=PubFi
It answered our last check on 17 October 2026 in 162 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by pubfi.ai and served from mcp.pubfi.ai, the vendor's own domain: https://mcp.pubfi.ai.
4, as returned by the server's own tools/list on 8 September 2026: pubfi.capabilities.get, pubfi.capabilities.list, pubfi.route.execute, pubfi.substrate.runtime_upgrade.verify.
It answered our last check on 17 October 2026 in 162 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.pubfi.ai. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.pubfi. Endpoint host: mcp.pubfi.ai. ARD identifier: urn:air:ai.pubfi:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.