app.korima/pos
Korima POS
Is the Korima POS MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Configura tu punto de venta Korima: productos con variantes, precios, existencias, clientes.
needs auth probed 2026-11-14 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Conecta tu cuenta de Korima para usar este servid- Endpoint
- https://korima.app/mcp (streamable-http)
- Host
- korima.app
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://korima.app/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 oaeyaaiirayhswvfadiw.supabase.co, PKCE S256, grants authorization_code, refresh_token.
Scopes openid email profile.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://korima.app/mcp-info
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention existencias or configura.
- Simplio3D - 3D CPQ and Product Configuration ai.simplio3d/platform · needs auth
- ai.smithery/PabloLec-keyprobe-mcp · not found
- TBit app.tbit/tbit · needs auth
- ClearPost: WordPress SEO Agent com.clearpostplugin/wordpress-seo · needs your URL
- com.cve-security/cve-intelligence · alive
- HALO Homebridge AI Surfaces com.homebridgepc.agent-commerce/halo-ai-surfaces · server error
- Loppix catalog and configuration com.loppix/catalog-configuration · alive
- roamflat Flat configurator com.roamflat/esim-catalog · 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.