LogPulse MCP server

• Registry nameapp.lovable.release-ripple-roadmap/logpulseverified in the MCP registry

The registry name sits under release-ripple-roadmap.lovable.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-30
• Tools9
• Server calls itselflogpulse
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 1232 ms.

• Its tools do every use case we checked: publish release notes with breaking changes and migration steps; let coding agents answer what changed between two versions.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer2668 ms
• Space in an agent's context≈ 2,412 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_changelogs

  Find a public LogPulse changelog by package name, repository, product name or slug. Returns slugs to use with the other tools.

• get_changelog

  Get a changelog's name, repository, packages, latest version and feed links.

• list_releases

  List published releases, newest first, with versions, breaking changes, migration steps and deprecations.

• get_release

  Get one release by version (2.0.0 or v2.0.0) or URL slug, with full notes, breaking changes and deprecations.

• compare_versions

  Answer “what changed between two versions, and what do I need to change?”: breaking changes with migration steps, deprecations and every release after `from` up to `to`.

• get_roadmap

  Get the public roadmap: items under review, planned, in progress and shipped, with vote counts.

• convert_changelog

  Turn any project's CHANGELOG.md text, or a GitHub release, releases page, repository or changelog file URL, into a machine-readable changelog: versions, dates, breaking changes with migration steps, and deprecations. Works for projects…

• publish_release

  Publish a release note to your LogPulse changelog right after shipping — with version, breaking changes, migration steps and deprecations. Needs a LogPulse API key with the “Publish releases” permission, sent as the Authorization header.

• post_roadmap_update

  Add an item to your LogPulse roadmap, or update one by id — move it to in progress or shipped, change its ETA, or link the release that shipped it. Needs a LogPulse API key with the “Update roadmap” permission, sent as the Authorization…