{"servers":[{"server":{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"io.github.gregcastro23/alchm-kitchen","description":"Live transits, ESMS ingredients, cosmic recipes, synastry \u0026 transit×natal overlays by alchm.kitchen","repository":{"url":"https://github.com/gregcastro23/WhatToEatNext","source":"github","subfolder":"mcp-server"},"version":"1.1.1","packages":[{"registryType":"npm","identifier":"@alchm/mcp-server","version":"1.1.1","transport":{"type":"stdio"},"environmentVariables":[{"description":"Your alchm.kitchen API key — mint one at https://alchm.kitchen/profile/api-keys. Optional; unlocks per-user quotas and invocation telemetry. The server runs anonymously without it.","isSecret":true,"name":"MCP_USER_API_KEY"},{"description":"PostgreSQL connection string. Optional; enables the token gate and invocation logging. Omit for anonymous mode (all tools still function).","isSecret":true,"name":"DATABASE_URL"}]}]},"_meta":{"io.modelcontextprotocol.registry/official":{"status":"active","statusChangedAt":"2026-05-29T21:41:50.720399Z","publishedAt":"2026-05-29T21:41:50.720399Z","updatedAt":"2026-05-29T21:41:50.720399Z","isLatest":false}}},{"server":{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"io.github.gregcastro23/alchm-kitchen","description":"Thirteen culinary \u0026 astrological tools: transits, ingredients, recipes, synastry, pantry \u0026 swaps.","repository":{"url":"https://github.com/gregcastro23/WhatToEatNext","source":"github","subfolder":"mcp-server"},"version":"1.5.2","packages":[{"registryType":"npm","identifier":"@alchm/mcp-server","version":"1.5.2","transport":{"type":"stdio"},"environmentVariables":[{"description":"Optional alchm.kitchen API key (mint at https://alchm.kitchen/profile/api-keys). Without DATABASE_URL the server forwards each call to the hosted endpoint, which validates the key and applies billing. Without a key, read tools run locally in demo mode; reflection publication requires a key.","isSecret":true,"name":"MCP_USER_API_KEY"},{"description":"Alias for MCP_USER_API_KEY, supported in sanitized Planetary Agents client environments.","isSecret":true,"name":"ALCHM_MCP_USER_API_KEY"},{"description":"Operator-only PostgreSQL connection string. Setting it runs the tools in-process and validates keys and ESMS billing locally; leave it unset to use the hosted service (with a key) or demo mode (without).","isSecret":true,"name":"DATABASE_URL"},{"description":"Optional. auto (the default): with an API key and no DATABASE_URL the server forwards to the hosted endpoint, otherwise it runs in-process. remote: always forward to the hosted endpoint, even if an unrelated DATABASE_URL is set in the environment (needs MCP_USER_API_KEY). local: always run in-process (with a key and no DATABASE_URL, tool calls still go to the hosted REST endpoint under ALCHM_MCP_BACKEND_URL).","name":"ALCHM_MCP_MODE"},{"description":"Optional. The hosted MCP endpoint a key-only install forwards to, and the place your API key is sent: set it only to a host you trust. Defaults to https://alchm.kitchen/api/mcp; must be https (http is accepted only for localhost).","name":"ALCHM_MCP_REMOTE_URL"},{"description":"Backend origin serving /api/astrologize. Bundled artifacts default to https://alchm.kitchen; source runs default to http://localhost:3000. It is also where the in-process server sends a keyed tool call when it has no database (ALCHM_MCP_MODE=local), so it is where your API key goes then: https, or http only for localhost, 127.0.0.1 and [::1], without credentials, a query string or a fragment.","name":"ALCHM_MCP_BACKEND_URL"}]}]},"_meta":{"io.modelcontextprotocol.registry/official":{"status":"active","statusChangedAt":"2026-11-10T21:50:23.50078Z","publishedAt":"2026-11-10T21:50:23.50078Z","updatedAt":"2026-11-10T21:50:23.50078Z","isLatest":false}}},{"server":{"$schema":"https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name":"io.github.gregcastro23/alchm-kitchen","description":"14 culinary, thermodynamic \u0026 astrological tools: cauldron, transits, recipes, synastry \u0026 swaps.","repository":{"url":"https://github.com/gregcastro23/WhatToEatNext","source":"github","subfolder":"mcp-server"},"version":"1.6.0","packages":[{"registryType":"npm","identifier":"@alchm/mcp-server","version":"1.6.0","transport":{"type":"stdio"},"environmentVariables":[{"description":"Optional alchm.kitchen API key (mint at https://alchm.kitchen/profile/api-keys). Without DATABASE_URL the server forwards each call to the hosted endpoint, which validates the key and applies billing. Without a key, read tools run locally in demo mode; reflection publication requires a key.","isSecret":true,"name":"MCP_USER_API_KEY"},{"description":"Alias for MCP_USER_API_KEY, supported in sanitized Planetary Agents client environments.","isSecret":true,"name":"ALCHM_MCP_USER_API_KEY"},{"description":"Operator-only PostgreSQL connection string. Setting it runs the tools in-process and validates keys and ESMS billing locally; leave it unset to use the hosted service (with a key) or demo mode (without).","isSecret":true,"name":"DATABASE_URL"},{"description":"Optional. auto (the default): with an API key and no DATABASE_URL the server forwards to the hosted endpoint, otherwise it runs in-process. remote: always forward to the hosted endpoint, even if an unrelated DATABASE_URL is set in the environment (needs MCP_USER_API_KEY). local: always run in-process (with a key and no DATABASE_URL, tool calls still go to the hosted REST endpoint under ALCHM_MCP_BACKEND_URL).","name":"ALCHM_MCP_MODE"},{"description":"Optional. The hosted MCP endpoint a key-only install forwards to, and the place your API key is sent: set it only to a host you trust. Defaults to https://alchm.kitchen/api/mcp; must be https (http is accepted only for localhost).","name":"ALCHM_MCP_REMOTE_URL"},{"description":"Backend origin serving /api/astrologize. Bundled artifacts default to https://alchm.kitchen; source runs default to http://localhost:3000. It is also where the in-process server sends a keyed tool call when it has no database (ALCHM_MCP_MODE=local), so it is where your API key goes then: https, or http only for localhost, 127.0.0.1 and [::1], without credentials, a query string or a fragment.","name":"ALCHM_MCP_BACKEND_URL"}]}]},"_meta":{"io.modelcontextprotocol.registry/official":{"status":"active","statusChangedAt":"2026-11-12T06:10:34.145407Z","publishedAt":"2026-11-12T06:10:34.145407Z","updatedAt":"2026-11-12T06:10:34.145407Z","isLatest":true}}}],"metadata":{"count":3}}
