Remote MCP server for septic system maintenance records: log service events, flag impossible entries, and compute next inspection and pump-out dates from EPA…
What you can do
Check service events for entries that cannot be true and compute the next inspection and pump-out window from published EPA intervals
Read the exact rule table, quoted interval sources, and stated limits of the checks
Create a maintenance record for one septic system and get a site id
Append service events to an existing record
Summarize a record: all events, flagged issues, last inspection and pump-out, and next dates
Create a single-use link for the service provider to confirm the recorded work
When to use it
Useful if you keep track of a septic system and want an assistant to log inspections and pump-outs, sanity-check the dates, and tell you when the next service is due. Also handy for explaining a result by quoting the rule table it was checked against.
Requirements
A remote MCP endpoint at septic-log.rowb.app over streamable HTTP; no packages or environment variables are declared. The record tools (create_site, add_events, get_record_summary, request_provider_signoff) require a bearer key, which the manifest does not list as a declared credential.
Before you install
Four tools require a bearer key, so you must supply a credential the manifest does not describe; keep it private. Creating records, appending events, and generating provider sign-off links all write data, and the sign-off link is single use and grants the provider access to confirm work. The checks are deterministic arithmetic against EPA intervals and do not judge local code compliance.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.rowb.septic-log%2Fmaintenance/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parametersas_ofeventsrequired
get_rules
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.
Takes no parameters.
create_site
Open a maintenance record for one septic system (returns a site id). Requires a bearer key.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.