Is the Com Assetize Maximo MCP server down?

mcp-registry/au.com.assetize/maximo · v1.0.0

As of 2026-10-26 23:02 UTC, the Com Assetize Maximo MCP server is up (it requires sign-in) with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 6 hours.

Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.

Point your MCP client at this streamable-http endpoint: https://assetize.com.au/mcp

Agent-readiness: B (80/100)

What to fix (5)

Auto-fix: 11 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fau.com.assetize%2Fmaximo/fixes

{
  "name": "compare_maximo_versions",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "from",
      "to"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "Target version, e.g. \"9.2\"."
      },
      "from": {
        "type": "string",
        "description": "Starting version, e.g. \"7.6.1.3\"."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Compare two Maximo versions"
}

{
  "name": "corpus_stats",
  "description": "Coverage / transparency stats for the Assetize corpus: published records, unique source documents, versions represented, and raw evidence items.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Assetize corpus coverage"
}

{
  "name": "deprecation_register",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "kind": {
        "type": "string",
        "description": "Optional: DEPRECATION, REMOVAL or RENAME."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Deprecation, removal and rename register"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/au.com.assetize/maximo"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/au.com.assetize/maximo"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~3,235 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.93% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• test_automation_script_evidence ~265 tokens
• maximo_mobile ~259 tokens
• change_watch ~254 tokens
• upgrade_plan ~231 tokens
• maximo_changelog ~229 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fau.com.assetize%2Fmaximo.svg)](https://glimind.com/server/mcp-registry%2Fau.com.assetize%2Fmaximo?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fau.com.assetize%2Fmaximo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fau.com.assetize%2Fmaximo.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fau.com.assetize%2Fmaximo.svg
   :target: https://glimind.com/server/mcp-registry%2Fau.com.assetize%2Fmaximo?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d50a9104a000844c…, first seen 2026-10-17, included at leaf 5890 of 76,126. Version history · verify what your client received.

Tools (19)

• ask_maximo
• behaviour_history
• change_watch
• compare_maximo_versions
• corpus_stats
• deprecation_register
• fixes_gained
• get_record
• lifecycle_dates
• list_gotchas
• lookup_error_code
• maximo_changelog
• maximo_mobile
• records_by_version
• search_records
• support_lifecycle
• test_automation_script_evidence
• upgrade_checklist
• upgrade_plan

Compare: most reliable knowledge servers · most reliable data servers · most reliable search servers · most reliable code servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Com Assetize Maximo MCP server down right now?

As of 2026-10-26 23:02 UTC, the Com Assetize Maximo MCP server is up (it requires sign-in) with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 6 hours.

How many tools does Com Assetize Maximo MCP server provide?

Com Assetize Maximo MCP server advertises 19 tools, including ask_maximo, behaviour_history, change_watch, compare_maximo_versions, corpus_stats.

How do I install Com Assetize Maximo MCP server?

Point your MCP client at this streamable-http endpoint: https://assetize.com.au/mcp

Is the Com Assetize Maximo MCP server safe to connect to an AI agent?

Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Com Assetize Maximo MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.