There is no live TrueFetch MCP endpoint to install or authorize yet. Do not paste a guessed server URL or credentials into a client. Release status will identify when access opens.
One task contract
REST and MCP are designed to expose the same operations, source restrictions, outcomes and billing rules. A model choosing a tool does not grant unlimited spending permission. Requests must stay within authorized scope and budget, and incomplete source coverage must remain visible in the result.
Long-running operations return a task handle. The client should follow that handle instead of repeatedly creating work. Retrieved web content is untrusted data, not instructions that can authorize other tools or change an account’s permissions.
Custom connections and directories
Custom server connections and a host’s official directory are separate routes. Instructions will identify the exact host, supported version, authentication flow and tested tasks before a connection is labeled verified. Directory submission and approval will be reported separately.
No client currently has a verified TrueFetch connection or installation guide. We will publish only steps supported by an operating integration, including authorization scopes, limits, revocation and known restrictions.
Billing and control
MCP follows the operation’s USD billing unit and spending ceiling; it does not introduce another public credit currency. Before execution, the service reserves the authorized upper bound. It settles eligible delivery and releases the unused amount. See the billing design.
Read the MCP technical plan and integration verification requirements, or tell us which client and task you need.