GOLDSHORE

Protected access

Log in to GoldShore

Choose the identity route that matches the service you need. Access permissions are still enforced after sign-in.

Continue with Cloudflare AccessContinue with GitHub

Stay in the loop

Receive GoldShore analysis, product updates, and practical notes. Confirm your address before anything is sent.

GoldShore MCP

Private tooling for approved humans and agents.

The public site can explain the offering, but https://mcp.goldshore.ai/mcp itself is reserved for identities that have already been approved. That keeps the surface useful for the team without turning it into an open prompt endpoint.

Open MCP adminRequest access

Actual connection

One endpoint. One server. Permission-gated tools.

The canonical public surface is the protected MCP Portal at https://mcp.goldshore.ai/mcp. It may aggregate approved internal GoldShore upstreams; the protected admin console documents and operates the same catalog without exposing those upstream URLs to clients.

Streamable HTTP client
[mcp_servers.goldshore-mcp-portal]
url = "https://mcp.goldshore.ai/mcp"
# sign in once: codex mcp login goldshore-mcp-portal

Interactive clients sign in through Cloudflare Access OAuth; no bearer token is issued. Headless service identities send CF-Access-Client-Id and CF-Access-Client-Secret headers from an encrypted secret store.

1

Request approval

Account and tool permissions are granted to a named human or service identity.

2

Authenticate at the edge

Cloudflare Access validates the identity before the request reaches gs-api.

3

Initialize the client

Connect with Streamable HTTP and negotiate the supported protocol version.

4

Review available tools

The live tools/list response and protected admin console share one canonical catalog.

Who can use it

Only you, approved operators, and a dedicated agent/service identity path.

How it is gated

Cloudflare Access sits in front of the host so the endpoint does not accept anonymous use.

What it is for

Controlled prompts, read/write actions, and internal tool calls that support the GoldShore stack.

What stays out

Public prompt boxes, open registrations, and broad anonymous tooling access.

Policy

Public explanation, private execution.

GoldShore can describe the MCP capability on the public site, but the live host stays behind Cloudflare Access and does not accept anonymous prompts or changes. That gives the product a front door without making the underlying tool surface public.