Remote MCP · Endpoint

async.elixirconf MCP server

No. async.elixirconf answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://async.elixirconf.com/mcp

The last check completed an MCP handshake.

Registry name
com.elixirconf/async
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
170 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
ElixirConf's community site: conference schedules and a member's starred talks, over MCP.
Website
https://async.elixirconf.com/developers
Listing
From the official MCP registry (active).
Recent checks of async.elixirconf
CheckedResultHandshake
1 hour agoHandshake completed170 ms
2 days agoHandshake completed173 ms
4 days agoHandshake completed134 ms
5 days agoHandshake completed140 ms
7 days agoHandshake completed136 ms
8 days agoHandshake completed646 ms
9 days agoHandshake completed196 ms
12 days agoHandshake completed143 ms
13 days agoHandshake completed204 ms
15 days agoHandshake completed332 ms
16 days agoHandshake completed200 ms
17 days agoHandshake completed144 ms
18 days agoHandshake completed140 ms
19 days agoHandshake completed173 ms
20 days agoHandshake completed273 ms
21 days agoHandshake completed174 ms
22 days agoHandshake completed97 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with async.elixirconf and makes no claim about it beyond what these checks measured.