Skip to main content

Food Logger MCP

ai.sig.foodlog/food-loggerVersion 1.1.0

Food logging, nutrition summaries, and meal photo calorie and macro estimates.

Status

Sign-in required292 msReachable. It asks for authorization, so we did not look inside.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 13:33 UTC
Latency
292 ms
Remotes responding
1 of 1
Sign-in
API key
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://foodlog.sig.ai/api/mcpSign-in required292 ms
API key

Claude Code

This server asks for sign-in. Your client opens the sign-in when it connects.

claude mcp add --transport http food-logger https://foodlog.sig.ai/api/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'

Replace <YOUR_TOKEN> before running.

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: food-logger
Remote MCP server URL: https://foodlog.sig.ai/api/mcp
This server expects the header Authorization.

Cursor

{
  "mcpServers": {
    "food-logger": {
      "url": "https://foodlog.sig.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Replace <YOUR_TOKEN> before running.

VS Code

code --add-mcp '{"name":"food-logger","type":"http","url":"https://foodlog.sig.ai/api/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'

Replace <YOUR_TOKEN> before running.

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

Tools are visible after sign-in; we do not look inside protected servers.

Details

Registry status
Active
Published
Jun 12, 2026
Updated
Jun 12, 2026
Categories (suggested)
Design and mediaSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing