Agent MCP Directory

Pipeboard: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Pipeboard at snap-ads.mcp.pipeboard.co answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.

Fact sheet

CompanyPipeboard
Domainpipeboard.co
CategoryMarketing (assigned by this directory from the registry description)
MCP serverSign-in required (OAuth with client registration)
Ora score70, grade B; Ora scanned the domain on 21 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for pipeboard.co, a vendor-published score)
Company found throughthe awesome-remote-mcp-servers list; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://snap-ads.mcp.pipeboard.co/
How it was foundlisted in the awesome-remote-mcp-servers list; the official MCP Registry
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:04 UTC
Handshake time973 ms over 1 attempt

The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:58:52Z https://snap-ads.mcp.pipeboard.co/ sent initialize result auth-required (HTTP 401) 1033 ms
  • 20:04:01Z https://snap-ads.mcp.pipeboard.co/ sent initialize result auth-required (HTTP 401) 973 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer realm="MCP", resource_metadata="https://snap-ads.mcp.pipeboard.co/.well-known/oauth-protected-resource?platform=snap-ads"
Protected resource metadatasnap-ads.mcp.pipeboard.co
Authorization server metadatasnap-ads.mcp.pipeboard.co
Registration endpointhttps://pipeboard.co/oauth/register?platform=snap-ads
Auth as listed by a registryOAuth2.1 (a claim, not checked by connecting)

The sign-in route, step by step

  1. Request https://snap-ads.mcp.pipeboard.co/ without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://snap-ads.mcp.pipeboard.co/.well-known/oauth-protected-resource?platform=snap-ads to find the authorization server.
  3. Register a client at the registration endpoint https://pipeboard.co/oauth/register?platform=snap-ads (dynamic client registration), so no human has to create an app first.
  4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Pipeboard. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)Not checked: the domain is not in the shared crawl for this edition.
agents.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: co.pipeboard/google-ads-mcp, co.pipeboard/meta-ads-mcp, co.pipeboard/snap-ads-mcp and 1 more
GitHub MCP RegistryNo
awesome-remote-mcp-serversYes
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.