Assetize — IBM Maximo knowledge

Name: Assetize — IBM Maximo knowledge
Author: au.com.assetize

MCP serverMCP

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

by au.com.assetizerepository ↗homepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"assetize-ibm-maximo-knowledge","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability45/45 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	1759 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
11 h ago	mcp initialize	ok	200	1754 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
17 h ago	mcp initialize	ok	200	773 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
23 h ago	mcp initialize	ok	200	1491 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
29 h ago	mcp initialize	ok	200	2998 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
35 h ago	mcp initialize	ok	200	1749 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
2 d ago	mcp initialize	ok	200	1733 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
2 d ago	mcp initialize	ok	200	1271 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
2 d ago	mcp initialize	ok	200	1838 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools
3 d ago	mcp initialize	ok	200	1974 ms	server assetize-maximo 1.0.0 · protocol 2025-06-18 · 19 tools

Tools observed via MCP handshake

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
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, got
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
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
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 as
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
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 eve
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
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
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
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
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
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,

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryau.com.assetize/maximo

first seen 12 d ago · fetched 22 h agoopen ↗

Field history (7 recent events)

12 d ago · declared · summary → "Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle."
12 d ago · declared · description → "Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle."
12 d ago · declared · publisherName → "au.com.assetize"
12 d ago · declared · homepageUrl → "https://assetize.com.au/connect"
12 d ago · declared · repoUrl → "https://github.com/softwarecomparereview/Assetize"
12 d ago · declared · version → "1.0.0"
12 d ago · declared · protocols → ["mcp"]

Assetize — IBM Maximo knowledge

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from