Remote MCP · Endpoint

Behavior Trees MCP server

No. Behavior Trees answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://www.behaviortrees.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.behaviortrees/behaviortrees
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 5 checks
Described by its publisher as
Validate, convert (behavior3 JSON, BehaviorTree.CPP XML) and open behavior trees in a visual editor
Listing
From the official MCP registry (active).
Recent checks of Behavior Trees
CheckedResultHandshake
52 minutes agoHandshake completed85 ms
3 days agoHandshake completed55 ms
12 days agoHandshake completed107 ms
13 days agoHandshake completed117 ms
14 days agoHandshake completed140 ms

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

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