gripe-mcp
Agent complaint box — one-tool MCP for logging bugs and improvement requests.
One tool: report_issue
Call it when you guess, hit a missing tool, find bad docs, or produce uncertain output. Non-blocking — log and continue.
| Param | Type | Description |
|---|---|---|
description |
str | What went wrong or what you'd like improved (max 200 chars) |
severity |
low / medium / high |
low = friction, medium = guessed, high = abandoned/wrong |
section |
str | Which instruction or tool caused the issue (max 80 chars) |
mode |
enum | ambiguous_instruction missing_tool bad_tool_doc hallucination_risk wrong_scope memory_miss other |
Storage
- Postgres: set
GRIPE_DB_URLenv var → singlegripe_issuestable - JSONL fallback: timestamped files in
.gripe-mcp/(one per day)
Identity
GRIPE_AGENT_ID and GRIPE_TASK_ID are set at server startup via env vars.
The agent never self-reports identity.
System prompt block
## Self-Monitoring
Use `report_issue` any time you guess, hit a missing tool, or produce output
you're uncertain about. Non-blocking — log and continue, no response expected.
There is no penalty for logging; silence is the failure mode we're trying to
prevent.
Run
GRIPE_AGENT_ID=precis GRIPE_TASK_ID=review-123 gripe
1 maintainer
Metadata
1 maintainer
Release files for gripe-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gripe_mcp-0.1.2.tar.gz | 9.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gripe_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.8 kB
Release files / gripe_mcp-0.1.2.tar.gz
| Download URL | gripe_mcp-0.1.2.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa0ce3bf38abb1ec1bcc64d3e905dd0051d83899899a7697ad7376a6bf2880a4
|
|
BLAKE2b-256 checksum How to use checksums |
3bbd967fba1a6656754038014690033b56596a673e7b969d10a86e6ea0b1843a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 7, 2026.
Transparency logRelease files / gripe_mcp-0.1.2-py3-none-any.whl
| Download URL | gripe_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27c7927b6de2c6d98bb660d0e5b1f2f345f2b25b2bc642b8ab7d27a485fa54b1
|
|
BLAKE2b-256 checksum How to use checksums |
52ab216f3efc27a5a7c71779fbae422f47b0c0f88ee56155c13cd54480a59b14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 7, 2026.
Transparency logSecurity for gripe-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for gripe_mcp-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
