Servidor MCP de Assetize

• Nombre en el registroau.com.assetize/maximoverificado en el registro MCP

El nombre en el registro está bajo assetize.com.au. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-19
• Herramientas19
• El servidor se llamaassetize-maximo
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

El 2026-10-19 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 466 ms.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 8 hasta ahora
• Respondióel 100% de los días8 de 8 comprobaciones diarias
• Mediana de la primera respuesta2068 ms
• Inicio de sesiónuna clave que pegas tú

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• 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…

• search_records

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

• lookup_error_code

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

• get_record

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

• 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…

• 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)…

• 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…

• list_gotchas

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

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

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

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

• corpus_stats

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

• 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…

• 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…

• 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…

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

• 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…

• 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…

• 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…