PubFi MCP
REMOTE · MCP.PUBFI.AI · SCANNED AUG 3
Enumerate and inspect PubFi capabilities, then execute an exact selected route.
Available components
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 →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 323 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 8 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.pubfi.ai
claude mcp add --transport http ai-pubfi-mcp https://mcp.pubfi.ai/
[mcp_servers.ai-pubfi-mcp] url = "https://mcp.pubfi.ai/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-pubfi-mcp": {
"type": "remote",
"url": "https://mcp.pubfi.ai/",
"enabled": true
}
}
} openclaw mcp add ai-pubfi-mcp --url https://mcp.pubfi.ai/ --transport streamable-http
mcp_servers:
ai-pubfi-mcp:
url: "https://mcp.pubfi.ai/" {
"mcpServers": {
"ai-pubfi-mcp": {
"type": "http",
"url": "https://mcp.pubfi.ai/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Aug 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- Server version: 0.1.78 → 0.1.79 functional
- 30 Jul 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- First check of Schema quality: unverified functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 0.1.76 → 0.1.77 functional
- 29 Jul 26 +1
- Stability: 0.07 → fail ▼ security
- Tool “pubfi.capabilities.search” was removed ▼ security
- Tool “pubfi.route.explain” was removed ▼ security
- Tool “pubfi.route.plan” was removed ▼ security
- Tool “pubfi.schema.get” was removed ▼ security
- Tool “pubfi.route.execute” is now declared destructive security
- Schema quality: 544 → 323 ▲ functional
- Tool “pubfi.route.execute” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 0.1.74 → 0.1.76 functional
- New tool “pubfi.capabilities.get” functional
- New tool “pubfi.capabilities.list” functional
- 28 Jul 26 +1
- Server version: 0.1.63 → 0.1.74 functional
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
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 3 Aug 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=YR1,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | RSA 2048 | SHA256-RSA | 5d80177f7bedd5ffa22f1031a98b45d5f68 |
| SANs: *.pubfi.ai, pubfi.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 |
DNSSEC insecure
Validation of mcp.pubfi.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| pubfi.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
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.
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 ~170
Execute one exact GET or POST path through the same Registry v2 matcher, credential authority, and typed executor as the HTTP gateway. Use either an authenticated account lane with metering or the accountless x402 payment metadata lane.
| 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.