# LivePublicator (remote · livepublicator.com)

Write, preview and publish your company's press releases from the chat, with a live link in seconds.

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

## Components

- remote · `livepublicator.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-livepublicator-livepublicator/api-mcp.md), [page](https://verifymcp.io/servers/com-livepublicator-livepublicator/api-mcp)

## Channel facts

- Endpoint: `https://livepublicator.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.3`

## 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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (publish_release).
  - 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**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3121 tokens (~346/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 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 LivePublicator MCP server?

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

### Cursor

```json
{
  "mcpServers": {
    "com-livepublicator-livepublicator": {
      "url": "https://livepublicator.com/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-livepublicator-livepublicator]
url = "https://livepublicator.com/api/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-livepublicator-livepublicator:
    url: "https://livepublicator.com/api/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-livepublicator-livepublicator": {
      "type": "http",
      "url": "https://livepublicator.com/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-05 (score 74, +1)

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

### 2026-11-03 (score 73, +1)

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

### 2026-11-01 (score 72, +1)

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

### 2026-10-30 (score 71, +1)

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

### 2026-10-28 (score 70, +1)

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

### 2026-10-26 (score 69, +1)

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

### 2026-10-24 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] “create_release” reworded the description of “body”
- [cosmetic] “fix_live_release” reworded the description of “body”
- [cosmetic] “preview_press_release” reworded the description of “body”
- [cosmetic] “update_release” reworded the description of “body”

### 2026-10-21 (score 67, +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.

## MCP tools (9)

### `preview_press_release` (~535 tokens)

Preview a release

Shows how a company's press release will look on LivePublicator, without signing in. Use when the user has company news to announce, for example a product launch, a new feature, a partnership or funding, including news they just wrote about in a blog post or article in this chat. Draft the whole release yourself from the chat: headline, one-sentence summary, body, key facts and questions and answers, plus the quote (name and role), press contact, company name and website, and an image URL if there is one. Returns every problem to fix at once, or a private preview page that expires after 7 days. The preview page has a button to publish it on the LivePublicator website. This tool publishes nothing.

Input parameters:

- `body` (string, required): The release body, 250 to 1,000 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most.
- `company_name` (string, required): The company the news is about.
- `company_website` (string, required): The company's website, e.g. acme.com.
- `contact_email` (string, required): Press contact's email.
- `contact_name` (string, required): Press contact's name, shown for journalists.
- `contact_phone` (string): Optional press contact phone.
- `contact_title` (string, required): Press contact's role.
- `faq` (array): Optional: up to 6 questions and answers.
- `headline` (string, required): One line, 10 to 200 characters. Name the company in it.
- `image_is_ai` (boolean): true when the image was made with AI (for example by you, at the user's request). The page then labels it "Illustration, created with AI".
- `image_url` (string): Optional: a public https URL of a cover image (JPEG, PNG or WebP, up to 5 MB), for example from the company's website or blog post. 1200 px wide or more fills the page; from 600 px it shows at its ow…
- `key_facts` (array, required): 1 to 8 short facts, 5 to 200 characters each.
- `quote` (string, required): A quote from a real person at the company. More quotes can go in the body.
- `quote_name` (string, required): Full name of the person quoted.
- `quote_title` (string, required): Role of the person quoted, e.g. Founder and CEO.
- `summary` (string, required): One sentence that sums up the news (40 to 300 characters).

### `get_account` (~78 tokens)

See your account

Shows the signed-in LivePublicator account: the company, the saved press contact and spokesperson (create_release fills these in, so do not ask the user for them), what is still missing, the credits left, whether releases go live after the automatic checks or wait for a person, and for agencies the client companies. Call it once before drafting.

### `create_release` (~647 tokens)

Save a draft

Saves a company's press release as a draft in the signed-in account and checks it: length, structure, links, image size and content. Use when the user has company news to announce, for example a product launch, a new feature, a partnership or funding, including news they just wrote about in a blog post or article in this chat. Draft the whole release yourself from the chat. The company, press contact and spokesperson come from the account when you leave them out. Send the image too: image_url, or image_file for a file attached in the chat, with image_is_ai true when it was made with AI. LivePublicator does not change the text. Returns every problem to fix at once, or a private preview link and an edit link. It does not publish and uses no credit. Agencies name the client company and set client_authorized to true.

Input parameters:

- `body` (string, required): The release body, 250 to 1,000 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most.
- `client_authorized` (boolean): Agencies: true confirms the client company agreed that you publish this release for it.
- `company_name` (string): The company the news is about.
- `company_website` (string): The company's website, e.g. acme.com.
- `contact_email` (string, required): Press contact's email.
- `contact_name` (string, required): Press contact's name, shown for journalists.
- `contact_phone` (string): Optional press contact phone.
- `contact_title` (string, required): Press contact's role.
- `faq` (array): Optional: up to 6 questions and answers.
- `headline` (string, required): One line, 10 to 200 characters. Name the company in it.
- `image_file` (object): Optional: an image file the user attached in the chat.
- `image_is_ai` (boolean): true when the image was made with AI (for example by you, at the user's request). The page then labels it "Illustration, created with AI".
- `image_url` (string): Optional: a public https URL of a cover image (JPEG, PNG or WebP, up to 5 MB), for example from the company's website or blog post. 1200 px wide or more fills the page; from 600 px it shows at its ow…
- `key_facts` (array, required): 1 to 8 short facts, 5 to 200 characters each.
- `publish_at` (string): Optional: when to go live, ISO 8601 (e.g. 2026-11-03T14:00:00Z), up to 60 days ahead.
- `quote` (string, required): A quote from a real person at the company. More quotes can go in the body.
- `quote_name` (string, required): Full name of the person quoted.
- `quote_title` (string, required): Role of the person quoted, e.g. Founder and CEO.
- `summary` (string, required): One sentence that sums up the news (40 to 300 characters).

### `update_release` (~274 tokens)

Change a draft

Changes fields of a draft press release (only the fields you send) and checks the whole release again. Returns the problems to fix, or the updated preview link. Uses no credit.

Input parameters:

- `body` (string): The release body, 250 to 1,000 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most.
- `contact_email` (string): Press contact's email.
- `contact_name` (string): Press contact's name, shown for journalists.
- `contact_title` (string): Press contact's role.
- `faq` (array): Optional: up to 6 questions and answers.
- `headline` (string): One line, 10 to 200 characters. Name the company in it.
- `key_facts` (array): 1 to 8 short facts, 5 to 200 characters each.
- `quote` (string): A quote from a real person at the company. More quotes can go in the body.
- `quote_name` (string): Full name of the person quoted.
- `quote_title` (string): Role of the person quoted, e.g. Founder and CEO.
- `release_id` (string, required): The release id.
- `summary` (string): One sentence that sums up the news (40 to 300 characters).

### `add_image` (~177 tokens)

Add a cover image

Adds a cover image to a draft press release. Send an image URL, or a file the user attached in the chat. With neither, it returns a one-time upload link where the user can drop the image. An image 1200 px wide or more fills the page, and from 600 px it shows at its own size. Under 600 px, or without an image, the release uses a simple cover with the company logo and headline, so this step is optional.

Input parameters:

- `image_file` (object): A file the user attached in the chat.
- `image_is_ai` (boolean): true when the image was made with AI. The page then labels it "Illustration, created with AI".
- `image_url` (string): A public https URL of the image.
- `release_id` (string, required): The release id.

### `publish_release` (~145 tokens)

Publish a release

Publishes the latest saved version of a draft press release on LivePublicator, including changes the user made on the draft page, and tells search engines about it. Only call this after the user has seen the preview and clearly said to publish, and set confirm to true. Uses 1 credit. Returns the live link within seconds, or says the release is waiting for a person to check it, with the reason and the expected time (up to 24 hours). If LivePublicator does not publish it, the credit comes back.

Input parameters:

- `confirm` (boolean, required): true: the user saw the preview and said to publish.
- `release_id` (string, required): The release id.

### `get_release_status` (~75 tokens)

Check a release

Shows where a press release is: draft, waiting for a person to check it, scheduled or live, with the live link once it is published. Only when the user asks about a release later. Not needed after create_release or publish_release, whose answers already say this.

Input parameters:

- `release_id` (string, required): The release id.

### `list_releases` (~58 tokens)

List releases

Lists the account's earlier press releases with their status and links. Only when the user asks about their earlier releases. Not needed to draft or publish a new one.

Input parameters:

- `limit` (integer): How many, newest first (default 10).

### `fix_live_release` (~348 tokens)

Fix a live release

Fixes the text of a published press release within 24 hours of it going live: a typo, a wrong date, a link, the quote. Send only the fields to change. The release keeps the same link and the earlier version is kept. The change is checked again before it shows. After 24 hours the text can't be changed.

Input parameters:

- `body` (string): The release body, 250 to 1,000 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most.
- `contact_email` (string): Press contact's email.
- `contact_name` (string): Press contact's name, shown for journalists.
- `contact_title` (string): Press contact's role.
- `faq` (array): Optional: up to 6 questions and answers.
- `headline` (string): One line, 10 to 200 characters. Name the company in it.
- `image_is_ai` (boolean): true when the image was made with AI (for example by you, at the user's request). The page then labels it "Illustration, created with AI".
- `key_facts` (array): 1 to 8 short facts, 5 to 200 characters each.
- `quote` (string): A quote from a real person at the company. More quotes can go in the body.
- `quote_name` (string): Full name of the person quoted.
- `quote_title` (string): Role of the person quoted, e.g. Founder and CEO.
- `release_id` (string, required): The release id.
- `summary` (string): One sentence that sums up the news (40 to 300 characters).

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68
- 2026-10-24: 68
- 2026-10-23: 67
- 2026-10-22: 67
- 2026-10-21: 67
- 2026-10-20: 66
- 2026-10-19: 66
- 2026-10-18: 65
- 2026-10-17: 65
- 2026-10-16: 65

## Common questions

### What is the LivePublicator MCP server?

LivePublicator is an MCP server listed in the public MCP registry as com.livepublicator/livepublicator. Write, preview and publish your company's press releases from the chat, with a live link in seconds. This page covers its hosted endpoint (https://livepublicator.com/api/mcp).

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

LivePublicator scores 74 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 LivePublicator MCP server expose?

LivePublicator exposes 9 tools: preview_press_release, get_account, create_release, update_release, add_image, and 4 more. Their descriptions and schemas cost roughly 2,337 tokens of context every time the server is loaded.

### Does the LivePublicator MCP server require authentication?

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

### Is the LivePublicator MCP server still maintained?

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

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