Is the Eosl MCP server down?

mcp-registry/ai.eosl/eosl · v1.0.0

healthy
Last checked 2026-10-24 02:11 UTC · handshake 131ms

As of 2026-10-24 02:11 UTC, the Eosl MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,527
outages (90d)
0
tools
5

Hardware end-of-life dates by part number, each linked to the vendor's own bulletin.

Install Eosl MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http eosl-mcp-server https://eosl.ai/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "eosl-mcp-server": {
      "type": "http",
      "url": "https://eosl.ai/mcp"
    }
  }
}

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

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 5 tool(s); ~875 tokens of tool definitions.
Scores higher than 47% of 15,622 MCP servers Glimind has audited.
Its tool list costs an agent ~875 tokens per session — lighter than 80% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: bulk_check, get_family, list_vendors, lookup_part, search_models

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 →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fai.eosl%2Feosl/fixes

bulk_check 1 change 
{
  "name": "bulk_check",
  "description": "Check up to 200 part numbers in one call (read-only, no auth; for a single part use lookup_part). Returns a per-part row (status, EOSL date, source URL, page URL) plus summary counts: past, endingSoon, supported, active, notFound. Never partial and never destructive: unknown or malformed entries do not fail the call, each simply returns found:false in its row.",
  "inputSchema": {
    "type": "object",
    "required": [
      "part_numbers"
    ],
    "properties": {
      "part_numbers": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 200,
        "minItems": 1,
        "description": "Part numbers to check; max 200 after case-insensitive deduplication. Punctuation differences (dashes, dots, spaces) are tolerated by the matcher, so raw inventory strings are fine."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_family 1 change 
{
  "name": "get_family",
  "description": "Fetch the full source-backed record for one product family by slug (from search_models or lookup_part pageUrl): lifecycle dates per SKU group, every part number, support runway score factors, and the vendor bulletin URLs. Read-only; an unknown slug returns found:false with a hint, never an error.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "Family slug, e.g. \"cisco-catalyst-3850\"."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_vendors 1 change 
{
  "name": "list_vendors",
  "description": "List all vendors tracked by EOSL.ai with family counts and vendor page URLs. Read-only, no parameters. Use this first to check whether a vendor is covered at all; for specific models use search_models, for a part number use lookup_part.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/ai.eosl/eosl"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.eosl/eosl"}) over MCP.

Passed

Largest tool definitions

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:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.eosl%2Feosl.svg)](https://glimind.com/server/mcp-registry%2Fai.eosl%2Feosl?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fai.eosl%2Feosl?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.eosl%2Feosl.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.eosl%2Feosl.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.eosl%2Feosl?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:d0ee0d6601a982dd…, first seen 2026-10-17, included at leaf 10668 of 55,944. Version history · verify what your client received.

Tools (5)

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

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Eosl MCP server down right now?

As of 2026-10-24 02:11 UTC, the Eosl MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Eosl MCP server provide?

Eosl MCP server advertises 5 tools, including bulk_check, get_family, list_vendors, lookup_part, search_models.

How do I install Eosl MCP server?

Point your MCP client at this streamable-http endpoint: https://eosl.ai/mcp

Is the Eosl MCP server safe to connect to an AI agent?

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

Feedback
Help us improve