Remote MCP · Endpoint

Neumann MCP server

No. Neumann answered an MCP handshake 8 days ago.

UpLast checked 8 days ago

Server URL

https://neumann.kromatic.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Kromatic-Innovation/neumann
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 9 checks
Described by its publisher as
Monte Carlo ranges for uncertain plans: project cost, budget, timeline, capacity, NPV/IRR/payback.
Listing
From the official MCP registry (active).
Recent checks of Neumann
CheckedResultHandshake
8 days agoHandshake completed76 ms
8 days agoHandshake completed39 ms
9 days agoHandshake completed40 ms
11 days agoHandshake completed109 ms
12 days agoHandshake completed40 ms
13 days agoHandshake completed48 ms
14 days agoHandshake completed44 ms
15 days agoHandshake completed36 ms
17 days agoHandshake completed57 ms

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

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 Neumann and makes no claim about it beyond what these checks measured.