_ registry / mcp streamable-http · checked 58m ago

LivePublicator

https://livepublicator.com

Registry code: 8502432343abb41c

api record

LivePublicator publishes a company's own news (press releases, announcements, product launches, company news) as a page in its newsroom, made to be read by people and by AI search, with a live link in seconds.

How to use it:

endpoint
https://livepublicator.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is LivePublicator live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is LivePublicator free to use?
No — it asks for a key or a login before it will serve.
What tools does LivePublicator have?
9 tools: list_releases, get_account, get_release_status, publish_release, preview_press_release, create_release, update_release, add_image, ….
Is LivePublicator safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
398ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
9 auth-required 9 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_releases auth-required 58m ago

    Lists the account's latest press releases and announcements with their status and links.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "How many, newest first (default 10)."
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • get_account auth-required 58m ago

    Shows the signed-in LivePublicator account: company or agency, the credits left for publishing press releases, whether releases go live after the automatic checks or wait for a person first, and for agencies the client companies.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_release_status auth-required 58m ago

    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. Useful to check back on a release that was waiting for review.

    mcp-tool

    {
  "type": "object",
  "required": [
    "release_id"
  ],
  "properties": {
    "release_id": {
      "type": "string",
      "description": "The release id."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • publish_release auth-required never probed

    Publishes a draft press release on LivePublicator 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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "release_id",
    "confirm"
  ],
  "properties": {
    "confirm": {
      "type": "boolean",
      "description": "true: the user saw the preview and said to publish."
    },
    "release_id": {
      "type": "string",
      "description": "The release id."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • preview_press_release auth-required never probed

    Shows how a company's press release or news announcement will look on LivePublicator, without signing in. Send the finished release: headline, one-sentence summary, body, key facts, a quote with the person's 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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "company_name",
    "company_website",
    "headline",
    "summary",
    "body",
    "key_facts",
    "quote",
    "quote_name",
    "quote_title",
    "contact_name",
    "contact_title",
    "contact_email"
  ],
  "properties": {
    "faq": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "question",
          "answer"
        ],
        "properties": {
          "answer": {
            "type": "string"
          },
          "question": {
            "type": "string"
          }
        }
      },
      "description": "Optional: up to 6 questions and answers."
    },
    "body": {
      "type": "string",
      "description": "The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most."
    },
    "quote": {
      "type": "string",
      "description": "A quote from a real person at the company. More quotes can go in the body."
    },
    "summary": {
      "type": "string",
      "description": "One sentence that sums up the news (40 to 300 characters)."
    },
    "headline": {
      "type": "string",
      "description": "One line, 10 to 200 characters. Name the company in it."
    },
    "image_url": {
      "type": "string",
      "description": "Optional: a public https URL of a landscape cover image, at least 1200 px wide (JPEG, PNG or WebP, up to 5 MB)."
    },
    "key_facts": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "1 to 8 short facts, 5 to 200 characters each."
    },
    "quote_name": {
      "type": "string",
      "description": "Full name of the person quoted."
    },
    "quote_title": {
      "type": "string",
      "description": "Role of the person quoted, e.g. Founder and CEO."
    },
    "company_name": {
      "type": "string",
      "description": "The company the news is about."
    },
    "contact_name": {
      "type": "string",
      "description": "Press contact's name, shown for journalists."
    },
    "contact_email": {
      "type": "string",
      "description": "Press contact's email."
    },
    "contact_phone": {
      "type": "string",
      "description": "Optional press contact phone."
    },
    "contact_title": {
      "type": "string",
      "description": "Press contact's role."
    },
    "company_website": {
      "type": "string",
      "description": "The company's website, e.g. acme.com."
    }
  },
  "additionalProperties": false
}
    arguments 98 lines
  • create_release auth-required never probed

    Saves a press release, launch announcement or other company news as a draft in the signed-in account and checks it: length, structure, links, image size and content. Send the finished release. LivePublicator does not write or change the text. Returns every problem to fix at once, or a private preview link. It does not publish and uses no credit. Company accounts can leave out the company name and website. Agencies name the client company and set client_authorized to true.

    mcp-tool

    {
  "type": "object",
  "required": [
    "headline",
    "summary",
    "body",
    "key_facts",
    "quote",
    "quote_name",
    "quote_title",
    "contact_name",
    "contact_title",
    "contact_email"
  ],
  "properties": {
    "faq": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "question",
          "answer"
        ],
        "properties": {
          "answer": {
            "type": "string"
          },
          "question": {
            "type": "string"
          }
        }
      },
      "description": "Optional: up to 6 questions and answers."
    },
    "body": {
      "type": "string",
      "description": "The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most."
    },
    "quote": {
      "type": "string",
      "description": "A quote from a real person at the company. More quotes can go in the body."
    },
    "summary": {
      "type": "string",
      "description": "One sentence that sums up the news (40 to 300 characters)."
    },
    "headline": {
      "type": "string",
      "description": "One line, 10 to 200 characters. Name the company in it."
    },
    "image_url": {
      "type": "string",
      "description": "Optional: a public https URL of a landscape cover image, at least 1200 px wide (JPEG, PNG or WebP, up to 5 MB)."
    },
    "key_facts": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "1 to 8 short facts, 5 to 200 characters each."
    },
    "publish_at": {
      "type": "string",
      "description": "Optional: when to go live, ISO 8601 (e.g. 2026-11-03T14:00:00Z), up to 60 days ahead."
    },
    "quote_name": {
      "type": "string",
      "description": "Full name of the person quoted."
    },
    "quote_title": {
      "type": "string",
      "description": "Role of the person quoted, e.g. Founder and CEO."
    },
    "company_name": {
      "type": "string",
      "description": "The company the news is about."
    },
    "contact_name": {
      "type": "string",
      "description": "Press contact's name, shown for journalists."
    },
    "contact_email": {
      "type": "string",
      "description": "Press contact's email."
    },
    "contact_phone": {
      "type": "string",
      "description": "Optional press contact phone."
    },
    "contact_title": {
      "type": "string",
      "description": "Press contact's role."
    },
    "company_website": {
      "type": "string",
      "description": "The company's website, e.g. acme.com."
    },
    "client_authorized": {
      "type": "boolean",
      "description": "Agencies: true confirms the client company agreed that you publish this release for it."
    }
  },
  "additionalProperties": false
}
    arguments 104 lines
  • update_release auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "release_id"
  ],
  "properties": {
    "faq": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "question",
          "answer"
        ],
        "properties": {
          "answer": {
            "type": "string"
          },
          "question": {
            "type": "string"
          }
        }
      },
      "description": "Optional: up to 6 questions and answers."
    },
    "body": {
      "type": "string",
      "description": "The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most."
    },
    "quote": {
      "type": "string",
      "description": "A quote from a real person at the company. More quotes can go in the body."
    },
    "summary": {
      "type": "string",
      "description": "One sentence that sums up the news (40 to 300 characters)."
    },
    "headline": {
      "type": "string",
      "description": "One line, 10 to 200 characters. Name the company in it."
    },
    "key_facts": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "1 to 8 short facts, 5 to 200 characters each."
    },
    "quote_name": {
      "type": "string",
      "description": "Full name of the person quoted."
    },
    "release_id": {
      "type": "string",
      "description": "The release id."
    },
    "quote_title": {
      "type": "string",
      "description": "Role of the person quoted, e.g. Founder and CEO."
    },
    "contact_name": {
      "type": "string",
      "description": "Press contact's name, shown for journalists."
    },
    "contact_email": {
      "type": "string",
      "description": "Press contact's email."
    },
    "contact_title": {
      "type": "string",
      "description": "Press contact's role."
    }
  },
  "additionalProperties": false
}
    arguments 75 lines
  • add_image auth-required never probed

    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. The image must be landscape and at least 1200 px wide. Without an image, the release uses a simple cover with the company logo and headline, so this step is optional.

    mcp-tool

    {
  "type": "object",
  "required": [
    "release_id"
  ],
  "properties": {
    "image_url": {
      "type": "string",
      "description": "A public https URL of the image."
    },
    "image_file": {
      "type": "object",
      "required": [
        "download_url"
      ],
      "properties": {
        "file_id": {
          "type": "string"
        },
        "download_url": {
          "type": "string"
        }
      },
      "description": "A file the user attached in the chat."
    },
    "release_id": {
      "type": "string",
      "description": "The release id."
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • fix_live_release auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "release_id"
  ],
  "properties": {
    "faq": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "question",
          "answer"
        ],
        "properties": {
          "answer": {
            "type": "string"
          },
          "question": {
            "type": "string"
          }
        }
      },
      "description": "Optional: up to 6 questions and answers."
    },
    "body": {
      "type": "string",
      "description": "The release body, 150 to 800 words, as text, Markdown or HTML. Do not repeat the headline. 3 links at most."
    },
    "quote": {
      "type": "string",
      "description": "A quote from a real person at the company. More quotes can go in the body."
    },
    "summary": {
      "type": "string",
      "description": "One sentence that sums up the news (40 to 300 characters)."
    },
    "headline": {
      "type": "string",
      "description": "One line, 10 to 200 characters. Name the company in it."
    },
    "key_facts": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "1 to 8 short facts, 5 to 200 characters each."
    },
    "quote_name": {
      "type": "string",
      "description": "Full name of the person quoted."
    },
    "release_id": {
      "type": "string",
      "description": "The release id."
    },
    "quote_title": {
      "type": "string",
      "description": "Role of the person quoted, e.g. Founder and CEO."
    },
    "contact_name": {
      "type": "string",
      "description": "Press contact's name, shown for journalists."
    },
    "contact_email": {
      "type": "string",
      "description": "Press contact's email."
    },
    "contact_title": {
      "type": "string",
      "description": "Press contact's role."
    }
  },
  "additionalProperties": false
}
    arguments 75 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8502432343abb41c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8502432343abb41c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8502432343abb41c/badge.svg)](https://brick.blue/agent/8502432343abb41c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.