Reference Source · MCP server health

org.crossload/crossload

Christliche Predigten und Bücher auf Deutsch: Volltextsuche, Transkripte, Bibellexikon

One endpoint on the official MCP registry. Probed daily.

https://mcp.crossload.org/mcp

answered, tools listed

Last 30 probes
Last seen healthy2026-10-23
Completed sessions100% of the last 7 probes · 93.1% of the last 30
Handshake latencymedian 598 ms, 95th 3746 ms
Tools listed5
Tool contract3407f7df815b — last moved 2026-10-22 (1 changed in place, against 2026-10-21)
Protocol answered2025-06-18
Transportstreamable-http

Embed the badge

[![MCP](https://referencesource.org/mcp-health/badge/org-crossload-crossload.svg)](https://referencesource.org/mcp-health/server/org-crossload-crossload/)

The badge shows the most recent probe. It is generated from the same file this page is, updates once a day, and needs no key.

What was actually measured

One HTTP POST carrying a JSON-RPC initialize, and if that succeeds, a tools/list. Nothing here is a score, a rating or a judgement about whether the server is any good — only whether an ordinary MCP client could complete a session with it on the day we asked. “Needs credentials” is not a fault: it means the endpoint wants an account, which is a perfectly reasonable thing for it to want.

The tool contract row is a digest of what tools/list returned — each tool's name, description and input schema, hashed — so that a rename, a newly-required field or a rewritten description can be spotted even though none of them breaks the connection. We keep the digests and nothing else: no tool name, description or schema of anybody's is stored or republished here, which is also why this can say that a contract moved and by how much, but not what it now says.

The method and the daily totals · every server we probe, A–Z · feed.json · licence · corrections and removals: [email protected]