Protected connection
A normal remote MCP client connects to https://app.boxfetch.ai/api/mcp/standard. It uses MCP Streamable HTTP and follows the OAuth challenge instead of asking for a pasted token.
Model Context Protocol
Connect agents without giving up human control
BoxFetch exposes public discovery for cold start and a protected MCP endpoint for account-bound operation. OAuth consent binds the client to one human, one selected agent, one runtime resource, and the scopes the human approved.
Three planes
Public guidance, app control plane, local runner
boxfetch.ai owns public explanation and setup guidance. app.boxfetch.ai owns accounts, OAuth, consent, acquisition, approvals, entitlement, package delivery, and MCP runtime. After entitlement, the BoxFetch runner executes the delivered kit in the user's environment.
Public bootstrap
https://app.boxfetch.ai/api/mcp/public offers public-safe discovery, provisional agent registration, and claim-status polling. It cannot purchase, read budgets, or return entitled content.
Provider-target execution
After entitlement and package delivery, the BoxFetch runner in the user's environment inspects, plans, pauses for human approval, applies, verifies, produces a redacted receipt, and performs bounded teardown where supported.
Connection flow
OAuth and consent stay human-owned
- Point the MCP client at the protected endpoint with no credential.
- Follow the protected-resource and authorization-server metadata.
- Complete dynamic client registration and PKCE S256.
- Open BoxFetch in the browser for sign-in and human consent.
- Review the unverified client, exact redirect, selected agent, and scopes.
- Initialize the MCP session after the client completes token exchange.
No manual token handoff
The client receives tokens through the back channel. The human never copies an OAuth access token into a prompt, chat, settings field, log, or screenshot.
Authority
Scopes narrow what a connected client can do
The initial protected-resource challenge requests only discover and preview. Broader authority requires a later consent step.
boxfetch:discover- Search buyer-visible listings.
boxfetch:preview- Read public-safe product previews.
boxfetch:quote- Create a current, server-bound quote.
boxfetch:purchase- Request purchases under owner policy.
boxfetch:content- Retrieve entitled content and submit usage feedback.
boxfetch:budget- Read private wallet and configured limit information.
boxfetch:seller- Seller authority retained outside the hosted launch profile.
offline_access is accepted only as OAuth protocol vocabulary. It never grants a BoxFetch tool and is not stored as tool authority.
Approvals
Purchase authority still follows owner policy
OAuth scope does not replace agent status, configured limits, quote validity, idempotency, human approval, or entitlement checks. Each is enforced again at use time.
Revocation
End the connection from the account
A human can revoke the OAuth grant or the selected agent. Revoked authority fails at use time and cannot be restored by a refresh token.
Open agent controlsMachine discovery
Runtime contracts remain on app.boxfetch.ai
These endpoints are public machine contracts. Human-facing guidance remains on this marketing origin.