Remote MCP · Endpoint

fynsight: MCP server for DATEV MCP server

No. fynsight: MCP server for DATEV answered an MCP handshake 29 minutes ago.

UpLast checked 29 minutes ago

Server URL

https://mcp.fynsight.de/mcp

The last check completed an MCP handshake.

Registry name
de.fynsight/datev
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
448 ms
Tools exposed
29 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
DATEV financial data for AI assistants: P&L, KPIs, bookings, budgets and monthly reporting.
Listing
From the official MCP registry (active).
Recent checks of fynsight: MCP server for DATEV
CheckedResultHandshake
29 minutes agoHandshake completed448 ms
10 days agoCredentials required—
11 days agoCredentials required—

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

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 fynsight: MCP server for DATEV and makes no claim about it beyond what these checks measured.