Remote MCP · Endpoint

ERP Facts MCP server

No. ERP Facts answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://erp-mcp.jaikin.eu/mcp

The last check completed an MCP handshake.

Registry name
eu.jaikin/erp-facts
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
424 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Sourced, dated ERP facts: Odoo 20 changes, support deadlines, prices, e-invoicing status.
Listing
From the official MCP registry (active).
Recent checks of ERP Facts
CheckedResultHandshake
1 hour agoHandshake completed424 ms
2 days agoHandshake completed41 ms
4 days agoHandshake completed60 ms
6 days agoHandshake completed305 ms
7 days agoHandshake completed288 ms
9 days agoHandshake completed81 ms
10 days agoHandshake completed303 ms
11 days agoHandshake completed255 ms
14 days agoHandshake completed442 ms
15 days agoHandshake completed390 ms
17 days agoHandshake completed409 ms
18 days agoHandshake completed212 ms
19 days agoHandshake completed307 ms
20 days agoHandshake completed517 ms
21 days agoHandshake completed228 ms
21 days agoHandshake completed506 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 ERP Facts and makes no claim about it beyond what these checks measured.