_ registry / mcp streamable-http · checked 2h ago

onelesstool

https://onelesstool.com

Registry code: 3997709776b49791

api record

OneLessTool helps people stop paying for software they don't need by finding what they can do with tools they already own.

How to use these tools well:

endpoint
https://onelesstool.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is onelesstool live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is onelesstool free to use?
Yes — the hub reached it with no key and no payment.
What tools does onelesstool have?
9 tools: get_pricing, estimate_savings, get_tool, search_catalog, find_alternatives, get_workflow, recommend_stack, compare_solutions, ….
Is onelesstool safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
821ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 open 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • find_workflows open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 300
        },
        "capability": {
          "type": "string",
          "maxLength": 80
        },
        "replaces_tool": {
          "type": "string",
          "maxLength": 80,
          "description": "Only workflows that replace this tool"
        }
      }
    }
    arguments 24 lines
  • get_pricing unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "tool": {
          "type": "string",
          "maxLength": 80
        }
      }
    }
    arguments 10 lines
  • estimate_savings unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "subscriptions"
      ],
      "properties": {
        "skill": {
          "enum": [
            "none",
            "basic",
            "technical"
          ],
          "type": "string"
        },
        "subscriptions": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "tool",
              "monthly_cost_usd"
            ],
            "properties": {
              "plan": {
                "type": "string",
                "maxLength": 80
              },
              "tool": {
                "type": "string",
                "maxLength": 80,
                "minLength": 1,
                "description": "Tool name or slug"
              },
              "seats": {
                "type": "integer",
                "maximum": 100000,
                "minimum": 1
              },
              "usage": {
                "enum": [
                  "daily",
                  "weekly",
                  "monthly",
                  "rarely",
                  "never"
                ],
                "type": "string"
              },
              "criticality": {
                "enum": [
                  "low",
                  "medium",
                  "high"
                ],
                "type": "string"
              },
              "monthly_cost_usd": {
                "type": "number",
                "maximum": 1000000,
                "minimum": 0,
                "description": "What they pay per month in total"
              },
              "capabilities_used": {
                "type": "array",
                "items": {
                  "type": "string",
                  "maxLength": 80
                },
                "maxItems": 30,
                "description": "Capability slugs they actually use it for (improves accuracy)"
              }
            }
          },
          "maxItems": 60,
          "minItems": 1
        }
      }
    }
    arguments 79 lines
  • get_tool unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tool"
      ],
      "properties": {
        "tool": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Tool name or slug, e.g. 'Canva' or 'canva'"
        }
      }
    }
    arguments 15 lines
  • search_catalog unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "kinds": {
          "type": "array",
          "items": {
            "enum": [
              "tool",
              "capability",
              "workflow",
              "guide"
            ],
            "type": "string"
          },
          "description": "Restrict result types"
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "query": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "What the user is looking for: a product name, a task, or an outcome"
        }
      }
    }
    arguments 34 lines
  • find_alternatives unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tool"
      ],
      "properties": {
        "tool": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "The tool the user is considering dropping"
        },
        "team_size": {
          "type": "integer",
          "maximum": 10000,
          "minimum": 1,
          "description": "People who need access (affects per-seat costs)"
        },
        "owned_tools": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 80
          },
          "maxItems": 50,
          "description": "Tools the user already pays for, by name or slug, e.g. [\"ChatGPT Plus\", \"google-workspace\"]"
        },
        "capabilities": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 80
          },
          "maxItems": 20,
          "description": "Capability slugs the user actually uses this tool for (default: its core capabilities)"
        }
      }
    }
    arguments 39 lines
  • get_workflow unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1
        },
        "sections": {
          "type": "array",
          "items": {
            "enum": [
              "overview",
              "steps",
              "prompts",
              "artifacts",
              "limitations",
              "verification",
              "savings"
            ],
            "type": "string"
          },
          "description": "Return only these sections to save context (default: all)"
        }
      }
    }
    arguments 30 lines
  • recommend_stack unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 300,
          "description": "Outcome in plain English, e.g. 'I need 15 YouTube thumbnails a month and a simple CRM'"
        },
        "skill": {
          "enum": [
            "none",
            "basic",
            "technical"
          ],
          "type": "string",
          "description": "User's technical skill"
        },
        "team_size": {
          "type": "integer",
          "maximum": 10000,
          "minimum": 1
        },
        "owned_tools": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 80
          },
          "maxItems": 50,
          "description": "Tools the user already pays for, by name or slug, e.g. [\"ChatGPT Plus\", \"google-workspace\"]"
        },
        "capabilities": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 80
          },
          "maxItems": 20
        },
        "sensitive_data": {
          "type": "boolean"
        },
        "needs_collaboration": {
          "type": "boolean"
        }
      }
    }
    arguments 48 lines
  • compare_solutions unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "capability"
      ],
      "properties": {
        "capability": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1,
          "description": "Capability slug, or a phrase like 'make thumbnails' (resolved via search)"
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3997709776b49791.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3997709776b49791/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3997709776b49791/badge.svg)](https://brick.blue/agent/3997709776b49791?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.