au.com.assetize/maximo

Est-ce que au.com.assetize/maximo est sûr ?

Au dernier audit MCP Hub, le serveur MCP « au.com.assetize/maximo » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 19 outils

• ask_maximo≈ 184 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • version · string · optionnel
    Optional version scope, e.g. "9.2", "8.11", "7.6.1".
  • question · string · requis
    The Maximo question, in plain language.

  Exemple d'appel

  {"name": "ask_maximo", "arguments": {"question": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• behaviour_history≈ 134 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
    Max results (default 30, max 100).
  • version · string · optionnel
    Optional version filter, e.g. "9.2".

  Exemple d'appel

  {"name": "behaviour_history", "arguments": {"limit": 1, "version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• change_watch≈ 244 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "change_watch", "arguments": {"slug": "texte", "limit": 1, "category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• compare_maximo_versions≈ 230 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • to · string · requis
    Target version, e.g. "9.2".
  • from · string · requis
    Starting version, e.g. "7.6.1.3".

  Exemple d'appel

  {"name": "compare_maximo_versions", "arguments": {"to": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• corpus_stats≈ 77 tokens

  Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "corpus_stats", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• deprecation_register≈ 135 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • kind · string · optionnel
    Optional: DEPRECATION, REMOVAL or RENAME.

  Exemple d'appel

  {"name": "deprecation_register", "arguments": {"kind": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• fixes_gained≈ 183 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · requis
    Target release, e.g. "9.2".
  • area · string · optionnel
    Optional functional area, e.g. "WORK_ORDERS".
  • from · string · requis
    Source release, e.g. "9.1".
  • limit · number · optionnel
    Max entries per section (default 40, max 200).

  Exemple d'appel

  {"name": "fixes_gained", "arguments": {"to": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_record≈ 101 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Record slug from search_records / lookup_error_code results.

  Exemple d'appel

  {"name": "get_record", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lifecycle_dates≈ 168 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • product · string · optionnel
    Optional product substring, e.g. "Application Suite" or "Asset Management".
  • version · string · optionnel
    Optional version, e.g. "8.11", "7.6.1", "9.0".

  Exemple d'appel

  {"name": "lifecycle_dates", "arguments": {"product": "texte", "version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_gotchas≈ 123 tokens

  Known traps, upgrade landmines, installation issues, security and troubleshooting records — optionally scoped to a version. Same data as assetize.com.au/gotchas.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
    Max results (default 30, max 100).
  • version · string · optionnel
    Optional version, e.g. "9.2".

  Exemple d'appel

  {"name": "list_gotchas", "arguments": {"limit": 1, "version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_error_code≈ 95 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • code · string · requis
    The error/fix code, e.g. "BMXAA4214E".

  Exemple d'appel

  {"name": "lookup_error_code", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• maximo_changelog≈ 220 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "maximo_changelog", "arguments": {"type": "texte", "limit": 1, "version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• maximo_mobile≈ 285 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "maximo_mobile", "arguments": {"topic": "texte", "version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• records_by_version≈ 128 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
    Max results (default 40, max 200).
  • version · string · requis
    Version label or family, e.g. "9.2".

  Exemple d'appel

  {"name": "records_by_version", "arguments": {"version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_records≈ 152 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "search_records", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• support_lifecycle≈ 141 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
    Max results (default 30).
  • version · string · optionnel
    Optional version, e.g. "8.11", "9.0".

  Exemple d'appel

  {"name": "support_lifecycle", "arguments": {"limit": 1, "version": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• test_automation_script_evidence≈ 317 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • lens · string · requis · 761 | mas811 | mas90 | mas91 | mas92
    The target release lens.
  • source · string · requis
    The Automation Script source — Jython or JavaScript, a WORKORDER Object launch point. Up to 64 KiB.

  Exemple d'appel

  {"name": "test_automation_script_evidence", "arguments": {"lens": "761", "source": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• upgrade_checklist≈ 184 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • to · string · requis
    Target release, e.g. "9.2".
  • from · string · requis
    Source release, e.g. "8.11".
  • phase · string · optionnel
    Optional: BEFORE, DURING or AFTER.

  Exemple d'appel

  {"name": "upgrade_checklist", "arguments": {"to": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• upgrade_plan≈ 280 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • to · string · requis
    Target release: "8.11", "9.0", "9.1", "9.2".
  • from · string · requis
    Source release: "7.6.1", "8.11", "9.0", "9.1".

  Exemple d'appel

  {"name": "upgrade_plan", "arguments": {"to": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://assetize.com.au/mcp