Assetize — IBM Maximo knowledge is answering right now. Last checked 7 min ago. It exposes 19 tools.
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
45 days of history
45 days agonow
100.0%
Uptime 24h
91 of 91 checks
19
Tools
read from the server
1915 ms
Response time
average over 24h
open, no key
Access
streamable-http
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add maximo --transport http https://assetize.com.au/mcpSettings → Connectors → Add custom connector, then paste this address
https://assetize.com.au/mcp~/.codex/config.toml
[mcp_servers.maximo]
url = "https://assetize.com.au/mcp".cursor/mcp.json
{
"mcpServers": {
"maximo": {
"url": "https://assetize.com.au/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"maximo": {
"type": "http",
"url": "https://assetize.com.au/mcp"
}
}
}Available tools 19
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
maximo
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, 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_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.
records
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>.
search_records
Fast keyword search over published Assetize knowledge records. Returns slugs, titles and short answers with record URLs.
upgrade
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 an item whose records are not published is dropped — or VERIFY, a level-dependent question to settle against IBM. Optionally one phase.
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 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>.
ask
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 DECLINES when the published record cannot support one — it never guesses. Best for how-to, troubleshooting, version-behaviour and error questions.
behaviour
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 assetize.com.au/archaeology.
change
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.
compare
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, 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.
corpus
corpus_stats
Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.
deprecation
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 records that say so. Curated; rows publish only on evidence. Same data as assetize.com.au/upgrade/deprecations.
fixes
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, never scored as upgrade weight.
gotchas
list_gotchas
Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.
lifecycle
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 IBM page each comes from. Optionally scope by product or version. Same data as assetize.com.au/upgrade/deadlines.
lookup
lookup_error_code
Find published records about a specific Maximo error or fix identifier (BMXAA1234E, IJ12345, APAR...).
record
get_record
Fetch one published record by slug: the established fact, claims, version scope, and every cited source URL.
support
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 and the curated Change Watch. Optionally scope to a version.
test
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 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).
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://assetize.com.au/mcp | streamable-http | answering | 2620 ms | 7 min ago |
Alternatives to Assetize — IBM Maximo knowledge
same job, measured the same wayNoetix
by noetix
Your company's knowledge for Claude Code, Cursor and Codex, with cited answers and procedures.
Memorybank
by maxweb4u
Seeds, governs and navigates a memory_bank knowledge base: gated writes, routing, drift vs code
Hypermnesia MCP Viz
by cdeust
Read-only visualization for Cortex memory, knowledge, sessions, traces, and codebase graphs.
crewlore
by srijansk
Team knowledge compiled from your coding agents' sessions and pull requests, every entry cited.
Code-Graph-RAG
by vitali87
Knowledge-graph RAG for multi-language codebases: index, query and edit code in natural language.
Codeseeker
by jghiringhelli
Graph-powered code intelligence with semantic search and knowledge graph for AI assistants
Rules MCP
by akr1166
MCP for rules/skills/knowledge evaluation for Cursor, Claude, VS Code, and Antigravity.
TokenKnows
by johnnywuj81
Distill AI coding sessions into weekly reports, ADRs and a knowledge graph - self-hosted
Assetize — IBM Maximo knowledge — questions
Answers built from our own checks of this server.
What can Assetize — IBM Maximo knowledge do?
It exposes 19 tools, read directly from the server on our last check. Among them: ask_maximo, behaviour_history, change_watch, compare_maximo_versions, corpus_stats, deprecation_register and 13 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Assetize — IBM Maximo knowledge mostly used for?
Its tools cluster around records, maximo and upgrade. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Assetize — IBM Maximo knowledge working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1915 ms. The bar chart above shows every period we have measured.
Is Assetize — IBM Maximo knowledge still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Assetize — IBM Maximo knowledge?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Assetize — IBM Maximo knowledge need an API key?
No. Assetize — IBM Maximo knowledge completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 19 of them are readable on this page. This is what we observed, not what the docs claim.