Assetize — IBM Maximo knowledge
REMOTE · ASSETIZE.COM.AU
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
Available components
Last scanned (21 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Code Search and Documentation
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3371 tokens (~134/item across 25 items; 19 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 +45
- Authorization: fail → unverified ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 26 Oct 26 −45
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://assetize.com.au/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=assetize.com.au | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 83551127565025d70eb605fdee3c4135 |
| SANs: assetize.com.au | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of assetize.com.au. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| au. | DS published | 26642 | 8 | Verified |
| com.au. | DS published | 13190, 14185 | 8, 8 | Verified |
| assetize.com.au. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://assetize.com.au/mcp | Verified | 200 | |
| http (plaintext) | http://assetize.com.au/mcp | HTTPS enforced | 301 | https://assetize.com.au/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_maximo Ask a Maximo question (evidence-cited) ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The Maximo question, in plain language. |
| version | string | – | Optional version scope, e.g. "9.2", "8.11", "7.6.1". |
No output schema declared.
No examples provided.
behaviour_history Maximo behaviour & lifecycle history ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 30, max 100). |
| version | string | – | Optional version filter, e.g. "9.2". |
No output schema declared.
No examples provided.
change_watch Curated Maximo Change Watch ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
compare_maximo_versions Compare two Maximo versions ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Starting version, e.g. "7.6.1.3". |
| to | string | yes | Target version, e.g. "9.2". |
No output schema declared.
No examples provided.
corpus_stats Assetize corpus coverage ~33
Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deprecation_register Deprecation, removal and rename register ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional: DEPRECATION, REMOVAL or RENAME. |
No output schema declared.
No examples provided.
fixes_gained Fixes and security changes a move carries ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional functional area, e.g. "WORK_ORDERS". |
| from | string | yes | Source release, e.g. "9.1". |
| limit | number | – | Max entries per section (default 40, max 200). |
| to | string | yes | Target release, e.g. "9.2". |
No output schema declared.
No examples provided.
get_record Get a full record with sources ~47
Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Record slug from search_records / lookup_error_code results. |
No output schema declared.
No examples provided.
lifecycle_dates Structured Maximo support dates ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
list_gotchas Maximo gotchas & upgrade traps ~77
Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 30, max 100). |
| version | string | – | Optional version, e.g. "9.2". |
No output schema declared.
No examples provided.
lookup_error_code Look up a Maximo error code ~60
Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The error/fix code, e.g. "BMXAA4214E". |
No output schema declared.
No examples provided.
maximo_changelog Maximo 9.x change log ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
maximo_mobile What IBM says about Maximo Mobile ~240
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
records_by_version What Assetize covers for a version ~85
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>.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 40, max 200). |
| version | string | yes | Version label or family, e.g. "9.2". |
No output schema declared.
No examples provided.
search_records Search published Maximo records ~89
Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, 1-25 (default 10). |
| query | string | yes | Keywords or an exact identifier (MXAPI..., BMX..., module name). |
| version | string | – | Optional version label or family filter, e.g. "9.2". |
No output schema declared.
No examples provided.
support_lifecycle Maximo support & end-of-support dates ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 30). |
| version | string | – | Optional version, e.g. "8.11", "9.0". |
No output schema declared.
No examples provided.
test_automation_script_evidence Check a WORKORDER Automation Script against a Maximo/MAS lens (Automation Script Test Harness) ~232
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).
| Name | Type | Req | Description |
|---|---|---|---|
| lens | string | yes | The target release lens. |
| source | string | yes | The Automation Script source — Jython or JavaScript, a WORKORDER Object launch point. Up to 64 KiB. |
No output schema declared.
No examples provided.
upgrade_checklist Phased upgrade checklist for a move ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Source release, e.g. "8.11". |
| phase | string | – | Optional: BEFORE, DURING or AFTER. |
| to | string | yes | Target release, e.g. "9.2". |
No output schema declared.
No examples provided.
upgrade_plan Plan a Maximo move (Upgrade Desk) ~250
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>.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Source release: "7.6.1", "8.11", "9.0", "9.1". |
| to | string | yes | Target release: "8.11", "9.0", "9.1", "9.2". |
No output schema declared.
No examples provided.
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.
remote · assetize.com.au
claude mcp add --transport http au-com-assetize-maximo 'https://assetize.com.au/mcp'
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 81 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Assetize — IBM Maximo knowledge MCP server?
VerifyMCP ran 12 checks on Assetize — IBM Maximo knowledge, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Assetize — IBM Maximo knowledge: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.