Remote MCP · Endpoint

Entity Enricher MCP server

No. Entity Enricher answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://entityenricher.ai/api/mcp/

The last check completed an MCP handshake.

Registry name
ai.entityenricher/enricher
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
453 ms
Tools exposed
62 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Multi-LLM entity enrichment: schemas, single/batch enrichment, fusion, model benchmarks.
Listing
From the official MCP registry (active).
Recent checks of Entity Enricher
CheckedResultHandshake
43 minutes agoHandshake completed453 ms
10 days agoHandshake completed478 ms
10 days agoHandshake completed799 ms
11 days agoHandshake completed468 ms
12 days agoHandshake completed475 ms
14 days agoHandshake completed462 ms
14 days agoHandshake completed458 ms
15 days agoHandshake completed458 ms
17 days agoHandshake completed467 ms
19 days agoHandshake completed462 ms
21 days agoHandshake completed467 ms
24 days agoHandshake completed507 ms
26 days agoHandshake completed523 ms
28 days agoHandshake completed452 ms

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

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