Checkslip Mcp

com.thaibankslipPublished by thaibankslip.comOfficial publisherv1.0.0Updated Oct 24, 2026

Verify Thai bank transfer slips: amount, receiver, date, and duplicate reuse via check_slip.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Lets an assistant verify Thai bank transfer slips, checking amount, receiver, date, and duplicate reuse.

What you can do
This remote server exposes a check_slip tool that verifies Thai bank transfer slips. It checks the amount, the receiver, the date, and whether the same slip has been reused as a duplicate. It is a single-purpose verification service rather than a general banking tool.
When to use it
Useful when an assistant needs to confirm that a Thai bank transfer slip is genuine and matches expected payment details, or to detect a slip that has already been submitted before.
Requirements
A remote MCP endpoint at thaibankslip.com over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
Slips and payment details are sent to a third-party service for verification. OAuth access is required, so review what account permissions you grant. Verification results should not be treated as a substitute for checking with the bank.

Installation

In SourceWeft

  1. Open Checkslip Mcp 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.thaibankslip%2Fcheckslip-mcp/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": {
    "checkslip": {
      "type": "http",
      "url": "https://thaibankslip.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.0LatestSep 16, 2026

Score

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

    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.