Hosted MCP server/Search Official

Official treg MCP server

Hosted at treg.to·Streamable HTTP

treg offers one MCP server and one key for more than 3,700 pay-per-call APIs. Coverage includes SEO and backlinks, people and company enrichment, social, ads, scraping, and image and video generation. The remote server at https://treg.to/mcp/v2/ uses OAuth, and a self-hosted option exists.

treg.to Streamable HTTP OAuth 2.1 (treg:catalog, treg:call, treg:read, treg:directory scopes) or per-org Bearer token Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-10-31
About

Where it fits

Developers and growth teams that need many paid data APIs behind a single key and one server.

  • Run a backlink check through a pay-per-call API
  • Enrich a company record from a single key
  • Generate an image through the same server

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Claude Code plugin install

The provider documents a Claude Code plugin install. The remote URL https://treg.to/mcp/v2/ remains available as an alternative and requires OAuth or a per-org bearer token.

  1. Add the plugin marketplace

    The provider documents a Claude Code plugin marketplace install.

    claude plugin marketplace add superdesigndev/treg
  2. Install the plugin

    Install the treg plugin from the marketplace, then authorize it.

  3. Alternative: use the remote URL

    Add https://treg.to/mcp/v2/ and authorize at treg.to/oauth/authorize or send a per-org bearer token.

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://treg.to/mcp/v2/
Host
treg.to · /mcp/v2/
Transport
Streamable HTTP
Authentication
OAuth 2.1 (treg:catalog, treg:call, treg:read, treg:directory scopes) or per-org Bearer token
Server name
treg
Listing type
Official provider listing

The installer uses the server name treg. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that treg appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Run a backlink check through a pay-per-call API. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.

Provider page available on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

treg documentationhttps://github.com/superdesigndev/treg/blob/HEAD/docs/CLAUDE-PLUGIN.mdGitHub repositoryhttps://github.com/superdesigndev/treg