Agent MCP Directory

GlanceAI: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for GlanceAI at glance.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

CompanyGlanceAI (registry title: GlanceAI Fashion MCP)
Domainglance.com
CategoryDeveloper Tools (assigned by this directory from the registry description)
MCP serverSign-in required (OAuth with client registration)
Tranco rank5,803 on the list of 4 November 2026
Ora scorenone: Ora returned no cached score for glance.com when asked on 5 November 2026
Company found throughthe official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://glance.com/mcp
How it was foundlisted in the official MCP Registry
Transportstreamable-http
HTTP status401
Connected4 November 2026, 20:01 UTC
Handshake time1,744 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:56:10Z https://glance.com/mcp sent initialize result auth-required (HTTP 401) 1115 ms
  • 20:01:48Z https://glance.com/mcp sent initialize result auth-required (HTTP 401) 1744 ms

Authentication

Auth typeOAuth with client registration
What the challenge saidBearer resource_metadata="https://ember.ailooks.glance.com/.well-known/oauth-protected-resource"
Protected resource metadataember.ailooks.glance.com
Authorization server metadataember.ailooks.glance.com
Registration endpointhttps://ember.ailooks.glance.com/register

The sign-in route, step by step

  1. Request https://glance.com/mcp without a token. It answers 401 and a WWW-Authenticate header.
  2. Read the protected resource metadata at https://ember.ailooks.glance.com/.well-known/oauth-protected-resource to find the authorization server.
  3. Register a client at the registration endpoint https://ember.ailooks.glance.com/register (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 GlanceAI. 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 detected on the home page by the shared crawl.
MCP discovery fileFound: glance.com/.well-known/mcp.json answered with a valid document in the shared crawl.
A2A agent cardFound: glance.com/.well-known/agent-card.json answered with a valid document in the shared crawl.
A2A agent card (older path)Found: glance.com/.well-known/agent.json answered with a valid document in the shared crawl.
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataFound: glance.com/.well-known/oauth-authorization-server answered with a valid document in the shared crawl.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: com.glance/glanceai-fashion
GitHub MCP RegistryNo
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.