MESSAGES / METADATA / MCP

Know when it made it.

Verify one attachment from local Messages metadata, without opening the conversation or reading what it contains.

Local only. Metadata only. Read only.

Install the repo, then verify the setup.

Clone the public source first. Run the standard-library checks before you connect the plugin to local Messages metadata.

Install

git clone https://github.com/henryvn27/attachment-proof.git
cd attachment-proof

The clone includes the plugin manifest, MCP configuration, server, and tests.

Verify

python3 -m unittest discover -s tests -v

Once it passes, open the cloned folder as a local Codex plugin. The manifest starts the dependency-free server.

Optional local probe

Use a fixture path when you need to inspect the service directly.

ATTACHMENT_PROOF_DB=/path/to/fixture.db python3 server.py --check

Attachment Proof gives the handoff a stable answer, so a follow-up starts from evidence instead of a guess.

The tool looks for one exact basename in local Messages metadata, then stays honest about what that metadata can and cannot prove.

Read the boundary

Three small moves keep the product useful inside the handoff that already exists.

Ask
Give Codex the exact filename, with an optional thread or time filter.
verify_attachment
Query
Read Messages metadata in SQLite query-only mode. Never open the body or bytes.
metadata_only: true
Decide
Use read, not-sent, not-found, or unknown to choose a truthful next check.
status + interpretation

The integration keeps the useful part and drops the parts that would turn a delivery check into a conversation reader.

INPUTOUTPUT

filename→basename

thread / time→bounded filters

Messages rows→status + timestamps

SQLite query-only. No write path.