Septic Log MCP

Septic Log is a maintenance record system for septic systems that logs inspections, pump-outs, and repairs. It validates data integrity, computes next service windows based on US EPA intervals, and generates printable records for homeowners and service providers.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Septic Log

You need:a bearer key is required for anything that writes to your own record

MCP endpoint (Streamable HTTP)

https://septic-log.rowb.app/mcp

Vendor documentation

What its tools do

6 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (6)

check_service_record
get_rules
create_site
add_events
get_record_summary
request_provider_signoff

6 of 6 have a description · 0 of 6 declare behavior hints · 1 of 5 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 7, 2026, 12:01 AM UTC
Passed Official MCP Registry namespace is tied to septic-log.rowb.app · Nov 6, 2026, 11:30 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 6, 2026, 11:30 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Log septic system inspections and pump-outs
Compute next inspection and pump-out dates using EPA intervals
Record sludge and scum levels measured by service providers
Generate printable A4 maintenance records with provider signature lines

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: app.rowb.septic-log/maintenance@1.0.0

Protocol and capabilities

Server: septic-log 1.0.0
MCP protocol negotiated in check: 2025-06-18
Tools: 6 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Tools

6 advertised

check_service_record

Advertised by the server during the last successful anonymous check.

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.

check_service_record input schema

{
  "type": "object",
  "required": [
    "events"
  ],
  "properties": {
    "as_of": {
      "type": "string",
      "description": "Treat this date as \"today\" (YYYY-MM-DD) when rejecting future dates and computing the next due date. Defaults to the server date."
    },
    "events": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Events to check. Each: {date:\"YYYY-MM-DD\", kind:\"inspection|pump_out|repair|other\", company:\"who did it\", gallons?:number, liquid_depth_inches?:number, sludge_inches?:number, scum_inches?:number, sludge_to_outlet_inches?:number, scum_to_outlet_inches?:number, notes?:string}."
    }
  }
}

get_rules

Advertised by the server during the last successful anonymous check.

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.

get_rules input schema

{
  "type": "object",
  "properties": {}
}

create_site

Advertised by the server during the last successful anonymous check.

Open a maintenance record for one septic system (returns a site id). Requires a bearer key.

create_site input schema

{
  "type": "object",
  "required": [],
  "properties": {
    "label": {
      "type": "string",
      "description": "What to call this system, e.g. \"Home - 12 Mill Rd\"."
    },
    "address": {
      "type": "string"
    },
    "tank_gallons": {
      "type": "number"
    },
    "household_size": {
      "type": "integer"
    },
    "installed_year": {
      "type": "integer"
    }
  }
}

add_events

Advertised by the server during the last successful anonymous check.

Append service events to an existing record. Requires a bearer key.

add_events input schema

{
  "type": "object",
  "required": [
    "site_id",
    "events"
  ],
  "properties": {
    "events": {
      "type": "array",
      "items": {
        "type": "object"
      }
    },
    "site_id": {
      "type": "string"
    }
  }
}

get_record_summary

Advertised by the server during the last successful anonymous check.

Every event, the flagged issues, the last inspection and pump-out, and the next dates, for one record. Requires a bearer key.

get_record_summary input schema

{
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "site_id": {
      "type": "string"
    }
  }
}

request_provider_signoff

Advertised by the server during the last successful anonymous check.

Create a one-time URL the service provider can open to confirm the recorded work. Requires a bearer key. The token is single use.

request_provider_signoff input schema

{
  "type": "object",
  "required": [
    "site_id"
  ],
  "properties": {
    "site_id": {
      "type": "string"
    },
    "provider_name": {
      "type": "string"
    },
    "provider_email": {
      "type": "string"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 684 ms
95th percentile latency: 684 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 7, 2026, 12:01 AM UTC · probe · passed · 684 ms · metadata changed · 6 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http septic-log-mcp https://septic-log.rowb.app/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add septic-log-mcp --url https://septic-log.rowb.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable septic-log-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "septic-log-mcp": {
      "url": "https://septic-log.rowb.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "septic-log-mcp": {
      "type": "streamableHttp",
      "url": "https://septic-log.rowb.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start septic-log-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "septic-log-mcp": {
      "type": "http",
      "url": "https://septic-log.rowb.app/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http septic-log-mcp https://septic-log.rowb.app/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://septic-log.rowb.app/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "septic-log-mcp": {
      "serverUrl": "https://septic-log.rowb.app/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Septic Log MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run Septic Log MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing