EOSL.ai — Hardware End-of-Life Database
REMOTE · EOSL.AI · SCANNED AUG 7
Hardware end-of-life dates by part number, each linked to the vendor's own bulletin.
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 →
Endpoint Security60
- 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 5 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 470 tokens (~94/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · eosl.ai
claude mcp add --transport http ai-eosl-eosl https://eosl.ai/mcp
[mcp_servers.ai-eosl-eosl] url = "https://eosl.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-eosl-eosl": {
"type": "remote",
"url": "https://eosl.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-eosl-eosl --url https://eosl.ai/mcp --transport streamable-http
mcp_servers:
ai-eosl-eosl:
url: "https://eosl.ai/mcp" {
"mcpServers": {
"ai-eosl-eosl": {
"type": "http",
"url": "https://eosl.ai/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.
- 7 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 6 Aug 26 +39
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: excellent functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- 5 Aug 26 24
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 7 Aug 2026 · Probed https://eosl.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eosl.ai | CN=WE1,O=Google Trust Services,C=US | 21 Jun 2026 | 19 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 190f25ecea04ccdd137d6ff36092c5d5 |
| SANs: eosl.ai | ||||||
| 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 |
DNSSEC secure
Validation of eosl.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| eosl.ai. | present | 2371 | 13 | Verified |
| eosl.ai. | Verified address RRset verified with the apex keys |
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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://eosl.ai/mcp | Verified | 200 | |
| http (plaintext) | http://eosl.ai/mcp | HTTPS enforced | 301 | https://eosl.ai/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.
bulk_check ~73
Check up to 200 part numbers in one call. Returns a per-part row (status, EOSL date, source URL, page URL) plus summary counts: past, endingSoon, supported, active, notFound.
| Name | Type | Req | Description |
|---|---|---|---|
| part_numbers | array | yes | Part numbers to check (deduplicated; max 200). |
No output schema declared.
No examples provided.
get_family ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Family slug, e.g. "cisco-catalyst-3850". |
No output schema declared.
No examples provided.
list_vendors ~25
List all vendors tracked by EOSL.ai with family counts and vendor page URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_part ~143
Look up one hardware part number in the EOSL.ai database. Returns support status, End-of-Sale and End-of-Service-Life dates, support runway score, and the primary vendor bulletin URL backing the dates. Matching is exact, then punctuation-insensitive, then Fortinet short-SKU aliases (FG-60E -> FortiGate-60E). Returns found:false rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| part_number | string | yes | Vendor part number / SKU, e.g. "WS-C3850-48P-S" or "FG-100F". |
| vendor | string | – | Optional vendor hint, e.g. "Cisco". Restricts the match to that vendor. |
No output schema declared.
No examples provided.
search_models ~81
Search tracked product families by vendor, product line, or series name (case-insensitive substring, e.g. "nexus 9300"). Returns up to 10 families with status, EOSL window, and page URL. Use get_family with a returned slug for the full record.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search text, 1-120 characters. |
No output schema declared.
No examples provided.