TrueCal

io.github.SuperboxAIPublished by GitHub account SuperboxAIv1.0.1Updated Oct 24, 2026

Use TrueCal from AI agents to review progress, meals, targets, trends, and supported updates.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

TrueCal is a remote MCP server that lets an AI assistant review your nutrition progress, meals, targets and trends, and make supported updates.

What you can do
  • Review progress and trends over time
  • Look up logged meals and nutrition targets
  • Apply supported updates to your TrueCal data
When to use it
Useful when you track food and nutrition in TrueCal and want an assistant to summarize progress, check meals against targets, or make supported changes without opening the app.
Requirements
A remote endpoint at app.truecal.com reached over streamable HTTP, plus a TrueCal account and OAuth sign-in. No environment variables or headers are declared.
Before you install
The server can make supported updates to your data, so changes may be written to your TrueCal account. Access is granted through OAuth to your account; review the permissions requested at sign-in. Your meal and progress data is handled by a third-party service.

Installation

In SourceWeft

  1. Open TrueCal in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.SuperboxAI%2Fgptbot-food-calendar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "truecal": {
      "type": "http",
      "url": "https://app.truecal.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 4, 2026
  2. v1.0.0Sep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.