LogPulse
REMOTE · RELEASE-RIPPLE-ROADMAP.LOVABLE.APP
Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.
Available components
Last scanned (59 minutes ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://release-ripple-roadmap.lovable.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lovable.app | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a0305f14b2a99af130a9e43af07d3e5 |
| SANs: lovable.app, *.lovable.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of release-ripple-roadmap.lovable.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| lovable.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://release-ripple-roadmap.lovable.app/mcp | Verified | 200 | |
| http (plaintext) | http://release-ripple-roadmap.lovable.app/mcp | HTTPS enforced | 301 | https://release-ripple-roadmap.lovable.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_versions Compare versions ~152
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| changelog | string | yes | 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. |
No output schema declared.
No examples provided.
convert_changelog Convert a changelog ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_changelog Get changelog ~61
Get a changelog's name, repository, packages, latest version and feed links.
| Name | Type | Req | Description |
|---|---|---|---|
| changelog | string | yes | Changelog slug, e.g. "acme". Use search_changelogs to find it from a package, repository or product name. |
No output schema declared.
No examples provided.
get_release Get release ~99
Get one release by version (2.0.0 or v2.0.0) or URL slug, with full notes, breaking changes and deprecations.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_roadmap Get roadmap ~77
Get the public roadmap: items under review, planned, in progress and shipped, with vote counts.
| Name | Type | Req | Description |
|---|---|---|---|
| changelog | string | yes | 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. |
No output schema declared.
No examples provided.
list_releases List releases ~121
List published releases, newest first, with versions, breaking changes, migration steps and deprecations.
| Name | Type | Req | Description |
|---|---|---|---|
| breaking_only | boolean | – | Only releases that contain breaking changes. |
| changelog | string | yes | 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. |
No output schema declared.
No examples provided.
post_roadmap_update Post roadmap update ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
publish_release Publish release ~284
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Short, user-facing headline, e.g. “Webhooks retry automatically”. |
| version | string | – | Version this release ships in, e.g. 2.0.0. Unique per changelog. |
No output schema declared.
No examples provided.
search_changelogs Search changelogs ~81
Find a public LogPulse changelog by package name, repository, product name or slug. Returns slugs to use with the other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results. Default 10. |
| query | string | yes | Package (e.g. @acme/analytics), repository (acme/analytics-js), product name or slug. |
No output schema declared.
No examples provided.
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.
remote · release-ripple-roadmap.lovable.app
claude mcp add --transport http app-lovable-release-ripple-roadmap-logpulse 'https://release-ripple-roadmap.lovable.app/mcp'
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.