Remote MCP · Endpoint

dev.mearef/reference-data MCP server

No. dev.mearef/reference-data answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mearef.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.mearef/reference-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.05 s
Tools exposed
22 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Mid-East govt data, cited to source: rates, VAT, tax, wages, holidays, FX. 9 countries; UAE free.
Website
https://mearef.dev/
Listing
From the official MCP registry (active).
Recent checks of dev.mearef/reference-data
CheckedResultHandshake
1 hour agoHandshake completed1.05 s
2 days agoHandshake completed994 ms
4 days agoHandshake completed1.00 s
5 days agoHandshake completed1.06 s
7 days agoHandshake completed1.02 s
8 days agoHandshake completed1.03 s
9 days agoHandshake completed945 ms
12 days agoHandshake completed1.02 s
13 days agoHandshake completed976 ms
15 days agoHandshake completed1.02 s
16 days agoHandshake completed991 ms
18 days agoHandshake completed999 ms
19 days agoHandshake completed1.01 s
20 days agoHandshake completed1.01 s
20 days agoHandshake completed1.01 s
21 days agoHandshake completed1.01 s
22 days agoHandshake completed1.10 s

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 dev.mearef/reference-data and makes no claim about it beyond what these checks measured.