com.striktly/living-shaders
Striktly Living Shaders
Is the Striktly Living Shaders MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Find, customize, preview and export interactive WebGL backgrounds for React and websites.
needs auth probed 2026-11-15 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Connect Striktly to continue."}- Endpoint
- https://striktly.com/mcp (streamable-http)
- Host
- striktly.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://striktly.com/mcp 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 striktly.com, PKCE S256, grants authorization_code, refresh_token.
Scopes shaders:read shaders:export.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://striktly.com/docs/mcp
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Servers that mention shaders.
- Enrichr Web Capture dev.enrichr/web-capture · needs auth
- HorizonX — Premium UI Library io.github.Mdx2025/horizonx · needs auth
- Three.js DevTools MCP io.github.DmitriyGolub/threejs-devtools · alive
- Unity MCP dev.shiranui-isuzu/unity-mcp · not probed
- io.github.n1m21n/infinite-engine · alive
- Subframe Motion com.subframe/motion · 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.