MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

app.toolaby/toolaby

Paid plans, licences, subscriptions and the paywall for Chrome extensions, on your own Stripe. — the publisher's description

4 of 6 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedversion 1.15.1MITstandard input/output30 tools

Summary

app.toolaby/toolaby is a local MCP server listed in the official MCP registry at version 1.15.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 30 tools, 2 resources and 4 prompts.

Record checks

4 of 6 record checks met · 3 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#314 of 15,112 packages by monthly downloads
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version behind the latest release
License: MIT
Dependencies: no known high or critical advisories
Tools: 30
Described as changing data: 19 of 30 toolsAI-classified
Mainly works on: money, payments or tradingAI-classified
Topic: finance-and-paymentsAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

19 tools are described as changing something (toolaby_sign_in, toolaby_create_tool, toolaby_update_tool, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
The registry lists 1.15.1; 1.16.1 is newer (2 releases).

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 1.15.1, published 2026-10-14 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-14 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-22
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.15.1 (published 2026-10-14).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

30tools

2resources

4prompts

What it mainly works on, as our AI model read its tool descriptions: money, payments or trading.

19 of 30 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

toolaby_whoamireads or searches
“The developer signed in to Toolaby (Test) and their workspaces, each with its role and the address its buyers use.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
toolaby_list_toolsreads or searches
“Every tool in the developer's workspaces on Toolaby (Test), with the id the other tools take.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
toolaby_get_toolreads or searches
“One tool on Toolaby (Test).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
toolaby_list_customersreads or searches
“The tool's customers on Toolaby (Test): everyone who holds or held it, with how (licence, subscription, trial, grant) and whether they are entitled now.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- querystring“Optional: part of an address or a name.”
- limitinteger“Optional: how many, 50 by default.”
toolaby_get_customerreads or searches
“One buyer of the tool on Toolaby (Test): whether they hold it now and how (entitledVia, plan, features), their licences, subscriptions (status, renews, endsAt, trialEnd) and grants, each with the id …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- emailstringrequired“The buyer's email address.”
toolaby_search_docson 1 other serverreads or searches
“Searches Toolaby's docs.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- querystringrequired
toolaby_docson 1 other serverreads or searches
“Toolaby's docs as Markdown.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- pagestring
toolaby_check
“Checks an extension folder's Toolaby wiring and answers findings with stable codes ({ code, level, message, file, line, fix, docs }); ok is false when any is an error.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- folderstring“The extension's folder, absolute or relative to where the server started.”
- builtstring“Optional: a build folder to check as the build.”
- browserboolean
- asstring“A plan id, as toolaby_get_tool lists them (the first plan is "default").”
toolaby_stripe_statusreads or searches
“Whether a workspace sells through Stripe yet on Test, and where a person connects it.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- workspacestring“The workspace slug, when you have more than one (toolaby_whoami lists them).”
toolaby_sign_indoes something elsedescribed as changing data
“Signs the command line and this server in to Toolaby (Test).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
Takes no inputs.
toolaby_create_toolcreates or changes datadescribed as changing data
“A new tool on Toolaby (Test): one more thing the workspace sells.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 1 required
- namestringrequired“What buyers see, like "Word Counter".”
- idstring“Optional: the id within the workspace.”
- taglinestring“Optional: one line under the name on the checkout page.”
- workspacestring“The workspace slug, when you have more than one (toolaby_whoami lists them).”
toolaby_update_toolcreates or changes datadescribed as changing data
“The tool's name, its line, its description, or its Chrome Web Store listing (the store link or the 32-letter id), on Test.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
5 inputs, 1 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- namestring
- taglinestring
- descriptionstring
- storeUrlstring

Show 18 more tools

toolaby_set_accesscreates or changes datadescribed as changing data
“What a buyer gets before paying, on Test: "open" (the tool's use, unlimited), "free_uses" (a number of uses per device, or per account with signInRequired, counted by gate() without a feature: for go…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
5 inputs, 2 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- accessstringrequired
- freeUsesinteger“With "free_uses": how many per device, or per account with signInRequired (at most 200 a day).”
- freeUsesPerstring“With "free_uses": how often they start again — "ever" (never, the default), or each UTC day, week (from Monday) or month.”
- signInRequiredboolean
toolaby_set_featurescreates or changes datadescribed as changing data
“The tool's whole feature list — send the features it keeps too: one left out is archived, never deleted (off the checkout, still held by the plans that held it, still answered for code that asks; sen…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
3 inputs, 2 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- featuresarrayrequired
- plansarray“For each plan id, the feature keys it unlocks.”
toolaby_add_plancreates or changes datadescribed as changing data
“A plan buyers can buy: a Price on the workspace's Stripe account (on Test, its test account).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
9 inputs, 4 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- billingstringrequired
- intervalstring“Subscriptions only.”
- amountnumberrequired“In the currency's main unit, like 9.99.”
- currencystringrequired“Three letters, like "usd" or "eur".”
- namestring“Optional: the plan's name, its tier, like "Pro".”
- trialDaysinteger“Subscriptions only: a free trial.”
- devicesinteger“Optional: devices one buyer may use at once.”
- perSeatboolean“Optional: sold per seat, to teams.”
toolaby_update_plancreates or changes datadescribed as changing data
“A plan's name (its tier), free trial, devices or per seat.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
6 inputs, 2 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- planstringrequired“A plan id, as toolaby_get_tool lists them (the first plan is "default").”
- namestring
- trialDaysinteger
- devicesinteger
- perSeatboolean
toolaby_retire_plandeletesdescribed as changing data
“Takes a plan off sale: its Stripe price is archived and nobody can buy it any more.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- planstringrequired“A plan id, as toolaby_get_tool lists them (the first plan is "default").”
toolaby_grantcreates or changes datadescribed as changing data
“Access to the tool's paid features without paying, for an address: a friend, a beta tester, a refund made good.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- emailstringrequired“The buyer's email address.”
- daysinteger“Optional: how long.”
toolaby_revoke_grantdeletesdescribed as changing data
“Takes back access given without paying: the person loses it at their next check.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- idstringrequired
toolaby_create_couponcreates or changes datadescribed as changing data
“A coupon code buyers type on the checkout page, on the workspace's Stripe account (Test).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
10 inputs, 1 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- codestring“Optional: the code.”
- percentOffnumber
- amountOffnumber
- currencystring
- durationstring
- monthsinteger
- maxRedemptionsinteger
- expiresDaysinteger
- firstTimeOnlyboolean
toolaby_refundmoves moneydescribed as changing data
“Refunds a buyer's lifetime licence in full on their card and revokes it at once; Stripe keeps its fee and Toolaby keeps its own.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
4 inputs, 1 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- emailstring“The buyer's email address.”
- licencestring“Optional: the licence id, when they have several.”
- reasonstring
toolaby_cancel_subscriptiondescribed as changing data
“Ends a buyer's subscription: at the end of the period they paid for (they keep access until then), or now.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
4 inputs, 1 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- emailstring“The buyer's email address.”
- subscriptionstring
- nowboolean“End it now, not at the period's end.”
toolaby_test_unlockcreates or changes datadescribed as changing data
“Test only.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
- planstring“A plan id, as toolaby_get_tool lists them (the first plan is "default").”
toolaby_copy_to_livedescribed as changing data
“Copies a tool from Test to Live — its Free plan, features, plans (as prices on the Live Stripe account), extension identity and versions — and answers the Live tool key.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
- toolstringrequired“The tool id, as toolaby_list_tools gives it (like "acme--word-counter"); the short one ("word-counter") works when it names one tool.”
toolaby_create_api_keycreates or changes datadescribed as changing data
“A secret API key for the developer's own server (Toolaby's REST API, Test), written into an env file as TOOLABY_API_KEY, with the API's base for this side as TOOLABY_API_URL, and never shown: the ans…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 1 required
- envFilestringrequired“The env file, like ".env" (relative to where the server started) or an absolute path.”
- namestring“Optional: what the key is for, like "Server".”
- workspacestring“The workspace slug, when you have more than one (toolaby_whoami lists them).”
toolaby_list_webhook_eventsreads or searches
“The events Toolaby sends a registered endpoint — purchases, subscriptions started and cancelled, refunds, disputes — each with a description and an example of what it carries, for the handler that re…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
toolaby_list_webhooksreads or searches
“The endpoints registered on Test: id, address, the events each listens for, and whether it is paused.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- workspacestring“The workspace slug, when you have more than one (toolaby_whoami lists them).”
toolaby_add_webhookcreates or changes datadescribed as changing data
“Registers the developer's server to receive Toolaby's events on Test, and writes its signing secret into an env file as TOOLABY_WEBHOOK_SECRET, never shown.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 2 required
- urlstringrequired“The public https address of the handler.”
- envFilestringrequired“The env file the server reads, like ".env", for TOOLABY_WEBHOOK_SECRET.”
- eventsarray“Optional: only these events (toolaby_list_webhook_events); all of them when left out.”
- descriptionstring
- workspacestring“The workspace slug, when you have more than one (toolaby_whoami lists them).”
toolaby_send_test_eventsends messagesdescribed as changing data
“Sends an event's example to every endpoint registered on Test that listens for it, as a real, signed delivery: the way to see a handler answer 2xx.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- typestringrequired“An event, like "purchase.completed" (toolaby_list_webhook_events).”
- workspacestring“The workspace slug, when you have more than one (toolaby_whoami lists them).”
toolaby_remove_webhookdeletesdescribed as changing data
“Removes an endpoint: deliveries to it stop at once.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 1 required
- idstringrequired“The endpoint id, as toolaby_list_webhooks gives it.”
- workspacestring“The workspace slug, when you have more than one (toolaby_whoami lists them).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 30 tools
Says what it returns: 59% of 29 tools
States limits, defaults or errors: 14% of 29 tools
Says when to use it: 100% of 5 tools
Items covered per tool: 2.5 of 4 on average

Counted from the listing

Parameters with a description: 69% of 86
Tools with a description: 100% of 30
Typical description length: 321 characters

The tool set

Counted from the listing

Tools: 30
Size of the list: about 8,952 tokens for an agent to load (characters ÷ 4)
Naming: 30 of 30 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 30 of 30 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package toolaby

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "toolaby": {
      "command": "npx",
      "args": [
        "-y",
        "toolaby@1.15.1",
        "mcp"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "toolaby": {
      "command": "npx",
      "args": [
        "-y",
        "toolaby@1.15.1",
        "mcp"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "toolaby": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "toolaby@1.15.1",
        "mcp"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"toolaby","type":"stdio","command":"npx","args":["-y","toolaby@1.15.1","mcp"]}'

Claude Code

claude mcp add --transport stdio toolaby -- npx -y toolaby@1.15.1 mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y toolaby@1.15.1 mcp

Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 1.15.1
Latest stable: 1.16.1
Status: behind the latest release (2 releases, 5 days)
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-+pDgEekUgMxm7hd72…
Signature: signed
License: MIT

Source: the package registry · 2026-10-22.

Usage

Downloads: 6,720 in the last month

Source: api.npmjs.org · 2026-10-22.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 1.15.1 on npm	Exists and can be installed	matches	npm · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

4 of 6 record checks met · 3 do not apply

#314 of 15,112 packages by monthly downloads
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists; a newer one is out.
Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about app.toolaby/toolaby

Answered from the data above

Is app.toolaby/toolaby safe to install?

We do not rate servers as safe or unsafe. 4 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 19 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has app.toolaby/toolaby been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can app.toolaby/toolaby do?

It lists 30 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, send messages, move money and do something else. We did not call any tool, so this describes the text, not the behaviour.

Can app.toolaby/toolaby change or delete data?

19 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Is the listed version current?

No. The registry lists 1.15.1; the latest stable release on npm is 1.16.1.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.lightningfaucet/lightning-wallet-mcpLightning Walletalso has tools that creates or changes data, deletes, does something else, moves money, reads or searches, sends messagescompare with this one
io.github.lightningfaucet/mcp-serveralso has tools that creates or changes data, deletes, does something else, moves money, reads or searches, sends messagescompare with this one
io.github.cnghockey/sats4aiSats4AI - Bitcoin-Powered AI Toolsalso has tools that creates or changes data, deletes, does something else, moves money, reads or searches, sends messagescompare with this one
co.lovie/company-formationLovie Company Formationalso has tools that creates or changes data, deletes, does something else, moves money, reads or searches, sends messagescompare with this one
io.github.ivaavimusic/singularitySingularity Layer MCPalso has tools that creates or changes data, deletes, does something else, moves money, reads or searches, sends messagescompare with this one
io.github.mikemark78/agentmarkalso has tools that creates or changes data, deletes, does something else, moves money, reads or searches, sends messagescompare with this one

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against

Does not apply to this server · 5

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
1,539 msConnected after 0 redirects.
Read the inventory: 30 tools, 2 resources, 4 prompts.
6,170 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

finance-and-payments

AI-classified (Gemini + Claude agreed) · 2026-10-23

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it.

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-22

Integrity hash

declared (sri)

package registry · 2026-10-22

Signature / provenance

signed

package registry · 2026-10-22

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

6,720 downloads a month

package registry · 2026-10-22

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “app.toolaby/toolaby: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/app.toolaby/toolaby

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/app.toolaby/toolaby)](https://protocolprobe.com/mcp/servers/app.toolaby/toolaby)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology