maintenance MCP server
app.rowb.septic-log/maintenanceseptic-log.rowb.appstreamable-httpv1.0.0Scanned
Septic maintenance record: log inspections and pump-outs; next due date under EPA intervals. No AI.
6 tools: 4 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the maintenance MCP server can do
The maintenance MCP server is published by septic-log.rowb.app, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: check_service_record, create_site, add_events and request_provider_signoff), but cannot delete data. 2 tools only read.
1 tool reads private data (get_rules); 1 tool brings in text other people can write (get_record_summary).
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 17, 2026, version 1.0.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.
6 tools
Changes things 4Claude Code: ask
add_eventsAppend service events to an existing record.No findings
Why it is in this group
- The name "add_events" says "add": a word for a change.
Description, as the server wrote it Append service events to an existing record. Requires a bearer key.
check_service_recordCheck a list of septic system service events for things that cannot be true, and compute the next inspection and pump-out window from the intervals published by the US EPA.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Check a list of septic system service events for things that cannot be true, and compute the next inspection and pump-out window from the intervals published by the US EPA. Deterministic arithmetic only - no AI. It does not judge whether your system is compliant, and it does not know your local code.
create_siteOpen a maintenance record for one septic system (returns a site id).No findings
Why it is in this group
- The name "create_site" says "create": a word for a change.
Description, as the server wrote it Open a maintenance record for one septic system (returns a site id). Requires a bearer key.
request_provider_signoffCreate a one-time URL the service provider can open to confirm the recorded work.No findings
Why it is in this group
- The name "request_provider_signoff" says "request": a word for a change.
Description, as the server wrote it Create a one-time URL the service provider can open to confirm the recorded work. Requires a bearer key. The token is single use.
Only reads 2Show 2 read-only tools
get_record_summaryEvery event, the flagged issues, the last inspection and pump-out, and the next dates, for one record.Reads text others writeNo findings
Why it is in this group
- The name "get_record_summary" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
Description, as the server wrote it Every event, the flagged issues, the last inspection and pump-out, and the next dates, for one record. Requires a bearer key.
get_rulesThe exact rule table this service checks against, the quoted source of every interval, and what it explicitly does not claim.Reads private dataNo findings
Why it is in this group
- The name "get_rules" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it The exact rule table this service checks against, the quoted source of every interval, and what it explicitly does not claim. Quote it if you need to explain a result.
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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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, 19:28 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
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://septic-log.rowb.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://septic-log.rowb.app/mcp: tools/list returned 6 tools to an anonymous client, including check_service_record (write), create_site (write), add_events (write), request_provider_signoff (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 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http maintenance https://septic-log.rowb.app/mcpclaude mcp add --transport http maintenance https://septic-log.rowb.app/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__maintenance__get_rules",
"mcp__maintenance__get_record_summary"
],
"ask": [
"mcp__maintenance__check_service_record",
"mcp__maintenance__create_site",
"mcp__maintenance__add_events",
"mcp__maintenance__request_provider_signoff"
],
"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 maintenance. Review it before you use it.
Capability tags behind 2 rules
- mcp__maintenance__get_rules private-data
- mcp__maintenance__get_record_summary 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/app.rowb.septic-log/maintenance/verify?hash=6ea7e257c7fe96bb1fc2e31b6e6d48637c2fb91215d885c0116fcdce1f8d7403" | jq -e '.changed == false'Pinned hash 6ea7e257c7fe, from Nov 17, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.rowb.septic-log/maintenance/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.rowb.septic-log/maintenance)Source: MCP Registry. Synced Oct 21, 2026, 17:45 UTC.
maintenance MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the maintenance MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 4 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 maintenance MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the maintenance 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 maintenance MCP server have?
- 6 tools: 4 write, 2 read. check_service_record, create_site, add_events, request_provider_signoff, get_rules and get_record_summary.
Does the maintenance MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the maintenance MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the maintenance MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.