mcp-registry/app.lovable.release-ripple-roadmap/logpulse · registry v1.0.0 · server reports v1.3.0
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.
Data as of .
| 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 | — |
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 16:32 UTC, the LogPulse MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 0 minutes.
Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.
Claude Code
claude mcp add --transport http logpulse-mcp-server https://release-ripple-roadmap.lovable.app/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"logpulse-mcp-server": {
"type": "http",
"url": "https://release-ripple-roadmap.lovable.app/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,341 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 10 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.lovable.release-ripple-roadmap/logpulse"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.lovable.release-ripple-roadmap/logpulse"}) over MCP.
publish_release ~827 tokenscommits_to_changelog ~645 tokensgithub_release_notes ~636 tokensgenerate_release_notes ~437 tokenspost_roadmap_update ~437 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fapp.lovable.release-ripple-roadmap%2Flogpulse?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.lovable.release-ripple-roadmap%2Flogpulse?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fapp.lovable.release-ripple-roadmap%2Flogpulse.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:74e0f18152c122c7…, first seen 2026-11-15, included at leaf 264180 of 384,635. Version history · verify what your client received.
Compare: most reliable code servers · most reliable retrieval servers · most reliable data servers · most reliable knowledge servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 16:32 UTC, the LogPulse MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 0 minutes.
LogPulse MCP server advertises 13 tools, including commits_to_changelog, compare_versions, convert_changelog, generate_release_notes, get_changelog.
Point your MCP client at this streamable-http endpoint: https://release-ripple-roadmap.lovable.app/mcp
Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.