Repository navigation
The docs stop selling the platform runtime as the MCP surface - #18
Merged
Merged
Conversation
Search and page reads record 1 credit, a connected-app action records 2, a call relayed through a saved MCP server records 1, and a call on your own provider key records nothing. Saving a remote MCP server and running its tools are on Pro; listing, using and removing a saved server stay on every plan, and every other tool runs on credits on every plan. The research tools are a fallback for a client with none, and the page says so, because preferring the client's own search and fetch is what keeps the bill honest.
The tool reference advertised the vault, the sandbox, connected apps, the job executor, remote MCP servers and web search as the hosted MCP surface, and the pricing page priced those calls. They now run on the Proofable platform, not on a connection: the endpoint carries the trust layer, and a call to a runtime tool answers platform_only. The reference, the secrets page, the jobs page, the pricing page and the privacy table all say where the work belongs.
…ope says what it is The public language gate reads every repo, and it flagged 11 findings in these pages plus one in the changelog and one in the instruction string a host reads. Rewritten to the house voice. The OAuth scope table no longer implies a connector can use the vault: the scope is still issued, and it describes stored credentials used by Proofable's own runs.
… at the job tools The unreleased entry sent readers to the MCP tools page for the job tools, which that page no longer lists: jobs run in Proofable. The boundary gets its own entry so the pages below it read in the right order.
The copy gate rejects a body that replays the frontmatter description as a shared four-word sequence, because the page then makes the same claim twice under the H1. My rewrite of that opening line did exactly that. Reworded so the body adds to the subtitle instead of repeating it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The tool reference called itself the complete hosted MCP reference and advertised the vault, the sandbox, connected apps, the job executor, remote MCP servers and web search; the pricing page priced those calls; the secrets and jobs pages taught them over MCP.
They run on the Proofable platform, not on a connection. The reference now documents the trust layer and states the boundary, the secrets page says saving a key is a platform action (a key typed into an app's conversation has already been disclosed to that app), the jobs page says runs live in Proofable, the pricing page stops pricing runtime calls as tools, and the privacy table says which tools a connection carries. Supersedes #17.