# FreshProof (remote · freshproof.ricardobessellp-11d.workers.dev)

Timestamped public URL observations with SHA-256 fingerprints, paid in USDC on Base via x402.

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

## Components

- remote · `freshproof.ricardobessellp-11d.workers.dev`: 63/100 (this document), [markdown](https://verifymcp.io/servers/ricksporto-freshproof/freshproof.md), [page](https://verifymcp.io/servers/ricksporto-freshproof/freshproof)

## Channel facts

- Endpoint: `https://freshproof.ricardobessellp-11d.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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 406, 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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 308 tokens (~77/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the FreshProof MCP server?

FreshProof is a hosted endpoint at https://freshproof.ricardobessellp-11d.workers.dev/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.

### Claude

```bash
claude mcp add --transport http ricksporto-freshproof 'https://freshproof.ricardobessellp-11d.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ricksporto-freshproof": {
      "url": "https://freshproof.ricardobessellp-11d.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ricksporto-freshproof": {
      "type": "http",
      "url": "https://freshproof.ricardobessellp-11d.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ricksporto-freshproof]
url = "https://freshproof.ricardobessellp-11d.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ricksporto-freshproof": {
      "type": "remote",
      "url": "https://freshproof.ricardobessellp-11d.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ricksporto-freshproof --url 'https://freshproof.ricardobessellp-11d.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ricksporto-freshproof:
    url: "https://freshproof.ricardobessellp-11d.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ricksporto-freshproof": {
      "Transport": "http",
      "Url": "https://freshproof.ricardobessellp-11d.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ricksporto-freshproof -t streamable-http -u 'https://freshproof.ricardobessellp-11d.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ricksporto-freshproof": {
      "type": "http",
      "url": "https://freshproof.ricardobessellp-11d.workers.dev/mcp"
    }
  }
}
```

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-29 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 62, −2)

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

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

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

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

- [functional improvement] Stability: unverified → 0.03

### 2026-09-22 (score 61)

First indexed and scored.

## MCP tools (4)

### `freshproof_info` (~29 tokens)

Describe FreshProof, its observation semantics, current MCP price and payment network. This tool is free.

### `verify_proof` (~63 tokens)

Verify the deterministic integrity of an existing FreshProof proof receipt and optionally evaluate declarative policy rules. This tool is free and performs no new public-network fetch.

Input parameters:

- `policy` (object)
- `proof_id` (string, required): FreshProof proof identifier returned by observe_url

### `observe_url` (~136 tokens)

Buy a timestamped FreshProof observation of a public HTTP/HTTPS URL. Returns final URL, observation timestamp, age, HTTP status, SHA-256 body hash, body size, ETag, Last-Modified, fetch duration, and whether the observation came from shared cache or a fresh public-network request. Set max_age=0 when a new public-network request is required. The response body itself is not returned.

Input parameters:

- `max_age` (integer): Maximum acceptable observation age in seconds. Defaults to 300. Set to 0 to force a fresh public-network request.
- `url` (string, required): Public HTTP or HTTPS URL to observe

### `verify_url` (~80 tokens)

Buy a FreshProof URL observation and immediately evaluate declarative trust policy rules against the resulting proof. This combines observe_url and verify_proof in one paid agent workflow.

Input parameters:

- `max_age` (integer)
- `policy` (object, required): Declarative policy evaluated against the resulting proof
- `url` (string, required): Public HTTP or HTTPS URL to observe and verify

## Diagnostics

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

## Score history

- 2026-09-29: 63
- 2026-09-28: 62
- 2026-09-27: 64
- 2026-09-26: 63
- 2026-09-25: 63
- 2026-09-24: 62
- 2026-09-23: 62
- 2026-09-22: 61

## Common questions

### What is the FreshProof MCP server?

FreshProof is an MCP server listed in the public MCP registry as io.github.ricksporto/freshproof. Timestamped public URL observations with SHA-256 fingerprints, paid in USDC on Base via x402. This page covers its hosted endpoint (https://freshproof.ricardobessellp-11d.workers.dev/mcp).

### Is the FreshProof MCP server safe to use?

FreshProof scores 63 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 FreshProof MCP server expose?

FreshProof exposes 4 tools: freshproof_info, verify_proof, observe_url, verify_url. Their descriptions and schemas cost roughly 308 tokens of context every time the server is loaded.

### Does the FreshProof MCP server require authentication?

No. We connected to FreshProof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FreshProof MCP server still maintained?

FreshProof 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://freshproof.ricardobessellp-11d.workers.dev/mcp
- Repository: https://github.com/ricksporto/freshproof
- Changelog RSS feed: https://verifymcp.io/servers/ricksporto-freshproof/freshproof.xml
- Changelog JSON feed: https://verifymcp.io/servers/ricksporto-freshproof/freshproof.json
- HTML version of this page: https://verifymcp.io/servers/ricksporto-freshproof/freshproof