LateCheckOut

com.thelatecheckoutPublished by thelatecheckout.comOfficial publisherv1.0.0Updated Nov 7, 2026

Find great places from people you follow and people who recommend some of the same places as you.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

LateCheckOut is a remote MCP server that helps an assistant find recommended places based on people you follow and users with similar taste.

What you can do
  • The listing gives no tool list, instructions or README, so only the stated purpose is known.
  • Based on its description, it surfaces place recommendations drawn from accounts you follow.
  • It also draws on people who recommend some of the same places as you, suggesting taste-based discovery.
  • No further capabilities can be confirmed from the supplied material.
When to use it
Consider it when you want an assistant to suggest places to visit or eat based on your social circle and users with overlapping recommendations, rather than generic search results.
Requirements
A remote endpoint at api.thelatecheckout.com over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your account, and the service works from who you follow and what you recommend, so your social graph and place history are used. No tool list is published, so what it can read or change is unverified.

Installation

In SourceWeft

  1. Open LateCheckOut 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/com.thelatecheckout%2Flatecheckout/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": {
    "latecheckout": {
      "type": "http",
      "url": "https://api.thelatecheckout.com/mcp"
    }
  }
}

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. v1.0.0LatestNov 7, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.