Products Tracked by Category
endoflifedate/products-in-category
The software products endoflife.date tracks in one category (lang, os, database, framework, app, server-app, service, device or standard), each with the exact name to use in lifecycle lookups, its display label, aliases and tags. Use it to find how a product is spelled before asking for its release cycles. Data from endoflife.date, https://endoflife.date, MIT licensed, passed through unmodified and served by Eden Engine; not an official endoflife.date product.
Price
$0.0026 per call
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.
Data source
Product lifecycle data from endoflife.date, https://endoflife.date, an open-source project released under the MIT licence (https://github.com/endoflife-date/endoflife.date/blob/master/LICENSE). Passed through unmodified and served by Eden Engine; this is not an official endoflife.date product.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "endoflifedate/products-in-category" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "endoflifedate/products-in-category" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "endoflifedate/products-in-category", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "endoflifedate/products-in-category", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0026 |
- Updated
- Oct 26, 2026
Input and output schemas
Input schema
{
"type": "object",
"required": [
"category"
],
"properties": {
"category": {
"enum": [
"lang",
"os",
"database",
"framework",
"app",
"server-app",
"service",
"device",
"standard"
],
"type": "string",
"description": "The product category."
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"required": [
"results"
],
"properties": {
"results": {
"type": "array",
"items": {
"type": "object",
"required": [
"name"
],
"properties": {
"uri": {
"type": "string",
"description": "The product's API address."
},
"name": {
"type": "string",
"description": "Name to use in lifecycle lookups."
},
"tags": {
"type": "array",
"items": {
"type": "string",
"description": "A tag."
},
"description": "Tags."
},
"label": {
"type": "string",
"description": "Display label."
},
"aliases": {
"type": "array",
"items": {
"type": "string",
"description": "An alternative name."
},
"description": "Alternative names."
},
"category": {
"type": "string",
"description": "The product's category."
}
},
"additionalProperties": true
},
"description": "Products in the category."
}
},
"additionalProperties": true
}