Remote MCP · Endpoint

Assetize — IBM Maximo knowledge MCP server

No. Assetize — IBM Maximo knowledge answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://assetize.com.au/mcp

The last check completed an MCP handshake.

Registry name
au.com.assetize/maximo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
619 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Cited IBM Maximo and MAS answers: upgrades, error codes, gotchas, versions and lifecycle.
Listing
From the official MCP registry (active).
Recent checks of Assetize — IBM Maximo knowledge
CheckedResultHandshake
35 minutes agoHandshake completed619 ms
9 days agoHandshake completed1.87 s
10 days agoHandshake completed2.18 s
11 days agoHandshake completed532 ms
12 days agoHandshake completed2.58 s
14 days agoHandshake completed2.77 s
14 days agoHandshake completed603 ms
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
21 days agoHandshake completed716 ms
24 days agoHandshake completed2.06 s
26 days agoHandshake completed1.70 s
28 days agoHandshake completed583 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 28.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Assetize — IBM Maximo knowledge and makes no claim about it beyond what these checks measured.