Agent MCP Directory

Sherweb: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for Sherweb at mcp.sherweb.com 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

CompanySherweb (registry title: Sherweb Platform MCP Server)
Domainsherweb.com
CategoryInfrastructure (assigned by this directory from the registry description)
MCP serverSign-in required (OAuth without client registration)
Ora score53, grade C; Ora scanned the domain on 1 September 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for sherweb.com, a vendor-published score)
Company found throughthe GitHub MCP Registry; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://mcp.sherweb.com
How it was foundlisted in the GitHub MCP Registry; the official MCP Registry
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:04 UTC
Handshake time1,980 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:59:29Z https://mcp.sherweb.com sent initialize result auth-required (HTTP 401) 2421 ms
  • 20:04:30Z https://mcp.sherweb.com sent initialize result auth-required (HTTP 401) 1980 ms

Authentication

Auth typeOAuth without client registration
What the challenge saidBearer resource_metadata="http://mcp.sherweb.com/.well-known/oauth-protected-resource/"
Protected resource metadatamcp.sherweb.com
Authorization server metadatacumulus.sherweb.com

The sign-in route, step by step

  1. Request https://mcp.sherweb.com without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the OAuth metadata at https://cumulus.sherweb.com/oidc/.well-known/openid-configuration. It lists no registration endpoint.
  3. Register the client by hand in the company's developer settings, or present a client ID metadata document if the authorization server supports one.
  4. Authorize as a person, then retry the endpoint with the bearer token. The connector stops after step 2.

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

CLI

No CLI is on record for Sherweb. 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: com.sherweb/platform
GitHub MCP RegistryYes
awesome-remote-mcp-serversNo
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.