EOSL.ai — Hardware End Of Life Database vs Influxdb3 MCP Server
A side-by-side look at the EOSL.ai — Hardware End Of Life Database and Influxdb3 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 Influxdb3 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 Influxdb3 MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
INFLUX_MCP_TOOL_PROFILE. - You want tools like
load_database_context, get_help, write_line_protocol.
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 | 82/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | INFLUX_MCP_TOOL_PROFILE |
| Verified owner | Community listing | Verified |
| GitHub stars | — | 38 |
| Directory activity | 0 views 0 installs 0 upvotes | 50 views 0 installs 0 upvotes |
| Tools | 5 | 27 |
| Full listing | View EOSL.ai — Hardware End Of Life Database | View Influxdb3 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.
Influxdb3 MCP Server tools 27
load_database_contextLoad optional custom database context and documentationget_helpGet help and troubleshooting guidance for InfluxDB operationswrite_line_protocolWrite data using InfluxDB line protocolcreate_databaseCreate a new database (with cloud-specific config options)update_databaseUpdate database configuration (retention for all; maxTables/maxColumns for Cloud Dedicated/Clustered)delete_databaseDelete a database by name (irreversible)execute_queryRun a SQL query against a database (supports multiple formats)query_sqlRun bounded read-only SQL with structured response metadataquery_influxqlRun bounded read-only InfluxQL with structured response metadataget_measurementsList all measurements (tables) in a databaseget_measurement_schemaGet schema (columns/types) for a measurement/tablelist_tablesList tables, also called measurements, in a database- +15 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/"
}
}
}
Influxdb3 MCP Server
{
"mcpServers": {
"influxdata-influxdb3-mcp-server": {
"command": "npx",
"args": [
"-y",
"usage"
],
"env": {
"INFLUX_MCP_TOOL_PROFILE": "YOUR_INFLUX_MCP_TOOL_PROFILE_HERE"
}
}
}
}
Frequently asked questions
EOSL.ai — Hardware End Of Life Database is categorized under Databases and uses a remote HTTP/SSE transport. Influxdb3 MCP Server belongs to Databases and uses a local stdio subprocess. Pick EOSL.ai — Hardware End Of Life Database for databases work and Influxdb3 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. Influxdb3 MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 eosl-ai-hardware-end-of-life-database and influxdata-influxdb3-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. Influxdb3 MCP Server has 82/100 (Excellent) with 50 views, 0 installs and 38 GitHub stars.