EOSL.ai — Hardware End-of-Life Database
REMOTE · EOSL.AI · SCANNED SEP 24
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 → Why this is hard to 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 695 tokens (~139/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the EOSL.ai — Hardware End-of-Life Database MCP server?
EOSL.ai — Hardware End-of-Life Database is a hosted endpoint at https://eosl.ai/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 · eosl.ai
claude mcp add --transport http ai-eosl-eosl 'https://eosl.ai/mcp'
{
"mcpServers": {
"ai-eosl-eosl": {
"url": "https://eosl.ai/mcp"
}
}
} {
"servers": {
"ai-eosl-eosl": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://eosl.ai/mcp"
}
}
} assistant mcp add ai-eosl-eosl -t streamable-http -u '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.
- 10 Sept 26 0
- “lookup_part” reworded the description of “vendor” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 5 Sept 26 0
- Stability: 0.97 → pass security
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 75
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Aug 26 0
- Tool “bulk_check” rewrote its description, which is the text the model reads security
- Tool “get_family” rewrote its description, which is the text the model reads security
- Tool “list_vendors” rewrote its description, which is the text the model reads security
- Tool “lookup_part” rewrote its description, which is the text the model reads security
- Tool “search_models” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “bulk_check” reworded the description of “part_numbers” cosmetic
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 24 Sept 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 | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | b13f21ba3d4d491413ddc1f6a59fa961 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. 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 →
bulk_check ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| part_numbers | array | yes | 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. |
No output schema declared.
No examples provided.
get_family ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Family slug, e.g. "cisco-catalyst-3850". |
No output schema declared.
No examples provided.
list_vendors ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_part ~228
Look up one hardware part number or model name in the EOSL.ai database (read-only, no auth; for many parts use bulk_check). 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); a model/family name (e.g. "7010TX-48") that matches no SKU returns the family-level record, flagged matchedVia:family-name. Anything else returns found:false rather than a guessed date.
| 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, e.g. "Cisco". A tracked vendor restricts the match to that vendor (a part tracked under another vendor returns found:false naming that vendor). A string that is not a tracked vendor… |
No output schema declared.
No examples provided.
search_models ~104
Search tracked product families by vendor, product line, or series name (case-insensitive substring, e.g. "nexus 9300"). Read-only. Returns up to 10 families with status, EOSL window, and page URL. Use this for discovery when you have a name; for an exact part number use lookup_part, and 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.
What is the EOSL.ai — Hardware End-of-Life Database MCP server?
EOSL.ai — Hardware End-of-Life Database is an MCP server listed in the public MCP registry as ai.eosl/eosl. Hardware end-of-life dates by part number, each linked to the vendor's own bulletin. This page covers its hosted endpoint (https://eosl.ai/mcp).
Is the EOSL.ai — Hardware End-of-Life Database MCP server safe to use?
EOSL.ai — Hardware End-of-Life Database scores 79 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 EOSL.ai — Hardware End-of-Life Database MCP server expose?
EOSL.ai — Hardware End-of-Life Database exposes 5 tools: lookup_part, bulk_check, search_models, get_family, list_vendors. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.
Does the EOSL.ai — Hardware End-of-Life Database MCP server require authentication?
No. We connected to EOSL.ai — Hardware End-of-Life Database without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EOSL.ai — Hardware End-of-Life Database MCP server still maintained?
EOSL.ai — Hardware End-of-Life Database is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.