io.github.PedroQuatro/petra402
REMOTE · PETRA402.COM · SCANNED SEP 29
Public web page to markdown, paid per call with x402. First 10 calls free, no signup.
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 → Why this is hard to score →
Endpoint Security46
- 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 1 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 271 tokens (~271/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.PedroQuatro/petra402 MCP server?
io.github.PedroQuatro/petra402 is a hosted endpoint at https://petra402.com/mcp?src=mcp-registry, 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 · petra402.com
claude mcp add --transport http pedroquatro-petra402 'https://petra402.com/mcp?src=mcp-registry'
{
"mcpServers": {
"pedroquatro-petra402": {
"url": "https://petra402.com/mcp?src=mcp-registry"
}
}
} {
"servers": {
"pedroquatro-petra402": {
"type": "http",
"url": "https://petra402.com/mcp?src=mcp-registry"
}
}
} [mcp_servers.pedroquatro-petra402] url = "https://petra402.com/mcp?src=mcp-registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pedroquatro-petra402": {
"type": "remote",
"url": "https://petra402.com/mcp?src=mcp-registry",
"enabled": true
}
}
} openclaw mcp add pedroquatro-petra402 --url 'https://petra402.com/mcp?src=mcp-registry' --transport streamable-http
mcp_servers:
pedroquatro-petra402:
url: "https://petra402.com/mcp?src=mcp-registry" {
"McpServers": {
"pedroquatro-petra402": {
"Transport": "http",
"Url": "https://petra402.com/mcp?src=mcp-registry"
}
}
} assistant mcp add pedroquatro-petra402 -t streamable-http -u 'https://petra402.com/mcp?src=mcp-registry'
{
"mcpServers": {
"pedroquatro-petra402": {
"type": "http",
"url": "https://petra402.com/mcp?src=mcp-registry"
}
}
} 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.
- 28 Sept 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
- 25 Sept 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
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 59
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 29 Sept 2026 · Probed https://petra402.com/mcp?src=mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=petra402.com | CN=WE1,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 637593e33ba16e241380c47e20e19bc0 |
| SANs: petra402.com, api.petra402.com, *.api.petra402.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of petra402.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| petra402.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://petra402.com/mcp?src=mcp-registry | Verified | 200 | |
| http (plaintext) | http://petra402.com/mcp?src=mcp-registry | Inconclusive | 405 |
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 →
scrape ~271
Fetch a public web page and return its main content as markdown. Charged per successful call with x402: 0.005 USDC on Base Sepolia (testnet). A failed scrape is never charged, and a cache hit inside 24 h is free. Payment happens at the HTTP transport layer: an unpaid call answers 402 with the payment requirements; sign and repeat the identical JSON-RPC call with the payment header. This server speaks x402 v2 (PAYMENT-SIGNATURE / PAYMENT-RESPONSE), not v1 (X-PAYMENT). A v1 client will loop on 402 without ever settling. Refusals that are policy and never charged: government, military and any health-related domain; private or internal addresses; paths disallowed by robots.txt; sites protected by an anti-bot vendor (never bypassed).
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | bypass the 24 h cache (a cache hit is free; fresh is always charged) |
| links | boolean | – | keep link targets in the markdown |
| max_age_seconds | number | – | accept a cached copy only if it is younger than this |
| max_chars | number | – | truncate the markdown; the answer reports truncated and chars_total |
| url | string | yes | absolute http(s) URL of a public page |
No output schema declared.
No examples provided.
What is the io.github.PedroQuatro/petra402 MCP server?
io.github.PedroQuatro/petra402 is an MCP server listed in the public MCP registry as io.github.PedroQuatro/petra402. Public web page to markdown, paid per call with x402. First 10 calls free, no signup. This page covers its hosted endpoint (https://petra402.com/mcp?src=mcp-registry).
Is the io.github.PedroQuatro/petra402 MCP server safe to use?
io.github.PedroQuatro/petra402 scores 64 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.PedroQuatro/petra402 MCP server expose?
io.github.PedroQuatro/petra402 exposes 1 tool: scrape. Their descriptions and schemas cost roughly 271 tokens of context every time the server is loaded.
Does the io.github.PedroQuatro/petra402 MCP server require authentication?
No. We connected to io.github.PedroQuatro/petra402 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.PedroQuatro/petra402 MCP server still maintained?
io.github.PedroQuatro/petra402 is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.