# io.github.PedroQuatro/petra402 (remote · petra402.com)

Public web page to markdown, paid per call with x402. First 10 calls free, no signup.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `petra402.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/pedroquatro-petra402/petra402.md), [page](https://verifymcp.io/servers/pedroquatro-petra402/petra402)

## Channel facts

- Endpoint: `https://petra402.com/mcp?src=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http pedroquatro-petra402 'https://petra402.com/mcp?src=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "pedroquatro-petra402": {
      "url": "https://petra402.com/mcp?src=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pedroquatro-petra402": {
      "type": "http",
      "url": "https://petra402.com/mcp?src=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pedroquatro-petra402]
url = "https://petra402.com/mcp?src=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pedroquatro-petra402": {
      "type": "remote",
      "url": "https://petra402.com/mcp?src=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pedroquatro-petra402 --url 'https://petra402.com/mcp?src=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pedroquatro-petra402:
    url: "https://petra402.com/mcp?src=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "pedroquatro-petra402": {
      "Transport": "http",
      "Url": "https://petra402.com/mcp?src=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pedroquatro-petra402 -t streamable-http -u 'https://petra402.com/mcp?src=mcp-registry'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 62, +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.

### 2026-09-21 (score 61, +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.

### 2026-09-19 (score 60, +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.

### 2026-09-18 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 59)

First indexed and scored.

## MCP tools (1)

### `scrape` (~271 tokens)

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).

Input parameters:

- `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, required): absolute http(s) URL of a public page

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pedroquatro-petra402/petra402#diagnostics

## Score history

- 2026-09-29: 64
- 2026-09-28: 64
- 2026-09-27: 63
- 2026-09-26: 63
- 2026-09-25: 63
- 2026-09-24: 62
- 2026-09-23: 62
- 2026-09-22: 61
- 2026-09-21: 61
- 2026-09-20: 60
- 2026-09-19: 60
- 2026-09-18: 59
- 2026-09-17: 59

## Common questions

### 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.

## Links

- Remote endpoint: https://petra402.com/mcp?src=mcp-registry
- Repository: https://github.com/PedroQuatro/petra402-mcp
- Website: https://petra402.com/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/pedroquatro-petra402/petra402.xml
- Changelog JSON feed: https://verifymcp.io/servers/pedroquatro-petra402/petra402.json
- HTML version of this page: https://verifymcp.io/servers/pedroquatro-petra402/petra402