# OneLessTool (remote · onelesstool.com)

Find software subscriptions you can drop using tools you already own, with vendor-verified prices.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `onelesstool.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-onelesstool-onelesstool/api-mcp.md), [page](https://verifymcp.io/servers/com-onelesstool-onelesstool/api-mcp)

## Channel facts

- Endpoint: `https://onelesstool.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1138 tokens (~126/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 56% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the OneLessTool MCP server?

OneLessTool is a hosted endpoint at https://onelesstool.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-onelesstool-onelesstool 'https://onelesstool.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-onelesstool-onelesstool": {
      "url": "https://onelesstool.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-onelesstool-onelesstool": {
      "type": "http",
      "url": "https://onelesstool.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-onelesstool-onelesstool]
url = "https://onelesstool.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-onelesstool-onelesstool": {
      "type": "remote",
      "url": "https://onelesstool.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-onelesstool-onelesstool --url 'https://onelesstool.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-onelesstool-onelesstool:
    url: "https://onelesstool.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-onelesstool-onelesstool": {
      "Transport": "http",
      "Url": "https://onelesstool.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-onelesstool-onelesstool -t streamable-http -u 'https://onelesstool.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-onelesstool-onelesstool": {
      "type": "http",
      "url": "https://onelesstool.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (9)

### `search_catalog` (~108 tokens)

Search software, capabilities and workflows

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.

Input parameters:

- `kinds` (array): Restrict result types
- `limit` (integer): Max results (default 10)
- `query` (string, required): What the user is looking for: a product name, a task, or an outcome

### `get_tool` (~71 tokens)

Get a software product's profile

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.

Input parameters:

- `tool` (string, required): Tool name or slug, e.g. 'Canva' or 'canva'

### `find_alternatives` (~156 tokens)

Find cheaper ways to do what a tool does

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.

Input parameters:

- `capabilities` (array): Capability slugs the user actually uses this tool for (default: its core capabilities)
- `owned_tools` (array): Tools the user already pays for, by name or slug, e.g. ["ChatGPT Plus", "google-workspace"]
- `team_size` (integer): People who need access (affects per-seat costs)
- `tool` (string, required): The tool the user is considering dropping

### `compare_solutions` (~77 tokens)

Compare every way to accomplish a capability

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.

Input parameters:

- `capability` (string, required): Capability slug, or a phrase like 'make thumbnails' (resolved via search)

### `find_workflows` (~80 tokens)

Find replacement workflows

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.

Input parameters:

- `capability` (string)
- `limit` (integer)
- `query` (string)
- `replaces_tool` (string): Only workflows that replace this tool

### `get_workflow` (~75 tokens)

Get replacement instructions

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.

Input parameters:

- `sections` (array): Return only these sections to save context (default: all)
- `slug` (string, required)

### `recommend_stack` (~166 tokens)

Recommend the cheapest practical stack

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.

Input parameters:

- `capabilities` (array)
- `needs_collaboration` (boolean)
- `owned_tools` (array): Tools the user already pays for, by name or slug, e.g. ["ChatGPT Plus", "google-workspace"]
- `query` (string): Outcome in plain English, e.g. 'I need 15 YouTube thumbnails a month and a simple CRM'
- `sensitive_data` (boolean)
- `skill` (string): User's technical skill
- `team_size` (integer)

### `estimate_savings` (~82 tokens)

Audit a software stack and estimate savings

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).

Input parameters:

- `skill` (string)
- `subscriptions` (array, required)

### `get_pricing` (~37 tokens)

Get pricing metadata with verification status

List plan prices for one tool or all tools, each with evidence status, verification date and source URL.

Input parameters:

- `tool` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-onelesstool-onelesstool/api-mcp#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 76
- 2026-11-02: 76
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 73
- 2026-10-27: 73
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 71
- 2026-10-22: 71
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 69
- 2026-10-18: 69
- 2026-10-17: 68
- 2026-10-16: 68
- 2026-10-15: 67
- 2026-10-14: 64
- 2026-10-13: 64

## Common questions

### What is the OneLessTool MCP server?

OneLessTool is an MCP server listed in the public MCP registry as com.onelesstool/onelesstool. Find software subscriptions you can drop using tools you already own, with vendor-verified prices. This page covers its hosted endpoint (https://onelesstool.com/api/mcp).

### Is the OneLessTool MCP server safe to use?

OneLessTool scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the OneLessTool MCP server expose?

OneLessTool exposes 9 tools: search_catalog, get_tool, find_alternatives, compare_solutions, find_workflows, and 4 more. Their descriptions and schemas cost roughly 852 tokens of context every time the server is loaded.

### Does the OneLessTool MCP server require authentication?

No. We connected to OneLessTool without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the OneLessTool MCP server still maintained?

OneLessTool is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://onelesstool.com/api/mcp
- Website: https://onelesstool.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-onelesstool-onelesstool/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-onelesstool-onelesstool/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-onelesstool-onelesstool/api-mcp