MCP and AI clients
TrueFetch is designing REST and MCP around the same product inputs, billing rules and source outcomes.
Planned tools
Section titled “Planned tools”| Tool | Purpose |
|---|---|
truefetch_search_jobs |
Create a Job Search task. This can incur a charge once the service opens. |
truefetch_get_task |
Read an existing task and its result; not a new collection. |
A spending cap limits cost but does not guarantee that a client will skip its own permission prompts. Client authorization and user intent remain separate from the amount a request is allowed to cost.
Authentication paths
Section titled “Authentication paths”- API key: planned for compatible coding agents and clients.
- OAuth: planned for compatible hosted chat connectors. Availability will be confirmed independently of API-key support.
Directory acceptance and a client’s decision to choose a tool are not guaranteed by MCP support. We will publish tested connection steps for each supported path when it is available.
Untrusted source content
Section titled “Untrusted source content”Collected text is data, not instructions. A client must not follow embedded directions to reveal secrets, change budgets or call unrelated tools. Tool descriptions and output schemas help define the contract but do not eliminate this boundary.