# app.rowb.septic-log/maintenance (remote · septic-log.rowb.app)

Septic maintenance record: log inspections and pump-outs; next due date under EPA intervals. No AI.

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

- remote · `septic-log.rowb.app`: 56/100 (this document), [markdown](https://verifymcp.io/servers/app-rowb-septic-log-maintenance/septic-log.md), [page](https://verifymcp.io/servers/app-rowb-septic-log-maintenance/septic-log)

## Channel facts

- Endpoint: `https://septic-log.rowb.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-01.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 451 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 23% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the app.rowb.septic-log/maintenance MCP server?

app.rowb.septic-log/maintenance is a hosted endpoint at https://septic-log.rowb.app/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.

### Claude

```bash
claude mcp add --transport http app-rowb-septic-log-maintenance 'https://septic-log.rowb.app/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.app-rowb-septic-log-maintenance]
url = "https://septic-log.rowb.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-rowb-septic-log-maintenance": {
      "type": "remote",
      "url": "https://septic-log.rowb.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-rowb-septic-log-maintenance --url 'https://septic-log.rowb.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-rowb-septic-log-maintenance:
    url: "https://septic-log.rowb.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-rowb-septic-log-maintenance": {
      "Transport": "http",
      "Url": "https://septic-log.rowb.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-rowb-septic-log-maintenance -t streamable-http -u 'https://septic-log.rowb.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-rowb-septic-log-maintenance": {
      "type": "http",
      "url": "https://septic-log.rowb.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-30 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-29 (score 55)

First indexed and scored.

## MCP tools (6)

### `check_service_record` (~184 tokens)

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.

Input parameters:

- `as_of` (string): Treat this date as "today" (YYYY-MM-DD) when rejecting future dates and computing the next due date. Defaults to the server date.
- `events` (array, required): 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, slu…

### `get_rules` (~42 tokens)

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.

### `create_site` (~83 tokens)

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

Input parameters:

- `address` (string)
- `household_size` (integer)
- `installed_year` (integer)
- `label` (string): What to call this system, e.g. "Home - 12 Mill Rd".
- `tank_gallons` (number)

### `add_events` (~36 tokens)

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

Input parameters:

- `events` (array, required)
- `site_id` (string, required)

### `get_record_summary` (~45 tokens)

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

Input parameters:

- `site_id` (string, required)

### `request_provider_signoff` (~61 tokens)

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

Input parameters:

- `provider_email` (string)
- `provider_name` (string)
- `site_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-rowb-septic-log-maintenance/septic-log#diagnostics

## Score history

- 2026-10-01: 56
- 2026-09-30: 56
- 2026-09-29: 55

## Common questions

### What is the app.rowb.septic-log/maintenance MCP server?

app.rowb.septic-log/maintenance is an MCP server listed in the public MCP registry as app.rowb.septic-log/maintenance. Septic maintenance record: log inspections and pump-outs; next due date under EPA intervals. No AI. This page covers its hosted endpoint (https://septic-log.rowb.app/mcp).

### Is the app.rowb.septic-log/maintenance MCP server safe to use?

app.rowb.septic-log/maintenance scores 56 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 app.rowb.septic-log/maintenance MCP server expose?

app.rowb.septic-log/maintenance exposes 6 tools: check_service_record, get_rules, create_site, add_events, get_record_summary, request_provider_signoff. Their descriptions and schemas cost roughly 451 tokens of context every time the server is loaded.

### Does the app.rowb.septic-log/maintenance MCP server require authentication?

No. We connected to app.rowb.septic-log/maintenance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the app.rowb.septic-log/maintenance MCP server still maintained?

app.rowb.septic-log/maintenance is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://septic-log.rowb.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-rowb-septic-log-maintenance/septic-log.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-rowb-septic-log-maintenance/septic-log.json
- HTML version of this page: https://verifymcp.io/servers/app-rowb-septic-log-maintenance/septic-log