Live South African hunting safari species pricing, lodge availability, and instant quote calculator.
https://api.regfarm.co.za/mcpanswered, tools listed
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-11-22 |
| Completed sessions | 100% of our visits in the last 7 days · 100% in the last 30 |
| Handshake latency | median 424 ms, 95th 424 ms |
| Tools listed | 6 |
| Tool contract | f41ab12292a5 — first reading; nothing to compare it against yet |
| Protocol answered | 2025-06-18 |
| Transport | streamable-http |
https://api.regfarm.co.za/sseanswered, tools listed
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-11-22 |
| Completed sessions | 100% of our visits in the last 7 days · 100% in the last 30 |
| Handshake latency | median 1232 ms, 95th 1232 ms |
| Tools listed | 6 |
| Tool contract | f41ab12292a5 — first reading; nothing to compare it against yet |
| Protocol answered | 2024-11-05 |
| Transport | sse |
| Last detail | legacy HTTP+SSE transport |
[](https://referencesource.org/mcp-health/server/za-co-regfarm-regfarm-mcp/)
The badge shows the most recent probe. It is generated from the same file this page is, updates after each day's pass, and needs no key. This entry publishes 2 endpoints, and the badge reports the best result among them — the question a badge answers is whether a client can reach this project at all, and one dead spare URL is not a reason to call the project down. The per-endpoint verdicts are above, each with its own link.
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 day-by-day totals · every server we probe, A–Z · feed.json · licence · corrections and removals: contact@referencesource.org