# toolaby

The Toolaby command line: wire any Chrome extension to your Toolaby tool (sign-in, licences, subscriptions, the paywall), move one from ExtensionPay or start a new one; check it, pack it for the Chrome Web Store, and give coding agents Toolaby as an MCP s

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.15.1
- **Author:** Unknown
- **License:** MIT
- **npm:** toolaby
- **Source:** https://github.com/miltostave/Toolaby
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-16T11:16:02.974Z
- **Version scanned:** 1.15.1
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `sell-a-feature` — Make one feature of this extension paid: a plan, the feature, the gate in the code, and proof it unlocks.
- `feature` — What becomes paid, like "export to CSV".
- `price` — Like "$5 once" or "$4/month, 7-day trial".
- `move-from-extensionpay` — Switch an ExtensionPay extension to Toolaby, keep its paying users, and list what a person does in Stripe.
- `ship-to-store` — Copy the tool to Live, put the Live key in, build, pack, and list the person's steps.
- `version` — The version to ship, like "1.3.0".
- `fix-wiring` — Find and fix why the paywall does not show, or sign-in does not stick.
- `symptom` — What users see.
- `docs-page` — A page of the docs as Markdown, like toolaby://docs/gating or toolaby://docs/reference/client.
- `tool`
- `docs-index`
- `docs-agents`
- `toolaby`
- `toolaby_whoami`
- `toolaby_list_tools`
- `toolaby_get_tool`
- `toolaby_list_customers`
- `toolaby_get_customer`
- `toolaby_search_docs` — Searches Toolaby's docs. Call this before writing Toolaby code or answering how something works, even when you think you know: it gives the pages and sections t
- `toolaby_docs` — Toolaby's docs as Markdown. Without a page: the index, every page with what it covers. With a page (like "gating", "pricing", "agents", "reference/client"): tha
- `toolaby_check`
- `toolaby_stripe_status`
- `toolaby_sign_in`
- `toolaby_create_tool`
- `toolaby_update_tool`
- `toolaby_set_access`
- `toolaby_set_features`
- `toolaby_add_plan`
- `toolaby_update_plan` — A plan's name (its tier), free trial, devices or per seat. Only what is sent changes. The price never changes: a new price is a new plan (toolaby_add_plan), and
- `toolaby_retire_plan` — Takes a plan off sale: its Stripe price is archived and nobody can buy it any more. Everyone who bought it keeps what they bought.
- `toolaby_grant`
- `toolaby_revoke_grant` — Takes back access given without paying: the person loses it at their next check. The id comes from toolaby_grant's answer or toolaby_get_customer.
- `toolaby_create_coupon`
- `toolaby_refund` — 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. By the buyer's address (when th
- `toolaby_cancel_subscription` — Ends a buyer's subscription: at the end of the period they paid for (they keep access until then), or now. Nothing is refunded. By the buyer's address (when the
- `toolaby_test_unlock` — Test only. A licence for one of the tool's plans, for the developer's own +toolaby-test address, with no payment: then toolaby_check with browser and as: <plan>
- `toolaby_copy_to_live`
- `toolaby_create_api_key`
- `toolaby_list_webhook_events` — The events Toolaby sends a registered endpoint — purchases, subscriptions started and cancelled, refunds, disputes — each with a description and an example of w
- `toolaby_list_webhooks`

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"toolaby\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"toolaby\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on your machine.
- Floor 28, ceiling 52 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/toolaby
- Install plan: https://forgeregistry.com/api/v1/packages/toolaby/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/toolaby
- HTML page: https://forgeregistry.com/registry/toolaby
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.