io.github.P2Flux/mcp
REMOTE · AGENT.P2FLUX.COM · 2 COMPONENTS
Let your AI assistant pay for web content in USDC (x402) within a budget you set.
Available components
Last scanned (22 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 359 tokens (~89/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management88
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 84 to 88.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 74 to 78.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 68 to 71.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 61 to 64.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 54 to 57.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 48 to 51.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.
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 4 Nov 2026 · Probed https://agent.p2flux.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agent.p2flux.com | CN=YE2,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5393cd7d870152e9bf4f23ff1b7fa08289a |
| SANs: agent.p2flux.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent.p2flux.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| p2flux.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent.p2flux.com/mcp | Verified | 200 | |
| http (plaintext) | http://agent.p2flux.com/mcp | HTTPS enforced | 301 | https://agent.p2flux.com/mcp |
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 →
check_price ~73
See what a web page costs for an AI agent, without paying.
| Name | Type | Req | Description |
|---|---|---|---|
| access_tokens | array | – | Access tokens exactly as get_paid_page gave them (host|token|seal). Each is sent only to the site it was given for; others are ignored. |
| url | string | yes | The page address (https). |
No output schema declared.
No examples provided.
find_paid_content ~65
Search the P2Flux directory for websites that sell content to AI agents. Returns site names, what they offer and the price per page. Costs nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Words to look for, e.g. "soup recipes". Empty lists the newest sites. |
No output schema declared.
No examples provided.
get_paid_page ~61
Get the text of a page after the user approved its payment (see request_paid_page).
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The claim from request_paid_page (not on the approval link). |
| request_id | string | yes | The request_id from request_paid_page. |
No output schema declared.
No examples provided.
request_paid_page ~160
Ask to read a paid web page. Returns a link the USER must open to approve the payment in their own wallet - show the link and the price to the user and wait. Then call get_paid_page with the request_id. Nothing is paid without the user approving it.
| Name | Type | Req | Description |
|---|---|---|---|
| access_tokens | array | – | Access tokens exactly as get_paid_page gave them (host|token|seal). Each is sent only to the site it was given for; others are ignored. |
| max_price | string | – | The most to pay for this page, in USDC, e.g. "0.10". Required, after asking the user, for anything above a few USDC (a subscription). |
| url | string | yes | The page address (https). |
No output schema declared.
No examples provided.
How do I install the io.github.P2Flux/mcp server?
io.github.P2Flux/mcp is a hosted endpoint at https://agent.p2flux.com/mcp, 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 · agent.p2flux.com
claude mcp add --transport http p2flux-mcp 'https://agent.p2flux.com/mcp'
What is the io.github.P2Flux/mcp server?
io.github.P2Flux/mcp is listed in the public MCP registry as io.github.P2Flux/mcp. Let your AI assistant pay for web content in USDC (x402) within a budget you set. This page covers its hosted endpoint (https://agent.p2flux.com/mcp).
Is the io.github.P2Flux/mcp server safe to use?
io.github.P2Flux/mcp scores 80 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 io.github.P2Flux/mcp server expose?
io.github.P2Flux/mcp exposes 4 tools: find_paid_content, check_price, request_paid_page, get_paid_page. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.
Does the io.github.P2Flux/mcp server require authentication?
No. We connected to io.github.P2Flux/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.P2Flux/mcp server still maintained?
io.github.P2Flux/mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.