CampWatch MCP server
au.com.campwatch/campwatchcampwatch.com.austreamable-httpv0.4.0Scanned
Australian campground search, availability and phone-linked alerts using existing credits.
10 tools: 5 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 10
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CampWatch MCP server can do
The CampWatch MCP server is published by campwatch.com.au, a domain the MCP Registry verified. It has 10 tools. It can create or change data (5 tools: check_availability, enable_sms_alerts, create_alert, stop_alert and 1 more), but cannot delete data. 5 tools only read.
10 tools bring in text other people can write (find_campgrounds, list_providers, check_availability and 7 more); 1 tool can send data out of your system (enable_sms_alerts).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Changes things 5Claude Code: ask
check_availabilityCheck current availability for a campground, dates and party size.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check current availability for a campground, dates and party size. A result is a snapshot; errors do not prove no availability.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
create_alertCreate an SMS/push alert after the user approves target, dates and party size.Reads text others writeNo findings
Why it is in this group
- The name "create_alert" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Create an SMS/push alert after the user approves target, dates and party size. Use a new idempotencyKey for each intended alert; reuse it on retries. Available-now results can consume an alert credit under CampWatch's existing rules.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
enable_sms_alertsEnable SMS delivery for all alerts on the connected account, only after the user approves SMS notification intent.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "enable_sms_alerts" says "enable": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "enable_sms_alerts" says "enable" and "sms": it writes something other people read.
Description, as the server wrote it Enable SMS delivery for all alerts on the connected account, only after the user approves SMS notification intent. New phone-linked accounts have no delivery channel until configured. This preserves push settings and never starts a purchase.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
reactivate_alertReactivate a stopped alert owned by the connected account.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Reactivate a stopped alert owned by the connected account.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
stop_alertStop one alert owned by the connected account.Reads text others writeNo findings
Why it is in this group
- The name "stop_alert" says "stop": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Stop one alert owned by the connected account. It can be reactivated.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 5Show 5 read-only tools
credit_balanceRead the connected account's free and purchased alert credits.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Read the connected account's free and purchased alert credits.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
credit_historyRead the connected account's credit ledger.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Read the connected account's credit ledger.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
find_campgroundsSearch CampWatch's supported Australian campground catalogue.Reads text others writeNo findings
Why it is in this group
- The name "find_campgrounds" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search CampWatch's supported Australian campground catalogue. Use returned provider and slug for availability and alerts.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_alertsList the connected account's alerts.Reads text others writeNo findings
Why it is in this group
- The name "list_alerts" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the connected account's alerts. Default is active; pass ACTIVE,STOPPED,EXPIRED to see all.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_providersList supported booking systems and regions.Reads text others writeNo findings
Why it is in this group
- The name "list_providers" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List supported booking systems and regions.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write10
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:30 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.campwatch.com.au/.well-known/oauth-protected-resource
- Authorization servers
- https://www.campwatch.com.au
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.campwatch.com.au/mcp: tools/list returned 10 tools to an anonymous client, including check_availability (write), enable_sms_alerts (write), create_alert (write), stop_alert (write), reactivate_alert (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http campwatch https://www.campwatch.com.au/mcpclaude mcp add --transport http campwatch https://www.campwatch.com.au/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__campwatch__find_campgrounds",
"mcp__campwatch__list_providers",
"mcp__campwatch__list_alerts",
"mcp__campwatch__credit_balance",
"mcp__campwatch__credit_history"
],
"ask": [
"mcp__campwatch__check_availability",
"mcp__campwatch__enable_sms_alerts",
"mcp__campwatch__create_alert",
"mcp__campwatch__stop_alert",
"mcp__campwatch__reactivate_alert"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as campwatch. Review it before you use it.
Capability tags behind 10 rules
- mcp__campwatch__find_campgrounds untrusted-input
- mcp__campwatch__list_providers untrusted-input
- mcp__campwatch__check_availability untrusted-input
- mcp__campwatch__list_alerts untrusted-input
- mcp__campwatch__enable_sms_alerts untrusted-input, outbound
- mcp__campwatch__create_alert untrusted-input
- mcp__campwatch__stop_alert untrusted-input
- mcp__campwatch__reactivate_alert untrusted-input
- mcp__campwatch__credit_balance untrusted-input
- mcp__campwatch__credit_history untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/au.com.campwatch/campwatch/verify?hash=3b25711b526214b167a25eb328a3f3eda04bf460f81ca30577d1a8403bd4e429" | jq -e '.changed == false'Pinned hash 3b25711b5262, from Nov 12, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/au.com.campwatch/campwatch/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/au.com.campwatch/campwatch)Source: MCP Registry. Synced Oct 21, 2026, 17:45 UTC.
CampWatch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CampWatch MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CampWatch MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CampWatch MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CampWatch MCP server have?
- 10 tools: 5 write, 5 read. check_availability, enable_sms_alerts, create_alert, stop_alert, reactivate_alert, find_campgrounds, list_providers, list_alerts and 2 more.
Does the CampWatch MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CampWatch MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): enable_sms_alerts.
Has the CampWatch MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.