SpriteCook: MCP server, CLI and agent surfaces

Sign-in required, tools not seen, not counted. The MCP endpoint listed for SpriteCook at api.spritecook.ai 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

Company	SpriteCook
Domain	spritecook.ai
Category	Gaming & Media (assigned by this directory from the registry description)
MCP server	Sign-in required (OAuth with client registration)
Ora score	69, grade C; Ora scanned the domain on 8 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for spritecook.ai, a vendor-published score)
Company found through	the GitHub MCP Registry; the official MCP Registry
Last verified	4 November 2026

MCP server

Endpoint	`https://api.spritecook.ai/mcp`
How it was found	listed in the GitHub MCP Registry; the official MCP Registry
Transport	streamable-http
HTTP status	401
Connected	4 November 2026, 20:04 UTC
Handshake time	972 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:39Z https://api.spritecook.ai/mcp sent initialize result auth-required (HTTP 401) 1048 ms
20:04:39Z https://api.spritecook.ai/mcp sent initialize result auth-required (HTTP 401) 972 ms

Authentication

Auth type	OAuth with client registration
What the challenge said	`Bearer error="invalid_token", error_description="Authentication failed. The provided bearer token is invalid, expired, or no longer recognized by the server. To resolve: clear authentication tokens in your MCP client and reconnect. Your client should automatically re-register and obtain new tokens."`
Protected resource metadata	api.spritecook.ai
Authorization server metadata	api.spritecook.ai
Registration endpoint	`https://api.spritecook.ai/oauth/register`

The sign-in route, step by step

Request https://api.spritecook.ai/mcp without a token. It answers 401 and a WWW-Authenticate header.
Read the protected resource metadata at https://api.spritecook.ai/.well-known/oauth-protected-resource to find the authorization server.
Register a client at the registration endpoint https://api.spritecook.ai/oauth/register (dynamic client registration), so no human has to create an app first.
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 SpriteCook. 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
Surface	Result
OpenAPI file	Found: www.spritecook.ai (JSON, via a direct request).
WebMCP in the initial HTML	Not checked: the home page was not read by the shared crawl.
MCP discovery file	Not checked: the domain is not in the shared crawl for this edition.
A2A agent card	Not 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.json	Not checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadata	Not checked: the domain is not in the shared crawl for this edition.
NLWeb endpoint	Not checked in this edition.

Registry listings

Registry listings
Registry	Listed
Official MCP Registry	Yes: ai.spritecook/generate
GitHub MCP Registry	Yes
awesome-remote-mcp-servers	No
Smithery	Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
Glama	Not checked: Glama's API needs a key and attribution terms.