dev.cotlet/flickr
Flickr by Cotlet
Is the Flickr by Cotlet MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-09.
Photos, albums, tags and comments in your Flickr, worked by your agent.
needs auth probed 2026-11-14 · unchanged since 2026-11-09 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","message":"Sign in to Cotlet to use this MCP server."}- Endpoint
- https://cotlet.dev/mcp/v1/flickr/connect (streamable-http)
- Host
- cotlet.dev
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://cotlet.dev/mcp/v1/flickr/connect registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server cotlet.dev, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://cotlet.dev/integrations/flickr-api-mcp-server
- Registry
- active, updated 2026-11-09 · registry entry
Compare this server with others.
More servers
Other registry entries on cotlet.dev, the ones next to this name; all of them.
- Findymail MCP Server and API by Cotlet dev.cotlet/findymail · needs auth
- Fitatu MCP Server and API by Cotlet dev.cotlet/fitatu · not probed
- FitBudd MCP Server and API by Cotlet dev.cotlet/fitbudd · needs auth
- FitSW MCP Server and API by Cotlet dev.cotlet/fitsw · needs auth
- Formstack MCP Server and API by Cotlet dev.cotlet/formstack · needs auth
- Fortnox MCP Server and API by Cotlet dev.cotlet/fortnox · needs auth
- FreeScout MCP Server and API by Cotlet dev.cotlet/freescout · needs auth
- Fresha MCP Server and API by Cotlet dev.cotlet/fresha · needs auth
Servers that mention flickr.
- Flickr Public io.github.pipeworx-io/flickr-public · alive
- io.github.MK3Core/flickr-mcp · needs env
- io.github.mrfentmen/flickr-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.