Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
LogPulse is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http logpulse-mcp https://release-ripple-roadmap.lovable.app/mcp
# 2 — ask your agent for something these tools do
# search_changelogs, get_changelog, list_releases and 6 more
LogPulse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LOAll 6 servers
lovable6 servers
4 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http logpulse-mcp https://release-ripple-roadmap.lovable.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find a public LogPulse changelog by package name, repository, product name or slug. Returns slugs to use with the other tools.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Package (e.g. @acme/analytics), repository (acme/analytics-js), product name or slug. |
| limit | integer | no | Maximum results. Default 10. |
Get a changelog's name, repository, packages, latest version and feed links.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| changelog | string | yes | Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name. |
List published releases, newest first, with versions, breaking changes, migration steps and deprecations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| changelog | string | yes | Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name. |
| limit | integer | no | Maximum releases. Default 20. |
| since | string | no | Only releases published at or after this ISO 8601 time, e.g. 2026-01-01. |
| breaking_only | boolean | no | Only releases that contain breaking changes. |
Get one release by version (2.0.0 or v2.0.0) or URL slug, with full notes, breaking changes and deprecations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| changelog | string | yes | Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name. |
| release | string | yes | Version like 2.0.0, or the release's URL slug. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| changelog | string | yes | Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name. |
| from | string | no | The version the user is on, e.g. 1.4.0. Omit to start from the first release. |
| to | string | no | The version to upgrade to. Omit for the latest. |
| format | string | no | markdown (default) returns an upgrade guide; json returns structured data only. |
Get the public roadmap: items under review, planned, in progress and shipped, with vote counts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| changelog | string | yes | Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name. |
| status | string | no | Only items in this column. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | 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. |
| markdown | string | no | The changelog text itself, e.g. the contents of CHANGELOG.md. Use this or url. |
| name | string | no | Project name to use in the summary. |
| include_notes | boolean | no | Include each release's full notes in the JSON. Default false to keep the answer short. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Short, user-facing headline, e.g. “Webhooks retry automatically”. |
| version | string | no | Version this release ships in, e.g. 2.0.0. Unique per changelog. |
| summary | string | no | One sentence for lists and link previews. |
| body | string | no | Release notes in Markdown. |
| category | string | no | new, improved or fixed. Default new. |
| labels | array | no | Up to 10 short labels, e.g. API, Dashboard. |
| status | string | no | published (default) goes live now, or at published_at. draft saves it for a human to review in LogPulse. |
| published_at | string | no | Schedule a future time, or backdate an import. |
| breaking_changes | array | no | What breaks for existing users, each with migration steps. |
| deprecations | array | no | What is deprecated, its replacement and planned removal version. |
| author_name | string | no | Shown as the author. Defaults to the API key's name. |
| slug | string | no | URL slug. Defaults to the title. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | Update this item instead of creating a new one. |
| title | string | no | Item title. Required when creating. |
| description | no | What and why, in a sentence or two. | |
| status | string | no | Roadmap column. New items default to planned. |
| label | no | Short tag, e.g. API or Mobile. | |
| eta | no | Free text, e.g. Q3 or July. | |
| is_public | boolean | no | Show on the public roadmap. Defaults to true for new items. |
| linked_release | no | Release id, version or slug that shipped this item. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install LogPulse or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 31 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digeste0a352cf7cd2e0e082311043e7b6839672338af790ac2d07d484ebf7daaefe86
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_changelogs | no tags | |
| get_changelog | no tags | |
| list_releases | no tags | |
| get_release | no tags | |
| compare_versions | no tags | |
| get_roadmap | no tags | |
| convert_changelog | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| publish_release | state-write | state-write: declares readOnlyHint: false |
| post_roadmap_update | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digeste0a352cf7cd2e0e0
Scanned2026-10-31
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish LogPulse can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.