Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
OneLessTool is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Find software subscriptions you can drop using tools you already own, with vendor-verified prices.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http onelesstool-mcp https://onelesstool.com/api/mcp
# 2 — ask your agent for something these tools do
# search_catalog, get_tool, find_alternatives and 6 more
OneLessTool costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ONAll 1 server
onelesstool1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http onelesstool-mcp https://onelesstool.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Natural-language search across software products, capabilities (what software does) and replacement workflows. Understands synonyms, e.g. 'make thumbnails' finds YouTube thumbnail workflows. Returns ranked hits with URLs, plus the tool and capabilities the query most likely refers to.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What the user is looking for: a product name, a task, or an outcome |
| kinds | array | no | Restrict result types |
| limit | integer | no | Max results (default 10) |
Full structured profile of a software product: plans and prices (with evidence status and verification date), capabilities with fit and limitations, honest reasons it's hard to replace, risks, related replacement workflows and sources.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | Tool name or slug, e.g. 'Canva' or 'canva' |
For a specific product (e.g. Canva), list each capability it provides and the best alternatives — ranking tools the user ALREADY owns first at $0 extra. Pass the capabilities the user actually uses (from get_tool) for a precise answer. Includes the honest case for keeping the tool.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | The tool the user is considering dropping |
| capabilities | array | no | Capability slugs the user actually uses this tool for (default: its core capabilities) |
| owned_tools | array | no | Tools the user already pays for, by name or slug, e.g. ["ChatGPT Plus", "google-workspace"] |
| team_size | integer | no | People who need access (affects per-seat costs) |
For one capability (e.g. 'youtube-thumbnails', 'crm-contacts', 'workflow-automation'), compare all known tools: fit, quality scores on the dimensions that matter, required skill, cheapest qualifying plan and limitations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| capability | string | yes | Capability slug, or a phrase like 'make thumbnails' (resolved via search) |
Find practical, step-by-step workflows that replace a paid tool or accomplish an outcome with tools the user already owns. Filter by tool being replaced, capability, or free-text query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| replaces_tool | string | no | Only workflows that replace this tool |
| capability | string | no | — |
| limit | integer | no | — |
Full replacement guide: before/after, required tools and extra cost, setup steps, copyable prompts, templates/scripts, limitations, risks, a verification checklist to run BEFORE cancelling, and the savings methodology.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| sections | array | no | Return only these sections to save context (default: all) |
Given the outcomes the user needs (free text or capability slugs) and what they already own, recommend per-capability options (owned tools at $0 first) and a minimal stack covering everything, with incremental monthly cost and warnings about skill, collaboration and data sensitivity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Outcome in plain English, e.g. 'I need 15 YouTube thumbnails a month and a simple CRM' |
| capabilities | array | no | — |
| owned_tools | array | no | Tools the user already pays for, by name or slug, e.g. ["ChatGPT Plus", "google-workspace"] |
| team_size | integer | no | — |
| skill | string | no | User's technical skill |
| needs_collaboration | boolean | no | — |
| sensitive_data | boolean | no | — |
Audit the user's subscriptions. For each: keep, downgrade, redundant, test_replacement, review_unused or keep_critical — with the arithmetic. Savings are split into 'likely' and 'possible' and never double-counted. Costs are what the user actually pays (monthly, all seats).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subscriptions | array | yes | — |
| skill | string | no | — |
List plan prices for one tool or all tools, each with evidence status, verification date and source URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OneLessTool or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish OneLessTool can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.