Skip to content

LogPulse MCP server

app.lovable.release-ripple-roadmap/logpulserelease-ripple-roadmap.lovable.appstreamable-httpv1.0.0Scanned

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

9 tools: 1 do something that can't be undone, 2 change things and 6 only read.

Tools: 0 delete, 1 irreversible, 2 write, 6 read.
  • Reads private data · 3
  • Reads text others write · 3
  • Can send data out · 3
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LogPulse MCP server can do

The LogPulse MCP server is published by release-ripple-roadmap.lovable.app, a domain the MCP Registry verified. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_release) and create or change data (2 tools: convert_changelog and post_roadmap_update), but cannot delete data. 6 tools only read.

3 tools read private data (search_changelogs, get_changelog and get_release); 3 tools bring in text other people can write (get_release, get_roadmap and convert_changelog); 3 tools can send data out of your system (convert_changelog, publish_release and post_roadmap_update). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Can't be undone 1Claude Code: ask
  • publish_releasePublish a release note to your LogPulse changelog right after shipping — with version, breaking changes, migration steps and deprecations.Can send data outNo findings

    Why it is in this group

    • The name "publish_release" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_release" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 2Claude Code: ask
  • convert_changelogTurn 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 wit…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "convert_changelog" says "convert": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "convert_changelog" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The name "convert_changelog" says "convert": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • post_roadmap_updateAdd 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.Can send data outNo findings

    Why it is in this group

    • The name "post_roadmap_update" says "post": a word for a change.

    What it can reach

    • outboundThe name "post_roadmap_update" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • compare_versionsAnswer “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`.No findings

    Why it is in this group

    • The name "compare_versions" says "compare": a word for reading.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_changelogGet a changelog's name, repository, packages, latest version and feed links.Reads private dataNo findings

    Why it is in this group

    • The name "get_changelog" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "repository": it reads repositories.
    Description, as the server wrote it
    Get a changelog's name, repository, packages, latest version and feed links.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_releaseGet one release by version (2.0.0 or v2.0.0) or URL slug, with full notes, breaking changes and deprecations.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_release" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get one release by version (2.0.0 or v2.0.0) or URL slug, with full notes, breaking changes and deprecations.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • get_roadmapGet the public roadmap: items under review, planned, in progress and shipped, with vote counts.Reads text others writeNo findings

    Why it is in this group

    • The name "get_roadmap" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "review": it reads comments, which other people can write.
    Description, as the server wrote it
    Get the public roadmap: items under review, planned, in progress and shipped, with vote counts.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_releasesList published releases, newest first, with versions, breaking changes, migration steps and deprecations.No findings

    Why it is in this group

    • The name "list_releases" says "list": a word for reading.
    Description, as the server wrote it
    List published releases, newest first, with versions, breaking changes, migration steps and deprecations.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • search_changelogsFind a public LogPulse changelog by package name, repository, product name or slug.Reads private dataNo findings

    Why it is in this group

    • The name "search_changelogs" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "repository": it reads repositories.
    Description, as the server wrote it
    Find a public LogPulse changelog by package name, repository, product name or slug. Returns slugs to use with the other tools.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

27 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 3 outbound tools breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__logpulse__convert_changelog",
      "mcp__logpulse__post_roadmap_update",
      "mcp__logpulse__publish_release"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:25 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (3 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://release-ripple-roadmap.lovable.app/mcp: tools/list returned 13 tools to an anonymous client, including github_release_notes (irreversible), generate_release_notes (irreversible), publish_release (irreversible), commits_to_changelog (write), convert_changelog (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • Tools that change things, listed without credentials: 4 to 6
  2. Nov 14, 2026
    • Tools that change things, listed without credentials: 3 to 4

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "convert_changelog" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The name "convert_changelog" says "convert": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 6.View diff
    • Tools that change things, listed without credentials: 4 to 6
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
    • Tools that change things, listed without credentials: 3 to 4
  3. Tools9 changed.~9 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__logpulse__search_changelogs",
      "mcp__logpulse__get_changelog",
      "mcp__logpulse__list_releases",
      "mcp__logpulse__get_release",
      "mcp__logpulse__compare_versions",
      "mcp__logpulse__get_roadmap"
    ],
    "ask": [
      "mcp__logpulse__convert_changelog",
      "mcp__logpulse__publish_release",
      "mcp__logpulse__post_roadmap_update"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as logpulse. Review it before you use it.

Capability tags behind 7 rules
  • mcp__logpulse__search_changelogs private-data
  • mcp__logpulse__get_changelog private-data
  • mcp__logpulse__get_release private-data, untrusted-input
  • mcp__logpulse__get_roadmap untrusted-input
  • mcp__logpulse__convert_changelog untrusted-input, outbound
  • mcp__logpulse__publish_release outbound
  • mcp__logpulse__post_roadmap_update outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.lovable.release-ripple-roadmap/logpulse/verify?hash=f2699817e87a848dcfc96703aa64ddf80a2da5da6421f54bbdac9fabbb715dfd" | jq -e '.changed == false'

Pinned hash f2699817e87a, from Nov 12, 2026, 10:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.lovable.release-ripple-roadmap/logpulse/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.lovable.release-ripple-roadmap/logpulse
[![Anlyon Radar](https://radar.anlyon.com/badge/app.lovable.release-ripple-roadmap/logpulse.svg)](https://radar.anlyon.com/servers/app.lovable.release-ripple-roadmap/logpulse)

Source: MCP Registry. Synced Oct 30, 2026, 17:17 UTC.

LogPulse MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LogPulse MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LogPulse MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the LogPulse MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: publish_release.

What tools does the LogPulse MCP server have?

9 tools: 1 irreversible, 2 write, 6 read. publish_release, convert_changelog, post_roadmap_update, search_changelogs, get_changelog, list_releases, get_release, compare_versions and 1 more.

Does the LogPulse MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LogPulse MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): convert_changelog, publish_release and post_roadmap_update.

Has the LogPulse MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.