Dbhub vs EOSL.ai — Hardware End Of Life Database
A side-by-side look at the Dbhub and EOSL.ai — Hardware End Of Life Database MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
E
EOSL.ai — Hardware End Of Life DatabaseDatabases · Remote HTTP/SSEHardware end-of-life dates by part number, each linked to the vendor's own bulletin.56GoodAuth: no auth requiredVerdict: choose Dbhub for databases work as a local process; choose EOSL.ai — Hardware End Of Life Database for databases over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dbhub when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
dbhub.toml.
EChoose EOSL.ai — Hardware End Of Life Database when
- You need dedicated capabilities in the Databases domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
lookup_part, bulk_check, search_models.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | E EOSL.ai — Hardware End Of Life Database | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 57/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,716 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | 5 |
| Full listing | View Dbhub | View EOSL.ai — Hardware End Of Life Database |
Tools & capabilities
Dbhub tools 1
dbhub.toml
EOSL.ai — Hardware End Of Life Database tools 5
lookup_partLook 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.bulk_checkCheck 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.search_modelsSearch 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.get_familyFetch 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.list_vendorsList 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.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Dbhub
{
"mcpServers": {
"dbhub": {
"command": "npx",
"args": [
"-y",
"@bytebase/dbhub@latest"
]
}
}
}
EOSL.ai — Hardware End Of Life Database
{
"mcpServers": {
"eosl-ai-hardware-end-of-life-database": {
"url": "https://eosl.ai/mcp/"
}
}
}
Frequently asked questions
Dbhub is categorized under Databases and uses a local stdio subprocess. EOSL.ai — Hardware End Of Life Database belongs to Databases and uses a remote HTTP/SSE transport. Pick Dbhub for databases work and EOSL.ai — Hardware End Of Life Database for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Dbhub has no declared pricing — check the project's own site. EOSL.ai — Hardware End Of Life Database has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dbhub and eosl-ai-hardware-end-of-life-database as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dbhub has a quality signal of 57/100 (Good) with 1 views, 0 installs and 3,716 GitHub stars. EOSL.ai — Hardware End Of Life Database has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.