Is the Efim23 Logsloom MCP server down?

mcp-registry/io.github.efim23/logsloom · v0.1.1

As of 2026-10-26 07:17 UTC, the Efim23 Logsloom MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.

Ingest and search LogsLoom logs from coding agents.

claude mcp add --transport http efim23-logsloom-mcp-server https://mcp.logsloom.com/mcp

{
  "mcpServers": {
    "efim23-logsloom-mcp-server": {
      "type": "http",
      "url": "https://mcp.logsloom.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

What to fix (3)

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.efim23%2Flogsloom/fixes

{
  "name": "logs_get",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "minLength": 1,
        "description": "Log event id from ingest or search"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a log by id"
}

{
  "name": "logs_projects_list",
  "description": "There is no user-session projects API. Returns the project scope implied by the current API key (connectivity check via GET /v1/logs).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Current project scope"
}

{
  "name": "logs_search",
  "description": "List logs for the API-key's project (GET /v1/logs). Filters: q (message contains), level, service, limit, offset.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "q": {
        "type": "string",
        "minLength": 1,
        "description": "Case-insensitive message contains"
      },
      "level": {
        "enum": [
          "debug",
          "info",
          "warn",
          "error",
          "fatal"
        ],
        "type": "string"
      },
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1,
        "description": "1–100, default 50"
      },
      "offset": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": 0,
        "description": "Pagination offset, default 0"
      },
      "service": {
        "type": "string",
        "minLength": 1,
        "description": "Exact service name"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Search logs"
}

Get alerted

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/io.github.efim23/logsloom"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.efim23/logsloom"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~882 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.96% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• logs_ingest ~508 tokens
• logs_search ~191 tokens
• logs_get ~105 tokens
• logs_projects_list ~78 tokens

Static 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. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.efim23%2Flogsloom.svg)](https://glimind.com/server/mcp-registry%2Fio.github.efim23%2Flogsloom?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.efim23%2Flogsloom?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.efim23%2Flogsloom.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.efim23%2Flogsloom.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.efim23%2Flogsloom?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cd1eb50edd422c73…, first seen 2026-10-17, included at leaf 10349 of 71,371. Version history · verify what your client received.

Tools (4)

• logs_get
• logs_ingest
• logs_projects_list
• logs_search

Compare: most reliable retrieval servers · most reliable data servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Efim23 Logsloom MCP server down right now?

As of 2026-10-26 07:17 UTC, the Efim23 Logsloom MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Efim23 Logsloom MCP server provide?

Efim23 Logsloom MCP server advertises 4 tools, including logs_get, logs_ingest, logs_projects_list, logs_search.

How do I install Efim23 Logsloom MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.logsloom.com/mcp

Is the Efim23 Logsloom MCP server safe to connect to an AI agent?

Glimind scanned all 4 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.

Operator of Efim23 Logsloom MCP server?

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.