Publish HTML, Markdown, KV, JSON, and files to brewpage.app from AI assistants. No signup.
Nothing to run from here
LivePublicator is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Write, preview and publish your company's press releases from the chat, with a live link in seconds.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http livepublicator-mcp https://livepublicator.com/api/mcp
# 2 — ask your agent for something these tools do
# preview_press_release, get_account, create_release and 6 more
LivePublicator costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LIAll 1 server
livepublicator1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http livepublicator-mcp https://livepublicator.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 answe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_name | string | yes | The company the news is about. |
| company_website | string | yes | The company's website, e.g. acme.com. |
| headline | string | yes | One line, 10 to 200 characters. Name the company in it. |
| summary | string | yes | One sentence that sums up the news (40 to 300 characters). |
| body | string | yes | The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most. |
| key_facts | array | yes | 1 to 8 short facts, 5 to 200 characters each. |
| faq | array | no | Optional: up to 6 questions and answers. |
| 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. |
| contact_name | string | yes | Press contact's name, shown for journalists. |
| contact_title | string | yes | Press contact's role. |
| contact_email | string | yes | Press contact's email. |
| contact_phone | string | no | Optional press contact phone. |
| image_url | string | no | 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 own |
| image_is_ai | boolean | no | 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". |
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.
No parameter schema on file.
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 cont
| Parameter | Type | Required | Notes |
|---|---|---|---|
| company_name | string | no | The company the news is about. |
| company_website | string | no | The company's website, e.g. acme.com. |
| headline | string | yes | One line, 10 to 200 characters. Name the company in it. |
| summary | string | yes | One sentence that sums up the news (40 to 300 characters). |
| body | string | yes | The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most. |
| key_facts | array | yes | 1 to 8 short facts, 5 to 200 characters each. |
| faq | array | no | Optional: up to 6 questions and answers. |
| 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. |
| contact_name | string | yes | Press contact's name, shown for journalists. |
| contact_title | string | yes | Press contact's role. |
| contact_email | string | yes | Press contact's email. |
| contact_phone | string | no | Optional press contact phone. |
| image_url | string | no | 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 own |
| image_is_ai | boolean | no | 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_file | object | no | Optional: an image file the user attached in the chat. |
| client_authorized | boolean | no | Agencies: true confirms the client company agreed that you publish this release for it. |
| publish_at | string | no | Optional: when to go live, ISO 8601 (e.g. 2026-11-03T14:00:00Z), up to 60 days ahead. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| release_id | string | yes | The release id. |
| headline | string | no | One line, 10 to 200 characters. Name the company in it. |
| summary | string | no | One sentence that sums up the news (40 to 300 characters). |
| body | string | no | The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most. |
| key_facts | array | no | 1 to 8 short facts, 5 to 200 characters each. |
| faq | array | no | Optional: up to 6 questions and answers. |
| quote | string | no | A quote from a real person at the company. More quotes can go in the body. |
| quote_name | string | no | Full name of the person quoted. |
| quote_title | string | no | Role of the person quoted, e.g. Founder and CEO. |
| contact_name | string | no | Press contact's name, shown for journalists. |
| contact_title | string | no | Press contact's role. |
| contact_email | string | no | Press contact's email. |
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 optio
| Parameter | Type | Required | Notes |
|---|---|---|---|
| release_id | string | yes | The release id. |
| image_url | string | no | A public https URL of the image. |
| image_is_ai | boolean | no | true when the image was made with AI. The page then labels it "Illustration, created with AI". |
| image_file | object | no | A file the user attached in the chat. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| release_id | string | yes | The release id. |
| confirm | boolean | yes | true: the user saw the preview and said to publish. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| release_id | string | yes | The release id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many, newest first (default 10). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| release_id | string | yes | The release id. |
| headline | string | no | One line, 10 to 200 characters. Name the company in it. |
| summary | string | no | One sentence that sums up the news (40 to 300 characters). |
| body | string | no | The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most. |
| key_facts | array | no | 1 to 8 short facts, 5 to 200 characters each. |
| faq | array | no | Optional: up to 6 questions and answers. |
| quote | string | no | A quote from a real person at the company. More quotes can go in the body. |
| quote_name | string | no | Full name of the person quoted. |
| quote_title | string | no | Role of the person quoted, e.g. Founder and CEO. |
| contact_name | string | no | Press contact's name, shown for journalists. |
| contact_title | string | no | Press contact's role. |
| contact_email | string | no | Press contact's email. |
| image_is_ai | boolean | no | 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". |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install LivePublicator or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 2.0.3 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digesta449cc8d9f1199bb3874345220b5266c532d03c12fb69b9f44386f67bd508d68
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| preview_press_release | no tags | |
| get_account | no tags | |
| create_release | state-write | state-write: declares readOnlyHint: false |
| update_release | state-write | state-write: declares readOnlyHint: false |
| add_image | state-write | state-write: declares readOnlyHint: false |
| publish_release | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_release_status | no tags | |
| list_releases | no tags | |
| fix_live_release | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta449cc8d9f1199bb
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.3.
2.0.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish LivePublicator can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.