# readm3 (remote · readm3.com)

Read any URL as markdown (readm3.com)

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

## Components

- remote · `readm3.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-profullstack-readm3/readm3.md), [page](https://verifymcp.io/servers/com-profullstack-readm3/readm3)

## Channel facts

- Endpoint: `https://readm3.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-21.

- **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**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 163 tokens (~163/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% 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 readm3 MCP server?

readm3 is a hosted endpoint at https://readm3.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-profullstack-readm3 'https://readm3.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-profullstack-readm3": {
      "url": "https://readm3.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-profullstack-readm3": {
      "type": "http",
      "url": "https://readm3.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-profullstack-readm3]
url = "https://readm3.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-profullstack-readm3 --url 'https://readm3.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-profullstack-readm3:
    url: "https://readm3.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-profullstack-readm3": {
      "Transport": "http",
      "Url": "https://readm3.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-profullstack-readm3 -t streamable-http -u 'https://readm3.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-profullstack-readm3": {
      "type": "http",
      "url": "https://readm3.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-20 (score 73, +1)

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

### 2026-11-19 (score 72, +16)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-18 (score 56, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-16 (score 70, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.10 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-14 (score 70, +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-11-13 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 69, +65)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 50
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-11-11 (score 4)

First indexed and scored.

## MCP tools (1)

### `read_url` (~140 tokens)

Read a document at a URL

Fetch a document by URL and return its text: PDFs (arXiv papers, reports), web pages, Word, Excel, PowerPoint, OpenDocument, EPUB, Markdown and other text. Use it to summarize, quote or answer questions about a link. Returns title, kind, page count, character count, whether the text was truncated, and the text. maxChars caps the text (default 100,000, up to 400,000). No account needed; a free hourly allowance, then an x402 reader pass.

Input parameters:

- `maxChars` (integer)
- `url` (string, required): An http(s) URL on the public internet.

## Diagnostics

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

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 56
- 2026-11-17: 70
- 2026-11-16: 70
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 69
- 2026-11-12: 69
- 2026-11-11: 4

## Common questions

### What is the readm3 MCP server?

readm3 is an MCP server listed in the public MCP registry as com.profullstack/readm3. Read any URL as markdown (readm3.com). This page covers its hosted endpoint (https://readm3.com/mcp).

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

readm3 scores 73 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 readm3 MCP server expose?

readm3 exposes 1 tool: read_url. Their descriptions and schemas cost roughly 140 tokens of context every time the server is loaded.

### Does the readm3 MCP server require authentication?

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

### Is the readm3 MCP server still maintained?

readm3 is still listed as active in the MCP registry. We last reached this channel on 21 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 readm3 MCP server?

VerifyMCP ran 13 checks on readm3, 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://readm3.com/mcp
- Website: https://readm3.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-profullstack-readm3/readm3.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-profullstack-readm3/readm3/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-profullstack-readm3/readm3.json
- HTML version of this page: https://verifymcp.io/servers/com-profullstack-readm3/readm3
