# ABOVO.co: Email-to-Web Publishing (remote · mcp.abovo.co)

Turn any email into a public web page: send it to POST@abovo.co. No login: your email is your login.

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

## Components

- remote · `mcp.abovo.co`: 71/100 (this document), [markdown](https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/api-mcp.md), [page](https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/api-mcp)
- mcpb · `abovo-mcp-server-1.1.1.mcpb`: 48/100, [markdown](https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/https-github-com-seanfenlon-abovo-mcp-server-releases-download-v1-1-1-abovo-mcp.md), [page](https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/https-github-com-seanfenlon-abovo-mcp-server-releases-download-v1-1-1-abovo-mcp)

## Channel facts

- Endpoint: `https://mcp.abovo.co/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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**: 80/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 40/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 205 tokens (~68/item across 3 items; 2 tools + 1 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**: 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 ABOVO.co: Email-to-Web Publishing MCP server?

ABOVO.co: Email-to-Web Publishing is a hosted endpoint at https://mcp.abovo.co/api/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 seanfenlon-abovo-mcp-server 'https://mcp.abovo.co/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "seanfenlon-abovo-mcp-server": {
      "url": "https://mcp.abovo.co/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "seanfenlon-abovo-mcp-server": {
      "type": "http",
      "url": "https://mcp.abovo.co/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.seanfenlon-abovo-mcp-server]
url = "https://mcp.abovo.co/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seanfenlon-abovo-mcp-server": {
      "type": "remote",
      "url": "https://mcp.abovo.co/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add seanfenlon-abovo-mcp-server --url 'https://mcp.abovo.co/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  seanfenlon-abovo-mcp-server:
    url: "https://mcp.abovo.co/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "seanfenlon-abovo-mcp-server": {
      "Transport": "http",
      "Url": "https://mcp.abovo.co/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add seanfenlon-abovo-mcp-server -t streamable-http -u 'https://mcp.abovo.co/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "seanfenlon-abovo-mcp-server": {
      "type": "http",
      "url": "https://mcp.abovo.co/api/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 71, +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-17 (score 70, +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-11-15 (score 69, +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-11-13 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 67)

First indexed and scored.

## MCP tools (2)

### `prepare_abovo_post` (~145 tokens)

Prepare a ready-to-send email that publishes a public web page on ABOVO.co. This tool sends nothing: you or your user send the email to POST@abovo.co (or a group address) from your own email account. No login, no API key.

Input parameters:

- `body` (string, required): Post content; becomes the email body.
- `format` (string): text (default) or html. Mailto links carry plain text only.
- `group` (string): Optional ABOVO group name; the email goes to {group}@abovo.co instead of POST@abovo.co.
- `subject` (string, required): Post title; becomes the email subject.

### `get_abovo_info` (~53 tokens)

Get information about ABOVO.co capabilities, URL formats, groups, or use cases.

Input parameters:

- `query` (string, required): Topic to return. Allowed values: capabilities, url_format, groups, use_cases, about.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/api-mcp#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 70
- 2026-11-16: 69
- 2026-11-15: 69
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 67

## Common questions

### What is the ABOVO.co: Email-to-Web Publishing MCP server?

ABOVO.co: Email-to-Web Publishing is an MCP server listed in the public MCP registry as io.github.seanfenlon/abovo-mcp-server. Turn any email into a public web page: send it to POST@abovo.co. No login: your email is your login. This page covers its hosted endpoint (https://mcp.abovo.co/api/mcp).

### Is the ABOVO.co: Email-to-Web Publishing MCP server safe to use?

ABOVO.co: Email-to-Web Publishing scores 71 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 ABOVO.co: Email-to-Web Publishing MCP server expose?

ABOVO.co: Email-to-Web Publishing exposes 2 tools: prepare_abovo_post, get_abovo_info. Their descriptions and schemas cost roughly 198 tokens of context every time the server is loaded.

### Does the ABOVO.co: Email-to-Web Publishing MCP server require authentication?

No. We connected to ABOVO.co: Email-to-Web Publishing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ABOVO.co: Email-to-Web Publishing MCP server still maintained?

ABOVO.co: Email-to-Web Publishing 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 ABOVO.co: Email-to-Web Publishing MCP server?

VerifyMCP ran 13 checks on ABOVO.co: Email-to-Web Publishing, 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://mcp.abovo.co/api/mcp
- Repository: https://github.com/seanfenlon/abovo-mcp-server
- Website: https://www.abovo.co/
- Changelog RSS feed: https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/seanfenlon-abovo-mcp-server/api-mcp
