org.foodnotes/foodex2-encoder
FoodEx2 Encoder
Is the FoodEx2 Encoder MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-29.
Turn an English food description into an EFSA FoodEx2 code.
needs auth probed 2026-11-15 · unchanged since 2026-10-29 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: <!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title><meta http-equiv="Content-Type" content
- Endpoint
- https://foodex2-encoder.foodnotes.org/mcp (streamable-http)
- Host
- foodex2-encoder.foodnotes.org
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://foodex2-encoder.foodnotes.org/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server foodex2-encoder.foodnotes.org, PKCE S256, grants authorization_code, refresh_token.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/FoodNotes-org/foodex2-encoder
- Website
- https://foodex2-encoder.foodnotes.org/
- Registry
- active, updated 2026-10-16 · registry entry
Compare this server with others.
More servers
Servers that mention encoder.
- Execute ambisonics-b-format-encoder-mcp io.github.Evozim/ambisonics-b-format-encoder-mcp · paid (402)
- io.github.beeswaxpat/ffmpeg-render-pro · crashed on start
- Sunstone Weave: Local Semantic Code Search io.github.space-bacon/blackwindow-weave-mcp · needs env
- io.github.SebastianMaciel/jsx-notation · alive
- io.github.CSOAI-ORG/encoder-ai-mcp · needs mcp<2
- io.github.userFRM/rpg-encoder · crashed on start
- app.hyperwave.www/wavetable-tools · alive
- Neuroencoder EEG embeddings com.neuroencoder/eeg-embeddings · 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.