# Assetize — IBM Maximo knowledge (remote · assetize.com.au)

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

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `assetize.com.au`: 68/100 (this document), [markdown](https://verifymcp.io/servers/au-com-assetize-maximo/assetize.md), [page](https://verifymcp.io/servers/au-com-assetize-maximo/assetize)

## Channel facts

- Endpoint: `https://assetize.com.au/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3355 tokens (~134/item across 25 items; 19 tools + 6 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Assetize — IBM Maximo knowledge MCP server?

Assetize — IBM Maximo knowledge is a hosted endpoint at https://assetize.com.au/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http au-com-assetize-maximo 'https://assetize.com.au/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.au-com-assetize-maximo]
url = "https://assetize.com.au/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "au-com-assetize-maximo": {
      "type": "remote",
      "url": "https://assetize.com.au/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add au-com-assetize-maximo --url 'https://assetize.com.au/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  au-com-assetize-maximo:
    url: "https://assetize.com.au/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "au-com-assetize-maximo": {
      "Transport": "http",
      "Url": "https://assetize.com.au/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add au-com-assetize-maximo -t streamable-http -u 'https://assetize.com.au/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 68, +3)

- [security improvement] HSTS header: fail → pass

### 2026-09-26 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-25 (score 65)

First indexed and scored.

## MCP tools (19)

### `ask_maximo` (~115 tokens)

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.

Input parameters:

- `question` (string, required): The Maximo question, in plain language.
- `version` (string): Optional version scope, e.g. "9.2", "8.11", "7.6.1".

### `search_records` (~89 tokens)

Search published Maximo records

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

Input parameters:

- `limit` (number): Max results, 1-25 (default 10).
- `query` (string, required): Keywords or an exact identifier (MXAPI..., BMX..., module name).
- `version` (string): Optional version label or family filter, e.g. "9.2".

### `lookup_error_code` (~60 tokens)

Look up a Maximo error code

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

Input parameters:

- `code` (string, required): The error/fix code, e.g. "BMXAA4214E".

### `get_record` (~47 tokens)

Get a full record with sources

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

Input parameters:

- `slug` (string, required): Record slug from search_records / lookup_error_code results.

### `compare_maximo_versions` (~217 tokens)

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.

Input parameters:

- `from` (string, required): Starting version, e.g. "7.6.1.3".
- `to` (string, required): Target version, e.g. "9.2".

### `maximo_changelog` (~193 tokens)

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.

Input parameters:

- `limit` (number): Max entries (default 200, max 1000).
- `type` (string): Filter to one change type: DEPRECATION, BEHAVIOUR_CHANGE, FIX, SECURITY, GOTCHA, UPGRADE, LIFECYCLE, RELEASE.
- `version` (string): Filter to a 9.x line, e.g. "9.2". Omit for all of 9.x.

### `change_watch` (~183 tokens)

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.

Input parameters:

- `category` (string): Filter: SECURITY|UPGRADE|DEPRECATION|RELEASE|BEHAVIOUR|MIGRATION|INTEGRATION|SUPPORT.
- `limit` (number): Max items when listing (default 30, max 60).
- `slug` (string): A change slug for the full record. Omit to list.

### `list_gotchas` (~77 tokens)

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.

Input parameters:

- `limit` (number): Max results (default 30, max 100).
- `version` (string): Optional version, e.g. "9.2".

### `records_by_version` (~85 tokens)

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

Input parameters:

- `limit` (number): Max results (default 40, max 200).
- `version` (string, required): Version label or family, e.g. "9.2".

### `behaviour_history` (~85 tokens)

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.

Input parameters:

- `limit` (number): Max results (default 30, max 100).
- `version` (string): Optional version filter, e.g. "9.2".

### `support_lifecycle` (~90 tokens)

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.

Input parameters:

- `limit` (number): Max results (default 30).
- `version` (string): Optional version, e.g. "8.11", "9.0".

### `corpus_stats` (~33 tokens)

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` (~232 tokens)

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

Input parameters:

- `lens` (string, required): The target release lens.
- `source` (string, required): The Automation Script source — Jython or JavaScript, a WORKORDER Object launch point. Up to 64 KiB.

### `upgrade_plan` (~250 tokens)

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

Input parameters:

- `from` (string, required): Source release: "7.6.1", "8.11", "9.0", "9.1".
- `to` (string, required): Target release: "8.11", "9.0", "9.1", "9.2".

### `upgrade_checklist` (~119 tokens)

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.

Input parameters:

- `from` (string, required): Source release, e.g. "8.11".
- `phase` (string): Optional: BEFORE, DURING or AFTER.
- `to` (string, required): Target release, e.g. "9.2".

### `fixes_gained` (~127 tokens)

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.

Input parameters:

- `area` (string): Optional functional area, e.g. "WORK_ORDERS".
- `from` (string, required): Source release, e.g. "9.1".
- `limit` (number): Max entries per section (default 40, max 200).
- `to` (string, required): Target release, e.g. "9.2".

### `deprecation_register` (~89 tokens)

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.

Input parameters:

- `kind` (string): Optional: DEPRECATION, REMOVAL or RENAME.

### `lifecycle_dates` (~119 tokens)

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.

Input parameters:

- `product` (string): Optional product substring, e.g. "Application Suite" or "Asset Management".
- `version` (string): Optional version, e.g. "8.11", "7.6.1", "9.0".

### `maximo_mobile` (~240 tokens)

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.

Input parameters:

- `topic` (string): Optional topic: what, architecture, devices, deploy, auth, sync, admin, apps, notifications, classic.
- `version` (string): Optional Maximo Mobile release: "8.11", "9.0", "9.1" or "9.2". Facts that hold for every release are always included.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/au-com-assetize-maximo/assetize#diagnostics

## Score history

- 2026-09-28: 68
- 2026-09-27: 68
- 2026-09-26: 65
- 2026-09-25: 65

## Common questions

### What is the Assetize — IBM Maximo knowledge MCP server?

Assetize — IBM Maximo knowledge is an MCP server listed in the public MCP registry as au.com.assetize/maximo. Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle. This page covers its hosted endpoint (https://assetize.com.au/mcp).

### Is the Assetize — IBM Maximo knowledge MCP server safe to use?

Assetize — IBM Maximo knowledge scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Assetize — IBM Maximo knowledge MCP server expose?

Assetize — IBM Maximo knowledge exposes 19 tools: ask_maximo, search_records, lookup_error_code, get_record, compare_maximo_versions, and 14 more. Their descriptions and schemas cost roughly 2,450 tokens of context every time the server is loaded.

### Does the Assetize — IBM Maximo knowledge MCP server require authentication?

No. We connected to Assetize — IBM Maximo knowledge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Assetize — IBM Maximo knowledge MCP server still maintained?

Assetize — IBM Maximo knowledge is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://assetize.com.au/mcp
- Repository: https://github.com/softwarecomparereview/Assetize
- Website: https://assetize.com.au/connect
- Changelog RSS feed: https://verifymcp.io/servers/au-com-assetize-maximo/assetize.xml
- Changelog JSON feed: https://verifymcp.io/servers/au-com-assetize-maximo/assetize.json
- HTML version of this page: https://verifymcp.io/servers/au-com-assetize-maximo/assetize