Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nothing to run from here
Assetize — IBM Maximo knowledge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
19
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http assetize-ibm-maximo-knowledge-mcp https://assetize.com.au/mcp
# 2 — ask your agent for something these tools do
# ask_maximo, search_records, lookup_error_code and 16 more
Assetize — IBM Maximo knowledge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ASAll 1 server
assetize1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http assetize-ibm-maximo-knowledge-mcp https://assetize.com.au/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The Maximo question, in plain language. |
| version | string | no | Optional version scope, e.g. "9.2", "8.11", "7.6.1". |
Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords or an exact identifier (MXAPI..., BMX..., module name). |
| version | string | no | Optional version label or family filter, e.g. "9.2". |
| limit | number | no | Max results, 1-25 (default 10). |
Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | The error/fix code, e.g. "BMXAA4214E". |
Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Record slug from search_records / lookup_error_code results. |
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 (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Starting version, e.g. "7.6.1.3". |
| to | string | yes | Target version, e.g. "9.2". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Filter to a 9.x line, e.g. "9.2". Omit for all of 9.x. |
| type | string | no | Filter to one change type: DEPRECATION, BEHAVIOUR_CHANGE, FIX, SECURITY, GOTCHA, UPGRADE, LIFECYCLE, RELEASE. |
| limit | number | no | Max entries (default 200, max 1000). |
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; omi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | A change slug for the full record. Omit to list. |
| category | string | no | Filter: SECURITY|UPGRADE|DEPRECATION|RELEASE|BEHAVIOUR|MIGRATION|INTEGRATION|SUPPORT. |
| limit | number | no | Max items when listing (default 30, max 60). |
Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Optional version, e.g. "9.2". |
| limit | number | no | Max results (default 30, max 100). |
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>.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | yes | Version label or family, e.g. "9.2". |
| limit | number | no | Max results (default 40, max 200). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Optional version filter, e.g. "9.2". |
| limit | number | no | Max results (default 30, max 100). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Optional version, e.g. "8.11", "9.0". |
| limit | number | no | Max results (default 30). |
Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
No parameter schema on file.
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | yes | The Automation Script source — Jython or JavaScript, a WORKORDER Object launch point. Up to 64 KiB. |
| lens | string | yes | The target release lens. |
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 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Source release, e.g. "8.11". |
| to | string | yes | Target release, e.g. "9.2". |
| phase | string | no | Optional: BEFORE, DURING or AFTER. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | Source release, e.g. "9.1". |
| to | string | yes | Target release, e.g. "9.2". |
| area | string | no | Optional functional area, e.g. "WORK_ORDERS". |
| limit | number | no | Max entries per section (default 40, max 200). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Optional: DEPRECATION, REMOVAL or RENAME. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Optional product substring, e.g. "Application Suite" or "Asset Management". |
| version | string | no | Optional version, e.g. "8.11", "7.6.1", "9.0". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Optional Maximo Mobile release: "8.11", "9.0", "9.1" or "9.2". Facts that hold for every release are always included. |
| topic | string | no | Optional topic: what, architecture, devices, deploy, auth, sync, admin, apps, notifications, classic. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Assetize — IBM Maximo knowledge or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Assetize — IBM Maximo knowledge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.