PubFi MCP
REMOTE · MCP.PUBFI.AI
Use MCP 2026-07-28 discovery or 2025-11-25 initialize to list and execute PubFi routes.
Available components
Last scanned (4 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 954 tokens (~34/item across 28 items; 4 tools + 24 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Resource “orca-v2 OpenAPI” now points somewhere else: pubfi://registry/openapi/orca-v2/c32e73022cb638427758fc8aa06c89c709953565101fb022530e87ff02175260 → pubfi://registry/openapi/orca-v2/c234f65eeb8ed9007223690ef96a43d70b483a34ebaf91fd15d20c65b758eabb security
- Resource “raydium-v3 OpenAPI” now points somewhere else: pubfi://registry/openapi/raydium-v3/61fed8aa044b043fac6723a21000d410c1e639806714a6e0a9b90c33d957406c → pubfi://registry/openapi/raydium-v3/3e5b6e23fcf5a5649744bae2a224bd566a4123f7ab722a31d211dc8e5a4b672b security
- 4 Nov 26 0
- Resource “sourcify-server-v2 OpenAPI” now points somewhere else: pubfi://registry/openapi/sourcify-server-v2/e536a39aa4506f67dca6e3c235ebe5fd5702ec7733e6d0e705fef381f0539737 → pubfi://registry/openapi/sourcify-server-v2/82604f05db08fc8811b49a8db5e44a76f0f4b9214603dc31448ffc3c1911e91e security
- Resource “subscan OpenAPI” now points somewhere else: pubfi://registry/openapi/subscan/32f53c4cbbc50f024cd7b006e86ab3b852db4d5ca5069e52ad2dca6bc2cc888d → pubfi://registry/openapi/subscan/10807a0d65d7b1cc5935852a4b6ab32582c8726ec254c924fc33085f8824bcc4 security
- 3 Nov 26 0
- Resource “orca-v2 OpenAPI” now points somewhere else: pubfi://registry/openapi/orca-v2/cb33c992ef820c2388cc949928b2c45ab3d78c36bd808e18fdf0433114e9e5e3 → pubfi://registry/openapi/orca-v2/c32e73022cb638427758fc8aa06c89c709953565101fb022530e87ff02175260 security
- Resource “subscan OpenAPI” now points somewhere else: pubfi://registry/openapi/subscan/09232e5d500d394fae89ce893fbd08229d5bd996e061548dde7452032888b4fe → pubfi://registry/openapi/subscan/32f53c4cbbc50f024cd7b006e86ab3b852db4d5ca5069e52ad2dca6bc2cc888d security
- 31 Oct 26 0
- Resource “subscan OpenAPI” now points somewhere else: pubfi://registry/openapi/subscan/3bba61165c1bf9f49f6b55f76016910841e279dbb90c39a26213038fd1b66fc8 → pubfi://registry/openapi/subscan/09232e5d500d394fae89ce893fbd08229d5bd996e061548dde7452032888b4fe security
- 28 Oct 26 0
- Server version: 0.3.2 → 0.3.3 functional
- 27 Oct 26 0
- Resource “subscan OpenAPI” now points somewhere else: pubfi://registry/openapi/subscan/7d6078e609918cfed03a7c06a31240b6cf361dfa2f05a83a6d0c97e649362fe2 → pubfi://registry/openapi/subscan/3bba61165c1bf9f49f6b55f76016910841e279dbb90c39a26213038fd1b66fc8 security
- Server version: 0.3.1 → 0.3.2 functional
- Server version: 0.3.0 → 0.3.1 functional
- Server version: 0.2.85 → 0.3.0 functional
- 26 Oct 26 0
- Resource “raydium-v3 OpenAPI” now points somewhere else: pubfi://registry/openapi/raydium-v3/3e5b6e23fcf5a5649744bae2a224bd566a4123f7ab722a31d211dc8e5a4b672b → pubfi://registry/openapi/raydium-v3/61fed8aa044b043fac6723a21000d410c1e639806714a6e0a9b90c33d957406c security
- Server version: 0.2.84 → 0.2.85 functional
- 25 Oct 26 0
- Resource “raydium-v3 OpenAPI” now points somewhere else: pubfi://registry/openapi/raydium-v3/61fed8aa044b043fac6723a21000d410c1e639806714a6e0a9b90c33d957406c → pubfi://registry/openapi/raydium-v3/3e5b6e23fcf5a5649744bae2a224bd566a4123f7ab722a31d211dc8e5a4b672b security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.pubfi.ai
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pubfi.ai | CN=YR2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | RSA 2048 | SHA256-RSA | 5f86c1cb62f74e2f3292f820e3162f1ea06 |
| SANs: *.pubfi.ai, pubfi.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.pubfi.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| pubfi.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.pubfi.ai/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.pubfi.ai/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.pubfi.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.pubfi.ai |
| Authorisation server | https://mcp.pubfi.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.pubfi.ai | Verified | 200 | |
| http (plaintext) | http://mcp.pubfi.ai | HTTPS enforced | 301 | https://mcp.pubfi.ai/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pubfi.capabilities.get ~54
Return the full typed request, response, metering, and readiness contract for one exact capability id from the installed Registry generation.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | yes | Exact capability id returned by pubfi.capabilities.list. |
| Name | Type | Req | Description |
|---|---|---|---|
| capability | object | yes | – |
| compiled_at | string | yes | – |
| generation | object | yes | – |
| manifest | object | yes | – |
| observed_at | string | yes | – |
| schema_version | – | yes | – |
No examples provided.
pubfi.capabilities.list ~99
Enumerate the complete installed Registry v2 catalog as deterministic compact pages. The server does not rank, infer intent, or choose a capability.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque generation-bound cursor returned by the preceding page. |
| limit | integer | – | Maximum compact capability summaries to return. |
| method | string | – | – |
| provider_key | string | – | Optional exact public provider key. This is a static filter, not semantic search. |
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | – |
| compiled_at | string | yes | – |
| filters | object | yes | – |
| generation | object | yes | – |
| manifest | object | yes | – |
| matching_capability_count | integer | yes | – |
| next_cursor | string | – | – |
| observed_at | string | yes | – |
| schema_version | – | yes | – |
| total_capability_count | integer | yes | – |
No examples provided.
pubfi.route.execute ~171
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 variant.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Exact optional ASCII request-body bytes. For JSON routes, supply one compact serialized JSON document rather than a nested MCP argument value. |
| idempotency_key | string | – | – |
| method | string | yes | – |
| query | string | – | Exact ASCII raw query string without a leading question mark. |
| raw_path | string | yes | Exact original URI path consumed by the Registry matcher. Segments use canonical unreserved ASCII only; percent escapes, dot segments, query, fragment, and backslash are forbidden. |
| request_id | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
pubfi.substrate.runtime_upgrade.verify ~160
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 block. The server streams and discards provider runtime code, persists only a compact proof, and returns independent comparison evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_authorized_code_hash | string | yes | Canonical lowercase 0x-prefixed 32-byte hash. |
| extrinsic_hash | string | – | Canonical lowercase 0x-prefixed 32-byte hash. |
| extrinsic_index | string | – | – |
| idempotency_key | string | – | – |
| network | string | yes | – |
| request_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| computed_code_hash | string | yes | Canonical lowercase 0x-prefixed 32-byte hash. |
| credits_charged | integer | yes | – |
| execution_authority | – | yes | – |
| execution_status | – | yes | – |
| expected_authorized_code_hash | string | yes | Canonical lowercase 0x-prefixed 32-byte hash. |
| extrinsic_hash | string | yes | Canonical lowercase 0x-prefixed 32-byte hash. |
| extrinsic_index | string | yes | – |
| extrinsic_success | boolean | yes | – |
| generation | object | yes | – |
| matches | boolean | yes | – |
| meter_key | string | yes | – |
| ok | – | yes | – |
| provider | object | yes | – |
| provider_response_bytes | integer | yes | – |
| provider_response_sha256 | string | yes | – |
| reserved_units | integer | yes | – |
| route | object | yes | – |
| runtime_code_bytes | integer | yes | – |
| upstream | object | yes | – |
| upstream_latency_ms | integer | yes | – |
| upstream_status | – | yes | – |
No examples provided.
How do I install the PubFi MCP server?
PubFi MCP is a hosted endpoint at https://mcp.pubfi.ai/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.pubfi.ai
claude mcp add --transport http ai-pubfi-mcp 'https://mcp.pubfi.ai/'
What is the PubFi MCP server?
PubFi MCP is listed in the public MCP registry as ai.pubfi/mcp. Use MCP 2026-07-28 discovery or 2025-11-25 initialize to list and execute PubFi routes. This page covers its hosted endpoint (https://mcp.pubfi.ai).
Is the PubFi MCP server safe to use?
PubFi MCP scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PubFi MCP server expose?
PubFi MCP exposes 4 tools: pubfi.capabilities.list, pubfi.capabilities.get, pubfi.route.execute, pubfi.substrate.runtime_upgrade.verify. Their descriptions and schemas cost roughly 484 tokens of context every time the server is loaded.
Does the PubFi MCP server require authentication?
Yes. PubFi MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the PubFi MCP server still maintained?
PubFi MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.