ShaBaasPay MCP Server

io.github.shabaaspayPublished by GitHub account shabaaspayv1.0.4Updated Oct 24, 2026

MCP server for PayTo agreements and payment initiation in Australia.

VerifiedSTDIODesktop onlyFinance

Server details

Identifier: io.github.shabaaspay/shabaaspay-mcp-server
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account shabaaspay for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.shabaaspay%2Fshabaaspay-mcp-server.svg)](https://sourceweft.com/mcp/io.github.shabaaspay%2Fshabaaspay-mcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server for Australian PayTo agreements and payment initiation, letting an assistant work with PayTo payment flows.

What you can do: Work with PayTo agreements and payment initiation in Australia.
The registry lists no individual tools, so the exact operations an assistant can call are not documented here.
No instructions or README are provided, so setup and usage details are unknown.
When to use it: Consider it if you need an assistant to help with Australian PayTo payment agreements or to initiate payments through this provider. Because the available tools are undocumented, confirm the exact capabilities before relying on it.
Requirements: Runs as a local process on the user's machine, distributed as the npm package shabaaspay-mcp-server (stdio transport; the package also lists streamable-http). Desktop only. No environment variables, headers or authentication are declared, so any account or credential needs are unstated.

Before you install

It concerns payment initiation and PayTo agreements, so actions may move money or create recurring payment authorisations; review each action before approving. No authentication, credentials or environment variables are declared, which makes it unclear how access to a payment account is secured. The tool list is undocumented, so verify what it can actually do first.

Installation

In SourceWeft

Open ShaBaasPay MCP Server in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.4LatestSep 16, 2026

Score

25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
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.