# Postcard (remote · postcard.clawhard.com)

Check a link's share card on X, Facebook, LinkedIn: real image size, tag problems, fixed tags.

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

## Components

- remote · `postcard.clawhard.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-clawhard-postcard/postcard.md), [page](https://verifymcp.io/servers/com-clawhard-postcard/postcard)

## Channel facts

- Endpoint: `https://postcard.clawhard.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**: 63/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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1029 tokens (~257/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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 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.
  - Supports UI / widget rendering.

## Install

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

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

### Cursor

```json
{
  "mcpServers": {
    "com-clawhard-postcard": {
      "url": "https://postcard.clawhard.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-clawhard-postcard]
url = "https://postcard.clawhard.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-clawhard-postcard:
    url: "https://postcard.clawhard.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-clawhard-postcard": {
      "type": "http",
      "url": "https://postcard.clawhard.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-19 (score 70, +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-11-17 (score 69, +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-11-15 (score 68, +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-14 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (2)

### `postcard_check_link_preview` (~420 tokens)

Check the card a link shows when shared on X, Facebook, LinkedIn and chat apps

Use when the user asks how a link will look when shared, why a shared link shows no image or the wrong title, or wants a page checked before a launch post (signals: "link preview", "og:image not showing", "Twitter card", "X card", "social card", "share image", "unfurl", "Open Graph", "LinkedIn preview is blank", "after deploying the landing page"). Fetches the public page the way a link crawler does (following redirects, no JavaScript), reads the og: and twitter: tags with X's documented fallbacks (twitter:* then og:*, last twitter:card wins), downloads the og:image and twitter:image and reads their real pixel size, format and file size from the bytes, and checks robots.txt for Twitterbot and facebookexternalhit on the page and the image. Returns the card X, Facebook, LinkedIn and chat apps will build, every problem with severity and fix (relative or http image URL, image that is really an HTML page, SVG or AVIF, below X's 300x157 / Facebook's 200x200 / LinkedIn's 1200x627, over 5 MB, 2:1 crop of a square logo, tags added by JavaScript, tags past Facebook's first 1 MB, title over X's 70 characters, missing twitter:card, robots.txt blocks), and a paste-ready <meta> block. Rules come from the platforms' docs, with the check date. Example: {"url":"https://example.com/launch"}. Limits: public http/https pages on ports 80 and 443 (localhost and unpublished pages go through postcard_check_preview_tags); platforms cache cards (X for about 7 days), so a fixed page can still show the old card until rescraped; sites that serve different HTML to real crawlers by User-Agent can differ.

Input parameters:

- `url` (string, required): The page address people will share, for example "https://example.com/blog/launch".

### `postcard_check_preview_tags` (~365 tokens)

Check share-card tags in pasted HTML (before deploy, localhost, private pages)

Use when the share-card tags need checking in HTML that is not public yet: a page being built, a localhost or staging page, a template, or a <head> block the user pasted (signals: "check my meta tags", "are these og tags right", "before I deploy", "Next.js metadata", "index.html head"). Reads the og: and twitter: tags in the pasted HTML with X's documented fallbacks and returns the same result as postcard_check_link_preview: the card each platform will build, problems with fixes (missing og:image or twitter:card, relative image path, title over X's 70 characters, duplicates, name= instead of property=, tags in <body>, a JavaScript app shell with no tags) and a paste-ready <meta> block. The page is not fetched; with fetch_image true, a public absolute image URL is downloaded to read its real size, format and bytes. Example: {"html":"<head><meta property=\"og:title\" content=\"Launch\"><meta property=\"og:image\" content=\"/og.png\"></head>","url":"https://example.com/launch"}. Limits: robots.txt and redirects of the page are not checked (no fetch); without url, relative image paths cannot be resolved.

Input parameters:

- `fetch_image` (boolean): true to download the public og:image / twitter:image and read its real pixel size, format and file size. Default false (nothing is fetched).
- `html` (string, required): The page HTML, or at least its <head> with the meta tags (up to 400,000 characters).
- `url` (string): Optional address the page will be served at, used to turn relative image paths into full URLs and to compare og:url.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Postcard MCP server?

Postcard is an MCP server listed in the public MCP registry as com.clawhard/postcard. Check a link's share card on X, Facebook, LinkedIn: real image size, tag problems, fixed tags. This page covers its hosted endpoint (https://postcard.clawhard.com/mcp).

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

Postcard scores 70 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 Postcard MCP server expose?

Postcard exposes 2 tools: postcard_check_link_preview, postcard_check_preview_tags. Their descriptions and schemas cost roughly 785 tokens of context every time the server is loaded.

### Does the Postcard MCP server require authentication?

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

### Is the Postcard MCP server still maintained?

Postcard 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 Postcard MCP server?

VerifyMCP ran 14 checks on Postcard, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://postcard.clawhard.com/mcp
- Website: https://postcard.clawhard.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-clawhard-postcard/postcard.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-clawhard-postcard/postcard/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-clawhard-postcard/postcard.json
- HTML version of this page: https://verifymcp.io/servers/com-clawhard-postcard/postcard
