Treg MCP Server: One Endpoint for Thousands of Paid APIs

• Finds API endpoints by the job you want done

  Searches the catalog by task words such as 'work email' or 'backlinks for a domain'. It returns each endpoint's ID, provider, price per call and whether Treg can serve it without a provider key. Its verdict says whether the catalog covers the task.

  Try: “Find an API that gives me the work email for someone at reddit.com.”

  Network · catalog_search

• Shows one endpoint's inputs, price and reliability

  Returns an endpoint's parameters, exact price, whether Treg serves it on its own key, and other providers for the same job with their measured success rate and speed. The server says to read it before calling.

  Try: “What would the backlinks endpoint cost, and what does it need?”

  Network · catalog_get

• Calls an API through Treg and bills your balance

  Calls a catalog endpoint, one of your team's own tools or a hub tool. Treg adds the credential on its server and returns the provider's answer unchanged. Catalog calls on Treg's key are charged to your team's prepaid balance, and it can send POST, PUT and DELETE requests as well as reads.

  Try: “Look up the email for Alexis Ohanian at reddit.com and tell me the price first.”

  Delete · call

• Calls an audio API and returns the sound

  Works like the main call tool but for endpoints that produce audio, such as Fish Audio speech, and returns the audio file.

  Try: “Read this paragraph aloud with an English voice.”

  Write · call_media

• Shows your prepaid balance

  Returns your team's balance in US dollars and any spend still in flight. The server suggests checking it when a call is refused for lack of funds.

  Try: “How much Treg credit do I have left?”

  Network · balance

• Lists the tools your team has registered

  Lists your team's own API keys, OAuth connections, vendor CLIs and skills that you can call without holding the credential. Your own tool wins over the catalog, and those calls are never charged.

  Try: “Which tools has my team shared on Treg?”

  Network · my_tools

• Lists voices and other resources made on Treg's accounts

  Lists durable resources created with Treg-provided provider credentials for your team. It can filter Fish voices.

  Try: “List the Fish Audio voices my team has made.”

  Network · resources_list

• Asks Treg to add a missing API

  Files a request for a provider or capability the catalog lacks. It is meant for when a search comes up empty.

  Try: “Ask Treg to add a TikTok comments API.”

  Write · catalog_request

• Sends feedback to Treg

  Submits feedback to Treg in one of four categories. It writes to Treg, not to an outside provider, and spends no balance. Some AI apps do not get this tool.

  Try: “Tell Treg the pagination example in the docs is unclear.”

  Write · feedback

• Rates how useful a call was

  Records whether the result of a catalog call was useful. Some AI apps do not get this tool.

  Try: “Mark that last call as useful.”

  Write · review

• Publishes a hub tool built from other tools

  Publishes a tool made of other tools under your team's name. Treg validates the files, runs the sample check once for real on your balance, and the version goes live if it passes. Some AI apps do not get this tool.

  Try: “Publish my lead-finder recipe as a hub tool.”

  Write · hub_create

• Publishes a new version of a hub tool

  Publishes a new version of a hub tool your team owns. The newest live version serves by default. Some AI apps do not get this tool.

  Try: “Publish version 2 of my lead-finder hub tool.”

  Write · hub_update

• Lists your team's hub tools

  Lists your team's hub tools with every version, its status, price, uses and check result. Some AI apps do not get this tool.

  Try: “Show the hub tools my team has published.”

  Network · hub_mine

Watch out for

• It can send writes and deletes to providers

  The call tool can use POST, PUT and DELETE, and the provider may create, change or delete data. Approve write calls one at a time. github.com

• It spends your team's prepaid balance, and the assistant decides when

  Catalog calls on Treg's key are billed per call to the team that authorised the connection, which can be shared with teammates. The tool text only tells the assistant to state the price before a call that costs more than a cent; it is an instruction to the assistant, so ask to see the price from catalog_get first and check the balance tool. The README says automatic top-ups can be set up, so turn them off if you want the loaded balance to be the limit. Calls that use your own registered key are not charged. github.com

• It can reach your team's own APIs

  Tools your team registered are called with the stored credential injected on the server. Share only the tools you want an assistant to use. github.com

• Public links and hub tools have side effects

  Publishing a hub tool runs its check once for real on your balance. Keep these tools for people who need them. github.com

• Check which team the connection spends from

  An OAuth grant is tied to one team. The server labels answers with the team and the signed-in email so a wrong team is visible; a person who authorised the connection can move it to another team from the CLI. github.com

• Spending limits exist on Treg's side

  The source says every call goes through checks for a per-user daily cap, a platform daily cap and a balance reserve, and an empty balance refuses the call with a 402 error. The caps' amounts are not in the README, so do not rely on a particular figure. github.com

Security advisories