LeapCal

io.github.pdelchevPublished by GitHub account pdelchevv0.1.0Updated Nov 5, 2026

Booking infrastructure for AI agents — distributed locking, trust scores, tamper-proof receipts.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

LeapCal is a remote booking service for AI agents, offering distributed locking, trust scores and tamper-proof receipts via OAuth.

What you can do
  • The listing gives no tool list, so capabilities are known only from its one-line description.
  • It presents itself as booking infrastructure that AI agents can use.
  • It advertises distributed locking, presumably to prevent double bookings.
  • It advertises trust scores and tamper-proof receipts for bookings.
When to use it
Consider it when an assistant needs to make or coordinate bookings and you want locking, trust scoring or verifiable receipts around those reservations. With no tool list or documentation available, evaluate it only after checking the provider's own details.
Requirements
A remote MCP endpoint at leapcal.com over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. No local package or runtime is needed.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested. Booking actions likely create or change reservations, and trust scores and receipts imply booking data is recorded by the provider. No tool list or README is available to confirm what it writes or shares.

Installation

In SourceWeft

  1. Open LeapCal 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.pdelchev%2Fleapcal/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": {
    "leapcal": {
      "type": "http",
      "url": "https://leapcal.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

1
  1. v0.1.0LatestNov 5, 2026

Score

75% 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
  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.