Assetize

Connect

Wire Assetize into your AI assistant

Assetize runs a public Model Context Protocol server. Point Claude, Claude Code, Cursor or any MCP client at it and your assistant answers Maximo questions from published, source-cited evidence — and says so when the evidence isn't there, instead of making something up.

How a question travels

Public Maximo knowledge only. Customer assessments never pass through this endpoint.

  1. Your AI assistant sends a tool call to assetize.com.au/mcp.
  2. The arguments are validated against the tool's schema.
  3. The rate limit is checked.
  4. One of the 19 tools reads the public Maximo corpus.
  5. You get a cited answer, or a decline when the evidence isn't there.

Endpoint

https://assetize.com.au/mcp — Streamable HTTP, no auth. Ask generation (ask_maximo on incident/how-to questions) is 10 requests per minute and 100 per day per IP address; version-path encyclopedia answers and other tools are not that cap. Other MCP tools are 30/min and 500/day, resetting at 00:00 UTC. A shared office or VPN network counts as one IP.

Tools (19)

  • ask_maximo (question, version?) — Ask a Maximo question (evidence-cited). 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 how-to, troubleshooting, version-behaviour and error questions.
  • search_records (query, version?, limit?) — Search published Maximo records. Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
  • lookup_error_code (code) — Look up a Maximo error code. Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
  • get_record (slug) — Get a full record with sources. Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
  • compare_maximo_versions (from, to) — Compare two 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 as context only, never scored as upgrade work. Same reviewed, source-backed comparison and ranking as assetize.com.au/compare. Accepts either a version label ("7.6.1.3", "9.2") or bucket id ("9-2"). Known buckets: 7.6.1.3, 7.6.x (classic Maximo 7.6/7.6.1/7.6.1.x), 8.x (Maximo Application Suite 8), 9.0, 9.1, 9.2.
  • maximo_changelog (version?, type?, limit?) — Maximo 9.x change log. 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) and nothing the curator demoted. Same data as assetize.com.au/changelog. Optionally filter by version ("9.1", "9.2") and/or type.
  • change_watch (slug?, category?, limit?) — Curated Maximo 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 clearly-labelled Assetize interpretation (never presented as IBM’s), the IBM sources, and the corpus records that grounded it. Pass a slug for one change in full; omit it to list, optionally filtered by category. Same data as assetize.com.au/change-watch.
  • list_gotchas (version?, limit?) — Maximo gotchas & upgrade traps. 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 (version, limit?) — What Assetize covers for a 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 (version?, limit?) — Maximo behaviour & lifecycle 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 (version?, limit?) — Maximo support & end-of-support dates. 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.
  • corpus_stats (—) — Assetize corpus coverage. Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
  • test_automation_script_evidence (source, lens) — Check a WORKORDER Automation Script against a Maximo/MAS lens (Automation Script Test Harness). 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/getDate/getBoolean, then reports which ones the named lens has evidence for. Static evidence only — it does not run the script. A missing attribute is reported NOT_ASSESSED, never claimed as a runtime failure; for a real pass/fail/skip verdict, run the CLI (mvn verify) or the browser runner at assetize.com.au/test-stubs/automation-scripts. Lenses: 761 (Maximo 7.6.1), mas811 (MAS 8.11), mas90 (MAS 9.0), mas91 (MAS 9.1), mas92 (MAS 9.2).
  • upgrade_plan (from, to) — Plan a Maximo move (Upgrade Desk). 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 (route, platform, database, Java, users, add-ons, reports; each with IBM's words and page), the few items only the customer's own system can answer, break-class changes (deprecations, behaviour changes) and landmines (upgrade notes, gotchas) in range from the 9.x change log, fix and security counts, the deprecation-register rows touching the range, and the curated Change Watch entries. Every item links its record or IBM page. Same composition as assetize.com.au/upgrade/<from>/<to>.
  • upgrade_checklist (from, to, phase?) — Phased upgrade checklist for a move. 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-dependent question to settle against IBM. Optionally one phase.
  • fixes_gained (from, to, area?, limit?) — Fixes and security changes a move carries. 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 (kind?) — Deprecation, removal and rename 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.com.au/upgrade/deprecations.
  • lifecycle_dates (product?, version?) — Structured Maximo support 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 assetize.com.au/upgrade/deadlines.
  • maximo_mobile (version?, topic?) — What IBM says about 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 URL, MDM), login and shared devices, data sync and attachments, administration (Mobile Configuration app, properties), the apps release by release (8.11, 9.0, 9.1, 9.2), push notifications, and coming from Maximo Anywhere or 7.6.1. Every fact carries IBM's verbatim sentence, page and read date. Scope by release and/or topic. Same data as assetize.com.au/mobile. For fixes and gotchas use search_records.

The server also publishes MCP Resources for discovery: assetize://corpus/capabilities (every tool and resource), assetize://corpus/versions, assetize://corpus/stats, and the record/{slug}, version/{version} and error/{code} templates.

What your assistant can do with it

Ask what breaks on a 7.6.1.3 → 9.2 move and get a per-area report where announcement volume is never counted as upgrade burden. Ask what changed in 9.2 this quarter and filter the change log to deprecations. Resolve a BMXAA code against the published record. Ask "does this apply on 9.1 too?" and get a version-scoped answer, because every record carries its version scope. Ask it to plan an 8.11 → 9.2 move and the Upgrade Desk tools return the route under IBM's n-1 policy, what IBM says about the move, the checklist, the register rows and the deadline clock. Ask what your technicians' devices need for Maximo Mobile 9.2 and maximo_mobile answers with the OS levels, memory, WebView2 and shared-device rules in IBM's words, from the Maximo Mobile desk.

The difference from asking a general assistant the same questions: these answers are assembled only from records carrying an IBM or named-expert source and a verification date — and where that evidence does not exist, the tool says so rather than producing a confident, plausible, wrong answer about your system.

Ground rules

  • Every substantive claim carries a citation back to the original public source.
  • When the published evidence cannot support an answer, the tools decline. No fabrication.
  • Public and unauthenticated. Ask generation is 10 requests/minute and 100/day per IP address; version-path encyclopedia answers are not that cap. Other MCP tools are 30/min and 500/day. Get in touch for higher limits.