Assetize — IBM Maximo knowledge is a remote MCP server that gives an AI agent 19 tools, among them ask_maximo, behaviour_history, change_watch. It answers at https://assetize.com.au/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 26 September 2026; the last check, on 9 November 2026, succeeded.
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 DECLINES when the published record cannot support one — it never guesses. Best for Inputs: question, version |
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 assetize.com.au/archaeology. Inputs: version, limit |
change_watch | The curated feed of genuinely material IBM Maximo / MAS 9.x changes — security, upgrades, deprecations, releases, behaviour and migration breaks. Each carries What Changed / Why It Matters, previous behaviour, a version comparison, a clearl Inputs: slug, category, limit |
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, gotchas), fixes/APARs since, and newly announced capability — the last two reported Inputs: from, to |
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 records that say so. Curated; rows publish only on evidence. Same data as assetize.co Inputs: kind |
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, never scored as upgrade weight. Inputs: from, to, area, limit |
get_record | Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL. Inputs: slug |
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 IBM page each comes from. Optionally scope by product or version. Same data as ass Inputs: product, version |
list_gotchas | Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas. Inputs: version, limit |
lookup_error_code | Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...). Inputs: code |
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, lifecycle and releases. Only real change records (never data-dictionary noise) an Inputs: version, type, limit |
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, ARCore, shared devices), getting the app onto devices (stores, MSIX, QR server U Inputs: version, topic |
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>. Inputs: version, limit |
search_records | Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs. Inputs: query, version, limit |
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 and the curated Change Watch. Optionally scope to a version. Inputs: version, limit |
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 every attribute the script references via mbo.getString/setValue/isNull/getInt/getD Inputs: source, lens |
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 an item whose records are not published is dropped — or VERIFY, a level-depende Inputs: from, to, phase |
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 source release, the staged route (IBM's n-1 policy), what IBM says about the move (r Inputs: from, to |
Every block below points at https://assetize.com.au/mcp. Pick your client and copy.
claude mcp add --transport http assetize-ibm-maximo-knowledge https://assetize.com.au/mcp
{
"mcpServers": {
"assetize-ibm-maximo-knowledge": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://assetize.com.au/mcp"]
}
}
}{
"mcpServers": {
"assetize-ibm-maximo-knowledge": {
"url": "https://assetize.com.au/mcp"
}
}
}{
"servers": {
"assetize-ibm-maximo-knowledge": {
"type": "http",
"url": "https://assetize.com.au/mcp"
}
}
}{
"context_servers": {
"assetize-ibm-maximo-knowledge": {
"url": "https://assetize.com.au/mcp"
}
}
}{
"mcpServers": {
"assetize-ibm-maximo-knowledge": {
"serverUrl": "https://assetize.com.au/mcp"
}
}
}{
"mcpServers": {
"assetize-ibm-maximo-knowledge": {
"url": "https://assetize.com.au/mcp"
}
}
}name: Assetize — IBM Maximo knowledge
version: 0.0.1
schema: v1
mcpServers:
- name: Assetize — IBM Maximo knowledge
type: streamable-http
url: https://assetize.com.au/mcp{
"mcpServers": {
"assetize-ibm-maximo-knowledge": {
"httpUrl": "https://assetize.com.au/mcp"
}
}
}{
"mcpServers": {
"assetize-ibm-maximo-knowledge": {
"type": "http",
"url": "https://assetize.com.au/mcp"
}
}
}{
"mcpServers": {
"assetize-ibm-maximo-knowledge": {
"url": "https://assetize.com.au/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fassetize.com.au%2Fmcp&type=streamable_http&id=assetize-ibm-maximo-knowledge&name=Assetize%20%E2%80%94%20IBM%20Maximo%20knowledge
It answered our last check on 9 November 2026 in 887 ms. Over 4 checks since 26 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by com.au and served from assetize.com.au, the vendor's own domain: https://assetize.com.au/mcp.
19, as returned by the server's own tools/list on 16 November 2026: ask_maximo, behaviour_history, change_watch, compare_maximo_versions, corpus_stats, deprecation_register, fixes_gained, get_record, and 11 more.
It answered our last check on 9 November 2026 in 887 ms. Over 4 checks since 26 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://assetize.com.au/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: au.com.assetize. Endpoint host: assetize.com.au. ARD identifier: urn:air:au.com.assetize:mcp:maximo.
First indexed 25 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.