LivePublicator
REMOTE · LIVEPUBLICATOR.COM
Write, preview and publish your company's press releases from the chat, with a live link in seconds.
Available components
Last scanned (6 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (publish_release). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- “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” cosmetic
- 21 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://livepublicator.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=livepublicator.com | CN=YE1,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 607c1f51339f708b501b81b44bc511c5e43 |
| SANs: *.livepublicator.com, livepublicator.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of livepublicator.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| livepublicator.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), usb=(), serial=(), hid=(), bluetooth=(), midi=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://livepublicator.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://livepublicator.com/api/mcp | HTTPS enforced | 301 | https://livepublicator.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_image Add a cover image ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The release id. |
No output schema declared.
No examples provided.
create_release Save a draft ~647
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | 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 | yes | Press contact's email. |
| contact_name | string | yes | Press contact's name, shown for journalists. |
| contact_phone | string | – | Optional press contact phone. |
| contact_title | string | yes | Press contact's role. |
| faq | array | – | Optional: up to 6 questions and answers. |
| headline | string | yes | 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 | yes | 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 | yes | A quote from a real person at the company. More quotes can go in the body. |
| quote_name | string | yes | Full name of the person quoted. |
| quote_title | string | yes | Role of the person quoted, e.g. Founder and CEO. |
| summary | string | yes | One sentence that sums up the news (40 to 300 characters). |
No output schema declared.
No examples provided.
fix_live_release Fix a live release ~348
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The release id. |
| summary | string | – | One sentence that sums up the news (40 to 300 characters). |
No output schema declared.
No examples provided.
get_account See your account ~78
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_release_status Check a release ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| release_id | string | yes | The release id. |
No output schema declared.
No examples provided.
list_releases List releases ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many, newest first (default 10). |
No output schema declared.
No examples provided.
preview_press_release Preview a release ~535
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | 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 | yes | The company the news is about. |
| company_website | string | yes | The company's website, e.g. acme.com. |
| contact_email | string | yes | Press contact's email. |
| contact_name | string | yes | Press contact's name, shown for journalists. |
| contact_phone | string | – | Optional press contact phone. |
| contact_title | string | yes | Press contact's role. |
| faq | array | – | Optional: up to 6 questions and answers. |
| headline | string | yes | 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 | yes | 1 to 8 short facts, 5 to 200 characters each. |
| quote | string | yes | A quote from a real person at the company. More quotes can go in the body. |
| quote_name | string | yes | Full name of the person quoted. |
| quote_title | string | yes | Role of the person quoted, e.g. Founder and CEO. |
| summary | string | yes | One sentence that sums up the news (40 to 300 characters). |
No output schema declared.
No examples provided.
publish_release Publish a release ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | true: the user saw the preview and said to publish. |
| release_id | string | yes | The release id. |
No output schema declared.
No examples provided.
update_release Change a draft ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The release id. |
| summary | string | – | One sentence that sums up the news (40 to 300 characters). |
No output schema declared.
No examples provided.
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.
remote · livepublicator.com
claude mcp add --transport http com-livepublicator-livepublicator 'https://livepublicator.com/api/mcp'
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.