Remote MCP · Endpoint

io.github.pooriaarab/doulas MCP server

No. io.github.pooriaarab/doulas answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://doulas.fyi/mcp

The last check completed an MCP handshake.

Registry name
io.github.pooriaarab/doulas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
134 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Find a birth, postpartum or end-of-life doula near you.
Repository
https://github.com/pooriaarab/directory
Listing
From the official MCP registry (active).
Recent checks of io.github.pooriaarab/doulas
CheckedResultHandshake
4 days agoHandshake completed134 ms
4 days agoHandshake completed2.24 s
5 days agoHandshake completed122 ms
7 days agoHandshake completed134 ms
8 days agoHandshake completed133 ms
9 days agoHandshake completed133 ms
10 days agoHandshake completed143 ms
11 days agoHandshake completed229 ms
12 days agoHandshake completed862 ms
15 days agoHandshake completed366 ms
18 days agoHandshake completed2.37 s
20 days agoHandshake completed1.09 s

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

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 io.github.pooriaarab/doulas and makes no claim about it beyond what these checks measured.