Remote MCP · Endpoint

Omie MCP server

No. Omie answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://api.mcp.ai/p_omie

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/omie-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
53 ms
Tools exposed
59 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Financial & accounting management on Omie (Brazil's leading cloud ERP), payables/receivables, financ
Listing
From the official MCP registry (active).
Recent checks of Omie
CheckedResultHandshake
2 days agoHandshake completed53 ms
4 days agoHandshake completed200 ms
5 days agoHandshake completed103 ms
7 days agoHandshake completed214 ms
8 days agoHandshake completed49 ms
9 days agoHandshake completed39 ms
12 days agoHandshake completed59 ms
13 days agoHandshake completed31 ms
15 days agoHandshake completed68 ms
17 days agoHandshake completed185 ms
18 days agoHandshake completed89 ms
19 days agoHandshake completed162 ms
20 days agoHandshake completed62 ms
20 days agoHandshake completed93 ms
21 days agoHandshake completed367 ms
23 days agoHandshake completed87 ms

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

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