Assetize — IBM Maximo knowledge MCP server
au.com.assetize/maximoassetize.com.austreamable-httpv1.0.0Scanned
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
19 tools: 3 do something that can't be undone, 12 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Assetize — IBM Maximo knowledge MCP server can do
The Assetize — IBM Maximo knowledge MCP server is published by assetize.com.au, a domain the MCP Registry verified. It has 19 tools. It can do things that cannot be undone, such as sending, paying or publishing (upgrade_plan, upgrade_checklist and fixes_gained) and create or change data (12 tools: ask_maximo, lookup_error_code, maximo_changelog, change_watch and 8 more), but cannot delete data. 4 tools only read.
2 tools bring in text other people can write (get_record and list_gotchas); 3 tools can send data out of your system (upgrade_plan, upgrade_checklist and fixes_gained).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
19 tools
Can't be undone 3Claude Code: ask
fixes_gainedEvery FIX and SECURITY record the 9.x change log holds for the releases inside a move (the 9.x log starts at 9.1).Can send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it 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.
upgrade_checklistThe phased checklist (before / during / after) for one Maximo move.Can send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it 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.
upgrade_planOne 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 stag…Can send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it 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>.
Changes things 12Claude Code: ask
ask_maximoAnswer a practical IBM Maximo question from Assetize’s published, source-backed knowledge.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
behaviour_historyHistorical, lifecycle, behaviour-change, deprecation, architecture and API records — the "how did this get here / when does it end" archaeology.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
change_watchThe curated feed of genuinely material IBM Maximo / MAS 9.x changes — security, upgrades, deprecations, releases, behaviour and migration breaks.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
corpus_statsCoverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
deprecation_registerWhat 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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_datesEnd-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 fr…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
lookup_error_codeFind published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).No findings
Why it is in this group
- The name "lookup_error_code" says "lookup": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
maximo_changelogThe 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 release…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
maximo_mobileResearched IBM statements about Maximo Mobile, by topic: what it is, the shell and Graphite-app architecture, device requirements (OS levels, memory, WebView2, ARCore, shared devic…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
records_by_versionEvery published record scoped to a given Maximo version or family (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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>.
support_lifecycleIBM 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 Chan…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
test_automation_script_evidenceStatically check a WORKORDER Object launch point Automation Script (Jython or JavaScript) against one release lens's real MXAPIWODETAIL dictionary.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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).
Only reads 4Show 4 read-only tools
compare_maximo_versionsCompare 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 s…No findings
Why it is in this group
- The name "compare_maximo_versions" says "compare": a word for reading.
Description, as the server wrote it 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.
get_recordFetch one published record by slug: the established fact, claims, version scope, and every cited source URL.Reads text others writeNo findings
Why it is in this group
- The name "get_record" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
list_gotchasKnown traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version.Reads text others writeNo findings
Why it is in this group
- The name "list_gotchas" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
Description, as the server wrote it Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.
search_recordsFast keyword search over published Assetize knowledge records.No findings
Why it is in this group
- The name "search_records" says "search": a word for reading.
Description, as the server wrote it Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:30 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (3 irreversible, 12 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://assetize.com.au/mcp: tools/list returned 19 tools to an anonymous client, including upgrade_plan (irreversible), upgrade_checklist (irreversible), fixes_gained (irreversible), ask_maximo (write), lookup_error_code (write) and 10 more
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 403 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 15
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: no to not observed
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 403
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 15 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 403 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 15 (and 2 more).View diff
- HTTP status of an anonymous initialize: 403 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 15
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: no to not observed
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 403; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 15 -> 0 (and 2 more).View diff
- HTTP status of an anonymous initialize: 200 to 403
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 15 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to no
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http maximo https://assetize.com.au/mcpclaude mcp add --transport http maximo https://assetize.com.au/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__maximo__search_records",
"mcp__maximo__get_record",
"mcp__maximo__compare_maximo_versions",
"mcp__maximo__list_gotchas"
],
"ask": [
"mcp__maximo__ask_maximo",
"mcp__maximo__lookup_error_code",
"mcp__maximo__maximo_changelog",
"mcp__maximo__change_watch",
"mcp__maximo__records_by_version",
"mcp__maximo__behaviour_history",
"mcp__maximo__support_lifecycle",
"mcp__maximo__corpus_stats",
"mcp__maximo__test_automation_script_evidence",
"mcp__maximo__upgrade_plan",
"mcp__maximo__upgrade_checklist",
"mcp__maximo__fixes_gained",
"mcp__maximo__deprecation_register",
"mcp__maximo__lifecycle_dates",
"mcp__maximo__maximo_mobile"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as maximo. Review it before you use it.
Capability tags behind 5 rules
- mcp__maximo__get_record untrusted-input
- mcp__maximo__list_gotchas untrusted-input
- mcp__maximo__upgrade_plan outbound
- mcp__maximo__upgrade_checklist outbound
- mcp__maximo__fixes_gained outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/au.com.assetize/maximo/verify?hash=41d2d2e5f67289da2f4355daf0611acb4d7625b4bc1273d533032a0ce8889289" | jq -e '.changed == false'Pinned hash 41d2d2e5f672, from Nov 10, 2026, 07:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/au.com.assetize/maximo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/au.com.assetize/maximo)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:45 UTC.
Assetize — IBM Maximo knowledge MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Assetize — IBM Maximo knowledge MCP server safe?
- No scan can promise that. What its definitions show: 19 tools, 15 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Assetize — IBM Maximo knowledge MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Assetize — IBM Maximo knowledge MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: upgrade_plan, upgrade_checklist and fixes_gained.
What tools does the Assetize — IBM Maximo knowledge MCP server have?
- 19 tools: 3 irreversible, 12 write, 4 read. upgrade_plan, upgrade_checklist, fixes_gained, ask_maximo, lookup_error_code, maximo_changelog, change_watch, records_by_version and 11 more.
Does the Assetize — IBM Maximo knowledge MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Assetize — IBM Maximo knowledge MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): upgrade_plan, upgrade_checklist and fixes_gained.
Has the Assetize — IBM Maximo knowledge MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.