EOSL.ai — Hardware End Of Life Database vs StackQL MCP Server
A side-by-side look at the EOSL.ai — Hardware End Of Life Database and StackQL MCP Server 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 EOSL.ai — Hardware End Of Life Database for databases work over a hosted endpoint; choose StackQL MCP Server for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose StackQL MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
describe_method, list_methods, list_providers.
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 | 56/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1,068 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | 15 |
| Full listing | View EOSL.ai — Hardware End Of Life Database | View StackQL MCP Server |
Tools & capabilities
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.
StackQL MCP Server tools 15
describe_methodFull I/O contract for one method: every input with its param_type (input_required params become exact-match WHERE predicates; input_optional ones may be added) and every output field, which are the columns a SELECT or RETURNING can reference. Call it after list_methods and before the first query against a method; there is no resource-level equivalent because each method returns its own shape. Requires provider, service, resource, method.list_methodsAccess methods (HTTP operations) for a resource with their SQL verb and required params. Pick the method whose verb matches the intent and whose required params you can supply, then describe_method it. Call when composing SQL from scratch against an unfamiliar resource; not needed when executing a vetted query library template. Requires provider, service, resource.list_providersAvailable cloud/SaaS providers (top of the hierarchy). No inputs.list_registryProviders (and their versions) available in the configured registry. Distinct from list_providers, which lists only providers already pulled. Optional provider arg lists versions for that provider.list_resourcesResources under a provider.service. Requires provider and service.list_servicesServices under a provider. Requires provider.pull_providerInstall a single provider from the registry into the local approot cache. Requires provider; version is optional (latest published is pulled when empty). Writes only local cache state; no cloud control/data plane effect.query_library_getRetrieve a query library entry by id. Without params: returns the raw template, param declarations and notes (adapt from it when no exact match exists). With params: the server validates values and returns rendered SQL plus which tool to execute it with (run_select_query or run_mutation_query). Read-only, no credentials.query_library_searchSearch the curated StackQL query library by natural-language intent. Returns ranked template ids. Consult before composing SQL from scratch; follow with query_library_get, which validates params and surfaces any the index omits. Read-only, no credentials.reload_credentialsLive-reload provider credentials: re-sources the server's configured env file into the process environment, invalidates cached auth contexts, and reports resolution status for every installed provider (optional provider arg filters the report; changed field flags values that differ from before). Never returns secret values. Credentials resolve automatically at query time - never call this at session start or before queries. Call only after a query fails with a credential resolution error (fix the env file first, then reload, then retry) or when the user says credentials have been rotated or changed. If the report shows changed: false after a failure, the file was not updated - ask the user rather than retrying.run_lifecycle_operationExecute a stackql EXEC lifecycle operation (eg EXEC aws.ec2.instances.start_instances ...). Real cloud side effects. Discover available operations and required params via list_methods and describe_method. Returns {messages, timestamp}. Gated by server mode.run_mutation_queryExecute INSERT/UPDATE/REPLACE/DELETE against the provider. Real side effects. Returns {messages, timestamp}. Gated by server mode. Consult query_library_search for a vetted template before composing SQL from scratch; when the SQL came from a library entry, pass its id as source.- +3 more on the listing page
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.
EOSL.ai — Hardware End Of Life Database
{
"mcpServers": {
"eosl-ai-hardware-end-of-life-database": {
"url": "https://eosl.ai/mcp/"
}
}
}
StackQL MCP Server
{
"mcpServers": {
"stackql-mcp-server": {
"command": "npx",
"args": [
"-y",
"@stackql/mcp-server"
]
}
}
}
Frequently asked questions
EOSL.ai — Hardware End Of Life Database is categorized under Databases and uses a remote HTTP/SSE transport. StackQL MCP Server belongs to Databases and uses a local stdio subprocess. Pick EOSL.ai — Hardware End Of Life Database for databases work and StackQL MCP Server 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.
EOSL.ai — Hardware End Of Life Database has no declared pricing — check the project's own site. Auth: no auth required. StackQL MCP Server is listed as free. 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 eosl-ai-hardware-end-of-life-database and stackql-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, EOSL.ai — Hardware End Of Life Database has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. StackQL MCP Server has 71/100 (Great) with 5 views, 0 installs and 1,068 GitHub stars.