# Lovable Release Ripple Roadmap Logpulse MCP server

Source: https://glimind.com/server/mcp-registry%2Fapp.lovable.release-ripple-roadmap%2Flogpulse
Registry id: `mcp-registry/app.lovable.release-ripple-roadmap/logpulse`
Status: live (checked 2026-11-22T16:47:14.356Z)

## Verdict

Lovable Release Ripple Roadmap Logpulse MCP server answered 99.99% of Glimind's liveness checks over 30 days, better than 43% of MCP servers, with 2341 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (90/100) across 13 tools, costing an agent about 4,759 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.99% | 43% of MCP servers |
| Median handshake latency | 2341 ms | 1% of MCP servers |
| p95 handshake latency | 3161 ms | — |
| Checks in 30 days | 4,993 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 0 min | — |
| Agent-readiness score | 90/100 (A) | 60% of MCP servers |
| Tools | 13 | — |
| Tool-list size for an agent | ~4,759 tokens | 30% of MCP servers |
| Days observed | 22 | — |

## Install

```json
{
  "mcpServers": {
    "lovable-release-ripple-roadmap-logpulse-": {
      "type": "http",
      "url": "https://release-ripple-roadmap.lovable.app/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http lovable-release-ripple-roadmap-logpulse- https://release-ripple-roadmap.lovable.app/mcp
```

## Tools (13)

- `commits_to_changelog`: Turn git log output or commit messages into a Keep a Changelog 2.0.0 section (Added, Changed, Deprecated, Removed, Fixed, Security) with breaking changes flagge
- `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
- `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, 
- `generate_release_notes`: Write release notes from a public GitHub repository's commits and merged pull requests: since the last tag by default, between two tags (from/to), or between tw
- `get_changelog`: Get a changelog's name, repository, packages, latest version and feed links.
- `get_release`: Get one release by version (2.0.0 or v2.0.0) or URL slug, with full notes, breaking changes and deprecations.
- `get_roadmap`: Get the public roadmap: items under review, planned, in progress and shipped, with vote counts.
- `github_release_notes`: Write the release notes for a release or tag of a public GitHub repository: compares two of its releases or plain Git tags (default: the latest release vs the o
- `list_releases`: List published releases, newest first, with versions, breaking changes, migration steps and deprecations.
- `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 LogP
- `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 
- `search_changelogs`: Find a public LogPulse changelog by package name, repository, product name or slug. Returns slugs to use with the other tools.
- `validate_changelog`: Check a CHANGELOG.md against Keep a Changelog 2.0.0: version headings, YYYY-MM-DD dates, newest-first order, the six types of change, breaking-change markers, U

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
