# treg.to [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/superdesigndev/treg  
**GitHub Stars:** 8716  
**Views:** 7  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/treg-to

## Description
OpenRouter for tools and data. Compare catalog providers and call them from one hosted MCP endpoint.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "treg-to": {
    "command": "uvx",
    "args": ["tools-registry"]
  }
}
```

## Documentation

## What treg.to MCP server does

treg.to provides an aggregation layer for agent tools and data. Its catalog groups external endpoints by the job they perform, including backlink research, SEO and rank tracking, social and trend analysis, people and company enrichment, advertising, scraping, and image, video, or audio generation. Agents can search by task instead of starting with a known vendor.

The same registry can expose tools belonging to a team. These may be paid APIs, OAuth connections, vendor command-line programs, or workflow skills defined with a `SKILL.md` file. A team can register these resources so teammates' agents can use them without receiving the underlying credentials.

## How it works

Requests use one treg token, sent in the `X-Treg-Token` header. The proxy forwards calls to upstream services and adds authentication on the server side; it does not create a separate model of each upstream API. When a team has registered its own provider tool or secret, that credential takes precedence over treg's catalog credential and calls are not metered through the catalog balance.

The command-line workflow illustrates the registry's main operations:

- `treg catalog search` finds tools by description of the desired task.
- `treg catalog get <id>` shows a tool's declared parameters, price, and example response.
- `treg call <id>` invokes a catalog or registered tool.
- `treg balance` reports call spending.
- `treg tool ls` lists tools shared with the team.
- `treg health` checks credential status.

Catalog tools can be called with query parameters, headers, and request bodies. Tools marked `strict_query` reject undeclared or repeated query parameters, unsupported values, and request bodies that do not meet their declared contract.

## Setup and configuration

Install the CLI and sign in through the hosted registry:

```bash
curl -fsSL https://treg.to/install.sh | sh
treg login
```

GitHub is the default sign-in method; email one-time codes and token-based login for agents or CI are also supported. After authentication, the same token is used across tools. The guided `treg onboard` command is available instead of following the individual quickstart steps.

Claude Code users can install the marketplace plugin with `/plugin marketplace add superdesigndev/treg` followed by `/plugin install treg@treg`. The plugin adds the skill and tools; sign-in is completed from the MCP interface. Other public workflow skills can be added with the `skills` CLI or the treg bootstrap command.

The hosted MCP surfaces are available at `https://treg.to/mcp/` and, for the Claude Connectors Directory, `https://treg.to/mcp/v2/`. The v2 connector exposes curated catalog endpoints and separates read and write calls. treg.to can also be self-hosted.

## Tools and capabilities

- Search a catalog of external tools by task or provider.
- Inspect declared parameters, pricing, and example responses before calling.
- Relay requests using catalog credentials or a team's own credentials.
- Register and share APIs, OAuth connections, vendor CLIs, and skills.
- Run workflow skills such as web access, lead-signal research, recruiting, and AI UGC creation.
- Call media and data services through the CLI, including binary responses redirected to files.

## Limitations and notes

The proxy relays upstream services rather than normalizing their interfaces, so callers work with each tool's declared request shape. Catalog coverage and behavior depend on the available endpoints and their provider routes. The Claude connector's v2 surface is limited to curated catalog endpoints and excludes image, video, and audio generation; the regular MCP surface also supports team-owned tools and imported skills.

_Full upstream README: https://allmcps.com/mcp/treg-to/readme_

