Toolaby

app.toolabyPublished by toolaby.appv1.15.1Updated Oct 24, 2026

Paid plans, licences, subscriptions and the paywall for Chrome extensions, on your own Stripe.

The publisher's own server: Toolaby docs

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Toolaby is a local MCP server for managing paid plans, licences, subscriptions and paywalls for Chrome extensions on your own Stripe account.

What you can do
The registry describes Toolaby as covering paid plans, licences, subscriptions and the paywall for Chrome extensions, running on your own Stripe. It is delivered as the npm package toolaby over stdio, so it starts as a local process on the user's machine. No individual tools are listed in the manifest, so the exact operations an assistant can call are not documented here.
When to use it
Consider it if you build Chrome extensions and want an assistant to help with the commercial side — plans, licences, subscriptions or paywall logic — while keeping billing on your own Stripe account. It is desktop-only, so it is not usable from a browser-based client.
Requirements
A local runtime able to run the npm package toolaby over stdio (typically Node.js), on a desktop machine. The manifest declares no authentication, environment variables or headers, but the description ties the server to your own Stripe account, so Stripe credentials are likely needed in practice.
Before you install
The server concerns billing and subscriptions on your own Stripe account, so treat any credentials it asks for as sensitive and check what it can change before granting access. No tools, permissions or credential names are documented in the supplied material, so verify the package and its behaviour yourself before installing.

Installation

In SourceWeft

  1. Open Toolaby in the dashboard and add it to a workspace.
  2. 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.

Tools

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

Version history

1
  1. v1.15.1LatestOct 14, 2026

Score

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

    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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Toolaby integrations

Toolaby docs

app.toolabyOfficial publisher

A remote MCP server that lets an assistant search and read Toolaby's documentation on payments, licences and paywalls for Chrome extensions.

Streamable HTTPWeb executable
Knowledge & Memory2 toolsOct 24, 2026