# PageRoast (remote · lab.dividendsolo.com)

AI landing page roast: score /100, 5-second test, top 3 conversion problems quoted from any URL.

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

## Components

- remote · `lab.dividendsolo.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-dividendsolo-lab-pageroast/lab.md), [page](https://verifymcp.io/servers/com-dividendsolo-lab-pageroast/lab)

## Channel facts

- Endpoint: `https://lab.dividendsolo.com/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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 128 tokens (~128/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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 2 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 PageRoast MCP server?

PageRoast is a hosted endpoint at https://lab.dividendsolo.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.

### Claude

```bash
claude mcp add --transport http com-dividendsolo-lab-pageroast 'https://lab.dividendsolo.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-dividendsolo-lab-pageroast": {
      "url": "https://lab.dividendsolo.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dividendsolo-lab-pageroast": {
      "type": "http",
      "url": "https://lab.dividendsolo.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-dividendsolo-lab-pageroast]
url = "https://lab.dividendsolo.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dividendsolo-lab-pageroast": {
      "type": "remote",
      "url": "https://lab.dividendsolo.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dividendsolo-lab-pageroast --url 'https://lab.dividendsolo.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dividendsolo-lab-pageroast:
    url: "https://lab.dividendsolo.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-dividendsolo-lab-pageroast": {
      "Transport": "http",
      "Url": "https://lab.dividendsolo.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dividendsolo-lab-pageroast -t streamable-http -u 'https://lab.dividendsolo.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-dividendsolo-lab-pageroast": {
      "type": "http",
      "url": "https://lab.dividendsolo.com/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-11-04 (score 75, +1)

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

### 2026-11-02 (score 74, +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-10-31 (score 73, +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-10-29 (score 72, +1)

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

### 2026-10-28 (score 71, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-10-27 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 66)

First indexed and scored.

## MCP tools (1)

### `roast_landing_page` (~108 tokens)

Free AI conversion review of a public landing page URL: score /100, 5-second-test first impression, top 3 problems quoted from the page, and a headline rewrite. Returns a link to the full report page (where an optional $9 full teardown can be bought). Takes ~20s. Limit 5 free roasts per day per IP.

Input parameters:

- `url` (string, required): Public http(s) URL of the landing page to review, e.g. https://example.com

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 66
- 2026-10-26: 66

## Common questions

### What is the PageRoast MCP server?

PageRoast is an MCP server listed in the public MCP registry as com.dividendsolo.lab/pageroast. AI landing page roast: score /100, 5-second test, top 3 conversion problems quoted from any URL. This page covers its hosted endpoint (https://lab.dividendsolo.com/mcp).

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

PageRoast scores 75 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 PageRoast MCP server expose?

PageRoast exposes 1 tool: roast_landing_page. Their descriptions and schemas cost roughly 108 tokens of context every time the server is loaded.

### Does the PageRoast MCP server require authentication?

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

### Is the PageRoast MCP server still maintained?

PageRoast is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the PageRoast MCP server?

VerifyMCP ran 13 checks on PageRoast, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://lab.dividendsolo.com/mcp
- Website: https://lab.dividendsolo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dividendsolo-lab-pageroast/lab.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dividendsolo-lab-pageroast/lab/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-dividendsolo-lab-pageroast/lab.json
- HTML version of this page: https://verifymcp.io/servers/com-dividendsolo-lab-pageroast/lab