# LogPulse (remote · release-ripple-roadmap.lovable.app)

Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `release-ripple-roadmap.lovable.app`: 75/100 (this document), [markdown](https://verifymcp.io/servers/app-lovable-release-ripple-roadmap-logpulse/release-ripple-roadmap.md), [page](https://verifymcp.io/servers/app-lovable-release-ripple-roadmap-logpulse/release-ripple-roadmap)

## Channel facts

- Endpoint: `https://release-ripple-roadmap.lovable.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1428 tokens (~158/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the LogPulse MCP server?

LogPulse is a hosted endpoint at https://release-ripple-roadmap.lovable.app/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.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.app-lovable-release-ripple-roadmap-logpulse]
url = "https://release-ripple-roadmap.lovable.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-lovable-release-ripple-roadmap-logpulse": {
      "type": "remote",
      "url": "https://release-ripple-roadmap.lovable.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-lovable-release-ripple-roadmap-logpulse --url 'https://release-ripple-roadmap.lovable.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-lovable-release-ripple-roadmap-logpulse:
    url: "https://release-ripple-roadmap.lovable.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-lovable-release-ripple-roadmap-logpulse": {
      "Transport": "http",
      "Url": "https://release-ripple-roadmap.lovable.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-lovable-release-ripple-roadmap-logpulse -t streamable-http -u 'https://release-ripple-roadmap.lovable.app/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 75, +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.

### 2026-11-02 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 72)

First indexed and scored.

## MCP tools (9)

### `search_changelogs` (~81 tokens)

Search changelogs

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

Input parameters:

- `limit` (integer): Maximum results. Default 10.
- `query` (string, required): Package (e.g. @acme/analytics), repository (acme/analytics-js), product name or slug.

### `get_changelog` (~61 tokens)

Get changelog

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

Input parameters:

- `changelog` (string, required): Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name.

### `list_releases` (~121 tokens)

List releases

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

Input parameters:

- `breaking_only` (boolean): Only releases that contain breaking changes.
- `changelog` (string, required): Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name.
- `limit` (integer): Maximum releases. Default 20.
- `since` (string): Only releases published at or after this ISO 8601 time, e.g. 2026-01-01.

### `get_release` (~99 tokens)

Get release

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

Input parameters:

- `changelog` (string, required): Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name.
- `release` (string, required): Version like 2.0.0, or the release's URL slug.

### `compare_versions` (~152 tokens)

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`.

Input parameters:

- `changelog` (string, required): Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name.
- `format` (string): markdown (default) returns an upgrade guide; json returns structured data only.
- `from` (string): The version the user is on, e.g. 1.4.0. Omit to start from the first release.
- `to` (string): The version to upgrade to. Omit for the latest.

### `get_roadmap` (~77 tokens)

Get roadmap

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

Input parameters:

- `changelog` (string, required): Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name.
- `status` (string): Only items in this column.

### `convert_changelog` (~188 tokens)

Convert a 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 that aren't on LogPulse. Returns an llms.txt-style summary plus structured JSON.

Input parameters:

- `include_notes` (boolean): Include each release's full notes in the JSON. Default false to keep the answer short.
- `markdown` (string): The changelog text itself, e.g. the contents of CHANGELOG.md. Use this or url.
- `name` (string): Project name to use in the summary.
- `url` (string): GitHub URL: a release (github.com/owner/repo/releases/tag/v1.2.0), the releases page, a repository, or a CHANGELOG.md file. Use this or markdown.

### `publish_release` (~284 tokens)

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.

Input parameters:

- `author_name` (string): Shown as the author. Defaults to the API key's name.
- `body` (string): Release notes in Markdown.
- `breaking_changes` (array): What breaks for existing users, each with migration steps.
- `category` (string): new, improved or fixed. Default new.
- `deprecations` (array): What is deprecated, its replacement and planned removal version.
- `labels` (array): Up to 10 short labels, e.g. API, Dashboard.
- `published_at` (string): Schedule a future time, or backdate an import.
- `slug` (string): URL slug. Defaults to the title.
- `status` (string): published (default) goes live now, or at published_at. draft saves it for a human to review in LogPulse.
- `summary` (string): One sentence for lists and link previews.
- `title` (string, required): Short, user-facing headline, e.g. “Webhooks retry automatically”.
- `version` (string): Version this release ships in, e.g. 2.0.0. Unique per changelog.

### `post_roadmap_update` (~190 tokens)

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 header.

Input parameters:

- `description`: What and why, in a sentence or two.
- `eta`: Free text, e.g. Q3 or July.
- `id` (string): Update this item instead of creating a new one.
- `is_public` (boolean): Show on the public roadmap. Defaults to true for new items.
- `label`: Short tag, e.g. API or Mobile.
- `linked_release`: Release id, version or slug that shipped this item.
- `status` (string): Roadmap column. New items default to planned.
- `title` (string): Item title. Required when creating.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-lovable-release-ripple-roadmap-logpulse/release-ripple-roadmap#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 72

## Common questions

### What is the LogPulse MCP server?

LogPulse is an MCP server listed in the public MCP registry as app.lovable.release-ripple-roadmap/logpulse. Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON. This page covers its hosted endpoint (https://release-ripple-roadmap.lovable.app/mcp).

### Is the LogPulse MCP server safe to use?

LogPulse scores 75 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 LogPulse MCP server expose?

LogPulse exposes 9 tools: search_changelogs, get_changelog, list_releases, get_release, compare_versions, and 4 more. Their descriptions and schemas cost roughly 1,253 tokens of context every time the server is loaded.

### Does the LogPulse MCP server require authentication?

No. We connected to LogPulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LogPulse MCP server still maintained?

LogPulse 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.

## Links

- Remote endpoint: https://release-ripple-roadmap.lovable.app/mcp
- Website: https://release-ripple-roadmap.lovable.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-lovable-release-ripple-roadmap-logpulse/release-ripple-roadmap.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-lovable-release-ripple-roadmap-logpulse/release-ripple-roadmap.json
- HTML version of this page: https://verifymcp.io/servers/app-lovable-release-ripple-roadmap-logpulse/release-ripple-roadmap