# Com Assetize Maximo MCP server

Source: https://glimind.com/server/mcp-registry%2Fau.com.assetize%2Fmaximo
Registry id: `mcp-registry/au.com.assetize/maximo`
Status: auth-required (checked 2026-10-27T02:04:14.081Z)

## Measurements (30 days)

- Uptime: 99.93%
- Checks: 4400
- Outages (90 days): 3

## Install

```json
{
  "mcpServers": {
    "com-assetize-maximo-mcp-server": {
      "type": "http",
      "url": "https://assetize.com.au/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http com-assetize-maximo-mcp-server https://assetize.com.au/mcp
```

## Tools (19)

- `ask_maximo`: Answer a practical IBM Maximo question from Assetize’s published, source-backed knowledge. The answer cites its evidence ([R#] markers with source URLs) and DEC
- `behaviour_history`: Historical, lifecycle, behaviour-change, deprecation, architecture and API records — the "how did this get here / when does it end" archaeology. Same data as as
- `change_watch`: The curated feed of genuinely material IBM Maximo / MAS 9.x changes — security, upgrades, deprecations, releases, behaviour and migration breaks. Each carries W
- `compare_maximo_versions`: Compare two Maximo versions/eras and get a cited upgrade-impact report per functional area: changes to absorb (deprecations, behaviour changes, API changes, got
- `corpus_stats`: Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
- `deprecation_register`: What was deprecated, removed or renamed in Maximo / MAS, in which version, what IBM says replaces it (blank when IBM has not named one), and the published recor
- `fixes_gained`: Every FIX and SECURITY record the 9.x change log holds for the releases inside a move (the 9.x log starts at 9.1). Optionally one functional area. Counted, neve
- `get_record`: Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
- `lifecycle_dates`: End-of-support, Extended Support and Dual Support dates for Maximo and MAS as structured rows: product, version, milestone, ISO date, days remaining, and the IB
- `list_gotchas`: Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas
- `lookup_error_code`: Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
- `maximo_changelog`: The dated, source-cited log of what changed across IBM Maximo / MAS 9.x (9.1 onward): deprecations, behaviour changes, API/fixes, security, gotchas, upgrades, l
- `maximo_mobile`: Researched IBM statements about Maximo Mobile, by topic: what it is, the shell and Graphite-app architecture, device requirements (OS levels, memory, WebView2, 
- `records_by_version`: Every published record scoped to a given Maximo version or family (e.g. "9.2", "7.6.1"). Same data as assetize.com.au/maximo/<version>.
- `search_records`: Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
- `support_lifecycle`: IBM Maximo / MAS support-lifecycle facts: end-of-support / Extended Support transitions and the 2026/2027 deadlines, drawn from source-backed lifecycle records 
- `test_automation_script_evidence`: Statically check a WORKORDER Object launch point Automation Script (Jython or JavaScript) against one release lens's real MXAPIWODETAIL dictionary. Extracts eve
- `upgrade_checklist`: The phased checklist (before / during / after) for one Maximo move. Every item is CITED — its published records are resolved against the corpus on this call and
- `upgrade_plan`: One Maximo move from an earlier catalogue release to a later one (7.6.1, 8.11, 9.0, 9.1, 9.2), composed from the published record: the support clock on the sour

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.