Skip to content
SHPBL

The house · Terms

Terms of service

Short, because the product is narrow. Last updated 24 August 2026. Operator: Kenneth E. Sweet Jr., Abilene, Texas, United States. Contact: kennethsweet214@gmail.com. Using the MCP server, the API, or this site means these terms apply to you.

1. What the service is

SHPBL: Repository Audit & Repair is a Model Context Protocol server that audits a Git repository, produces unified-diff repairs, harvests it into a sealed capability ledger, and can open a pull request with the result. The server does deterministic work; the reading and writing of prose is done by your own model, not ours.

2. Keys, tiers, and metering

  • A subscription key is personal to the subscriber. Do not resell or share it; a key that is shared is metered as one key.
  • Each tier carries a monthly allowance and a per-minute call brake, both stated on the access page and in the tool descriptions. Free tools need no key.
  • Refused calls are not charged. Calls accepted and completed are charged, whether or not you act on the result.

3. Your repository

  • You must own the repository you point a tool at, or hold permission from whoever does.
  • Reading tools read. The writing tool writes only when you call it, only on a branch, and delivers a pull request for a human to review and merge. Nothing is merged for you.
  • A repository connection is bound to one key and can be revoked at any time from GitHub, by uninstalling the SHPBL app.
  • You are responsible for reviewing a diff before you apply it. An audit is advice, not a warranty of correctness or of security.

4. Ownership

Your code stays yours. Reports, diffs, and ledger rows the tools produce about your repository are yours to use, publish, or bin — commercially included, no attribution required. The library prose, the method's naming systems, and the server itself remain the operator's; the license governs the written volumes.

5. Acceptable use

Do not use the service against repositories you have no right to, to evade its metering or rate limits, to attack the service or its providers, or to redistribute the library prose in breach of its license. We may suspend a key that does.

6. Availability, changes, and ending it

The service is provided as-is, without warranty of any kind, and the operator's liability is limited to the amount you paid in the current billing period. Tools are added and folded over time; breaking changes are versioned and noted on the release notes. You may cancel at any time and keep access until the period ends. We may end an account for a breach of section 5, or for non-payment.

7. Law

These terms are governed by the laws of the State of Texas, United States.

See also the privacy statement and agent access.