BadBuddy
REMOTE · WWW.BADBUDDY.CO.NZ
Find public badminton activities and venues in New Zealand through a read-only MCP server.
Available components
Last scanned (18 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 10 Oct 2026.
Category Entertainment and Games
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 −2
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 −2
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Oct 26 −2
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Oct 26 −2
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Oct 26 −2
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Oct 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- DNSSEC: fail → unverified ▼ security
- Authorization: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 10 Oct 26 −8
- Endpoint reachability: unreachable → behind authorisation ▼ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 4 Oct 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → fail ▼ security
- TLS certificate: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://www.badbuddy.co.nz/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of www.badbuddy.co.nz. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| www.badbuddy.co.nz. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.badbuddy.co.nz/mcp | Unreachable | ||
| http (plaintext) | http://www.badbuddy.co.nz/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_activity ~33
Get the complete public details of one BadBuddy activity by ID. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Activity ID. |
No output schema declared.
No examples provided.
list_activities ~76
List today's and future BadBuddy activities. Optional filters: city, venue ID, date, and status. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Optional city name. |
| date | string | – | Optional date in YYYY-MM-DD format. |
| status | string | – | – |
| venueId | integer | – | Optional numeric venue ID. |
No output schema declared.
No examples provided.
list_venues ~21
List BadBuddy venues available to public users. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the BadBuddy MCP server?
BadBuddy is a hosted endpoint at https://www.badbuddy.co.nz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.badbuddy.co.nz
claude mcp add --transport http nz-co-badbuddy-www-mcp 'https://www.badbuddy.co.nz/mcp'
What is the BadBuddy MCP server?
BadBuddy is an MCP server listed in the public MCP registry as nz.co.badbuddy.www/mcp. Find public badminton activities and venues in New Zealand through a read-only MCP server. This page covers its hosted endpoint (https://www.badbuddy.co.nz/mcp).
Is the BadBuddy MCP server safe to use?
BadBuddy scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BadBuddy MCP server expose?
BadBuddy exposes 3 tools: list_activities, get_activity, list_venues. Their descriptions and schemas cost roughly 130 tokens of context every time the server is loaded.
Does the BadBuddy MCP server require authentication?
Its publisher declares no required credentials for BadBuddy. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the BadBuddy MCP server still maintained?
BadBuddy has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 10 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.