LogsLoom
REMOTE · MCP.LOGSLOOM.COM · 2 COMPONENTS · SCANNED SEP 20
Ingest and search LogsLoom logs from coding agents.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 314 tokens (~78/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "logs_ingest" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the LogsLoom MCP server?
LogsLoom is a hosted endpoint at https://mcp.logsloom.com/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 · mcp.logsloom.com
claude mcp add --transport http efim23-logsloom 'https://mcp.logsloom.com/mcp'
{
"mcpServers": {
"efim23-logsloom": {
"url": "https://mcp.logsloom.com/mcp"
}
}
} {
"servers": {
"efim23-logsloom": {
"type": "http",
"url": "https://mcp.logsloom.com/mcp"
}
}
} [mcp_servers.efim23-logsloom] url = "https://mcp.logsloom.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"efim23-logsloom": {
"type": "remote",
"url": "https://mcp.logsloom.com/mcp",
"enabled": true
}
}
} openclaw mcp add efim23-logsloom --url 'https://mcp.logsloom.com/mcp' --transport streamable-http
mcp_servers:
efim23-logsloom:
url: "https://mcp.logsloom.com/mcp" {
"McpServers": {
"efim23-logsloom": {
"Transport": "http",
"Url": "https://mcp.logsloom.com/mcp"
}
}
} assistant mcp add efim23-logsloom -t streamable-http -u 'https://mcp.logsloom.com/mcp'
{
"mcpServers": {
"efim23-logsloom": {
"type": "http",
"url": "https://mcp.logsloom.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 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.
- 18 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 61
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 20 Sept 2026 · Probed https://mcp.logsloom.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.logsloom.com | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 519b99029d5706821397cef8084bc39d |
| SANs: mcp.logsloom.com | ||||||
| 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 mcp.logsloom.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| logsloom.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.logsloom.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.logsloom.com/mcp | HTTPS enforced | 301 | https://mcp.logsloom.com/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 →
logs_get Get a log by id ~58
Fetch one log by id. The HTTP API has no GET /v1/logs/:id yet, so this tries that path and falls back to searching the latest list page.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Log event id from ingest or search |
No output schema declared.
No examples provided.
logs_ingest Ingest logs ~121
Send one or many log events to LogsLoom (POST /v1/logs). Provide a single event via level+message, or a batch in `events` (max 100).
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | – |
| events | array | – | Batch of events; overrides single-event fields when set |
| level | string | – | Required unless `events` is set |
| message | string | – | Required unless `events` is set |
| metadata | object | – | – |
| service | string | – | – |
| timestamp | string | – | – |
No output schema declared.
No examples provided.
logs_projects_list Current project scope ~39
There is no user-session projects API. Returns the project scope implied by the current API key (connectivity check via GET /v1/logs).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logs_search Search logs ~96
List logs for the API-key's project (GET /v1/logs). Filters: q (message contains), level, service, limit, offset.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | – |
| limit | integer | – | 1–100, default 50 |
| offset | integer | – | Pagination offset, default 0 |
| q | string | – | Case-insensitive message contains |
| service | string | – | Exact service name |
No output schema declared.
No examples provided.
What is the LogsLoom MCP server?
LogsLoom is an MCP server listed in the public MCP registry as io.github.efim23/logsloom. Ingest and search LogsLoom logs from coding agents. This page covers its hosted endpoint (https://mcp.logsloom.com/mcp).
Is the LogsLoom MCP server safe to use?
LogsLoom scores 63 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 LogsLoom MCP server expose?
LogsLoom exposes 4 tools: logs_ingest, logs_search, logs_get, logs_projects_list. Their descriptions and schemas cost roughly 314 tokens of context every time the server is loaded.
Does the LogsLoom MCP server require authentication?
No. We connected to LogsLoom without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LogsLoom MCP server still maintained?
LogsLoom is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.