Back to search
100
MCP live MCP 2025-06-18 streamable-http

Assetize — IBM Maximo knowledge

au.com.assetize/maximo

Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.

Watch this dependency Share evidence report
Uptime
100.0%
5 direct probes · 30d
Response
3729ms
last probe
Tools
19
callable
Resources
6
readable
Prompts
0
available
Primary URL
https://assetize.com.au/mcp
Score: 100/100
Handshake verified by our own probe.
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
19 tools, 6 resources, 0 prompts returned.
pass 3 or more catalogue items 10/10
25 items in total; 3 or more earns these points.
pass Describes itself 10/10
89 characters; more than 30 earns these points.

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 DECLINES when the published record cannot s…

search_records

Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.

lookup_error_code

Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).

get_record

Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.

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 anno…

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 …

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 b…

list_gotchas

Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.

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>.

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.

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…

corpus_stats

Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.

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 m…

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 …

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…

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.

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 on…

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…

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…

Resources · 6

corpus-capabilities

Self-describing manifest — the server, every tool it exposes, and every discoverable resource. Read this first to learn the surface. JSON.

assetize://corpus/capabilities
corpus-stats

Published record count, unique source documents, versions represented, raw evidence items. JSON.

assetize://corpus/stats
corpus-versions

Every Maximo version/family the corpus covers, with published record counts and a read URI per version. JSON — the discovery layer for version-scoped queries.

assetize://corpus/versions
corpus-changelog

The dated, source-cited 9.x change log (same data as the maximo_changelog tool and assetize.com.au/changelog).

assetize://corpus/changelog
corpus-gotchas

Known traps, upgrade landmines, install / security / troubleshooting records (same data as the list_gotchas tool).

assetize://corpus/gotchas
corpus-change-watch

Curated feed of materially important 9.x changes, each with a labelled Assetize interpretation and its evidence (same data as the change_watch tool).

assetize://corpus/change-watch

How to use

Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://assetize.com.au/mcp

Cursor or Cline: add to your MCP config:

{
  "mcpServers": {
    "assetize_\u2014_ibm_maximo_knowledge": {
      "url": "https://assetize.com.au/mcp",
      "transport": "streamable-http"
    }
  }
}