Remote MCP · Endpoint

Anwani MCP server

No. Anwani answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://us-central1-nine-code-anwani.cloudfunctions.net/mcpRemote

The last check completed an MCP handshake.

Registry name
io.github.Anwani-app/anwani-mcp
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
69 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Anwani MCP: create and manage permanent 9-digit address codes through OAuth (9code.app).
Listing
From the official MCP registry (active).
Recent checks of Anwani
CheckedResultHandshake
13 minutes agoHandshake completed69 ms
9 days agoHandshake completed217 ms
9 days agoHandshake completed132 ms
11 days agoHandshake completed109 ms
12 days agoHandshake completed58 ms
13 days agoHandshake completed57 ms
14 days agoHandshake completed68 ms
14 days agoHandshake completed50 ms
16 days agoHandshake completed72 ms
19 days agoHandshake completed59 ms
21 days agoHandshake completed60 ms
24 days agoHandshake completed54 ms
26 days agoHandshake completed64 ms
28 days agoHandshake completed94 ms

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

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