Premium Test MCP

net.digitalpipe.verify-testPublished by verify-test.digitalpipe.netv1.0.0Updated Oct 24, 2026

Premium test server verified via DNS-TXT.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A remote, bearer-authenticated MCP endpoint from DigitalPipe, described only as a premium test server verified via DNS-TXT.

What you can do
The manifest lists no tools, so the concrete capabilities are not documented here. It is a remote streamable HTTP endpoint that an assistant connects to at a fixed address. Access is gated by a bearer token issued by DigitalPipe for the connecting agent. The only stated purpose is that it is a premium test server verified via DNS-TXT.
When to use it
Only when you specifically need to connect to this DigitalPipe test endpoint, for example to check that bearer-token authentication and remote connectivity work. It is not a general-purpose server for real tasks, since no tools or capabilities are described.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A bearer token issued by DigitalPipe, supplied in the Authorization header, is required. Network access to the endpoint is needed.
Before you install
You must hand over a DigitalPipe-issued bearer token in the Authorization header; treat it as a secret and avoid sharing it. The server is labeled a test server, so do not rely on it for production data. No tools are listed, so what it does with your data cannot be checked in advance.

Installation

In SourceWeft

  1. Open Premium Test MCP in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.digitalpipe.verify-test%2Fdfuagp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "premium-test": {
      "type": "http",
      "url": "https://app.digitalpipe.net/p/dfuagp/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.