Skip to content

Changelog and trust skill for the launch tool boundary #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chrisjleal merged 3 commits into from
Oct 25, 2026
Merged

Changelog and trust skill for the launch tool boundary #10

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cd381b0
The changelog says the vault left the connection, and nothing else did
chrisjleal Oct 25, 2026
4db5631
A connection that is not offered a tool is told so in the words it gets
chrisjleal Oct 25, 2026
41a31ce
The changelog says one tool moved to the profile
chrisjleal Oct 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ Product release notes: [docs.proofable.me/changelog](https://docs.proofable.me/c

### Changed

- **The hosted surface carries the trust layer.** `https://mcp.proofable.me/mcp` serves the proof and permission tools (prove something once, reuse the proof, hold an agent to a permission you can revoke), and no longer serves work that runs on the Proofable platform: background and scheduled jobs, the hosted browser, connected apps, a saved provider key, remote MCP servers, web search and page fetch, or the encrypted vault. Those run in Proofable itself, where the run holds its own permission and a human approves side effects; a call to one from a connection answers `platform_only`. Saving or revoking a key happens on your profile, so a credential is never passed through a client. `tools/list` and the published card both stop at the trust layer.
- **Saving a key moves to your profile.** `https://mcp.proofable.me/mcp` no longer accepts a key as a tool argument: `tools/list` does not offer the tool that saved one, and a call to it is rejected as an unknown tool, so a credential is never passed through a client. Every other tool stays on every plan for a signed-in connection, on your credits and within your permissions: the proof and permission tools, jobs, the hosted browser, connected apps, remote MCP servers, session notes, saved tools, web search, page fetch, and your saved keys (list, remove, or call a provider with one, never reading the key back). The published card lists twelve tools and no vault tool.

- **Dedicated ChatGPT plugin endpoint.** The ChatGPT plugin connects to `https://mcp.proofable.me/mcp/openai`, which serves the eight read and guided-verification tools with the same OAuth sign-in; `proofable_verify_or_guide` returns the hosted link whenever a verification step is needed. Cursor, Claude Code, Codex, and every other client see the trust-layer tool list on `/mcp`.
- **Dedicated ChatGPT plugin endpoint.** The ChatGPT plugin connects to `https://mcp.proofable.me/mcp/openai`, which serves the eight read and guided-verification tools with the same OAuth sign-in; `proofable_verify_or_guide` returns the hosted link whenever a verification step is needed. Cursor, Claude Code, Codex, and every other client get the full tool list on `/mcp`.

## [0.1.7] - 2026-10-10

Expand Down
2 changes: 1 addition & 1 deletion plugins/proofable-mcp/skills/proofable-trust-workflow/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Proofable: Blocked. A required trust condition was not satisfied. Next: Do not c

- Proofs stay off the chain unless the user asks for a blockchain record. Do not prompt for a wallet otherwise.
- Use proof IDs only from tool responses. Prefer “proof ID” / “portable proof” in user text.
- Never ask for a credential and never accept one. A key is saved on the profile in Proofable, where a run uses it without the value reaching a model or an app. This connection carries no tool that stores a secret; a call to one answers `platform_only`.
- Never ask for a credential and never accept one. A key is saved on the profile in Proofable, where a run uses it without the value reaching a model or an app. This connection carries no tool that stores a secret.
- Use live verifier IDs from **`proofable_context`** / **`proofable_verifiers_catalog`**. Do not hardcode a second catalog.

## Setup and mount
Expand Down
2 changes: 1 addition & 1 deletion skills/proofable-trust-workflow/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Proofable: Blocked. A required trust condition was not satisfied. Next: Do not c

- Proofs stay off the chain unless the user asks for a blockchain record. Do not prompt for a wallet otherwise.
- Use proof IDs only from tool responses. Prefer “proof ID” / “portable proof” in user text.
- Never ask for a credential and never accept one. A key is saved on the profile in Proofable, where a run uses it without the value reaching a model or an app. This connection carries no tool that stores a secret; a call to one answers `platform_only`.
- Never ask for a credential and never accept one. A key is saved on the profile in Proofable, where a run uses it without the value reaching a model or an app. This connection carries no tool that stores a secret.
- Use live verifier IDs from **`proofable_context`** / **`proofable_verifiers_catalog`**. Do not hardcode a second catalog.

## Setup and mount
Expand Down
Loading