LABSCO SUMMARY

It publishes the evidence behind a check rather than a score you have to take on faith.

Strale retired its single 0-100 composite deliberately, on the grounds that it compressed unrelated failure modes into one number that looked more precise than it was. What you get instead is the raw material — lifecycle state, when it was last tested, recent test history, stated coverage gaps and the upstream behind it — and capabilities that drop below the quality floor on real traffic are quarantined automatically. Execution carries a price ceiling and reports what was actually charged with provenance attached, and every past call, including the failures, stays retrievable by id.

What it is

A capability marketplace for agents: rather than integrating each upstream yourself, you search a registry, execute a capability by slug, and get an audit record back. It is reachable as a remote endpoint with no install, or locally over stdio, and a handful of capabilities run with no key at all.

What you get

strale_search finds the right capability by keyword, category or plain-language description, returning slug, description, category and price so you can choose before committing.
strale_execute runs one by slug under a price ceiling, returning the output alongside latency, the price actually charged and the provenance of the data.
strale_trust_profile is the call to make before depending on a check for a high-stakes decision: it returns that capability's evidence — recent test history, known limitations and the source behind it.
strale_methodology returns the full reference for how capability quality is assessed, as a document rather than a claim.
strale_getting_started lists what runs free without a key — email validation, DNS lookup, JSON repair, URL to markdown and IBAN validation — with example inputs.
strale_balance reports the wallet in EUR cents before a paid run, and strale_transaction retrieves any past execution by id with its inputs, outputs, latency, price, provenance and how a failure failed.
strale_ping confirms the API is reachable and the server running, which is worth doing before a series of paid calls.
Bundled solutions cover multi-step workflows — a full KYB check, company due diligence — as one capability rather than a chain you assemble.
A Web3 set alongside the rest: wallet risk scoring, token honeypot detection, ENS resolution, DeFi protocol TVL and fees, a gas oracle and EU MiCA VASP verification.

Requirements

Nothing for the free path: five capabilities — email validation, DNS lookup, JSON repair, URL to markdown, IBAN validation — run with no key, and so do the connectivity and getting-started calls. Everything else needs a Strale API key and funds in the wallet, which the balance call reports in EUR cents; a key comes with free credits to start. Point a client at the hosted endpoint with a bearer token and install nothing, or run the npm package locally with the key in the environment.

Setup effort

One command — npx -y strale-mcp

See installation options

USE CASES

01

Finding the right check without knowing what it is called

Describe the task and get matching capabilities ranked, each with its slug, price and required inputs, then run the one you picked.

strale_searchstrale_execute

02

Deciding whether a capability is reliable enough to depend on

Read its trust profile — recent test history, known limitations, the data source — before a compliance answer rests on it. No key needed to look.

strale_trust_profilestrale_methodology

03

Trying it before paying for anything

Run the free capabilities — validate an IBAN or an email, repair broken JSON, turn a URL into markdown — with no account at all.

strale_getting_startedstrale_execute

04

Running a paid check without an open-ended bill

Check the wallet, set a price ceiling on the call, and read back what was actually charged.

strale_balancestrale_execute

05

Auditing what a previous call actually did

Retrieve the execution by id with its inputs, outputs, latency, price and provenance — including the failures and how they were categorised.

strale_transactionstrale_ping

8 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`strale_balance`

Returns the current Strale wallet balance. Call this before executing paid capabilities to verify sufficient funds, or after a series of calls to reconcile spend. Returns balance in EUR cents (integer) and formatted EUR string. Requires an API key — returns an auth instruction if none is configured.

BEFORE YOU INSTALL

What to know first

Tools you get

8 tools when we connected. The 250+ figure is the LangChain and Composio toolkit. Over MCP, capabilities are found with strale_search and run through strale_execute, and your key decides which ones run.

Optional

STRALE_API_KEY in your environment

Where it runs

Of the 2 documented setups, 1 runs the server on your machine and 1 connects to a hosted endpoint.

CONTEXT COST

Light Standing cost

Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are

INSTALLATION

Connect your client

Server setup

npx

TERMINAL

npx -y strale-mcp

Hosted endpoint

ENDPOINT URL

https://api.strale.io/mcp

Add this hosted endpoint to your MCP client.

MCP Clients

Any MCP client — remote

ANY MCP CLIENT — REMOTE · JSON

{
  "mcpServers": {
    "strale": {
      "type": "streamableHttp",
      "url": "https://api.strale.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_KEY>"
      }
    }
  }
}

Clients spell the "type" value differently: Claude Code and VS Code use "http", Cline uses "streamableHttp", and Roo Code uses "streamable-http". Claude Desktop does not accept a URL entry in its config file; remote servers go under Settings → Connectors.

Any MCP client — stdio

ANY MCP CLIENT — STDIO · JSON

{
  "mcpServers": {
    "strale": {
      "command": "npx",
      "args": [
        "-y",
        "strale-mcp"
      ],
      "env": {
        "STRALE_API_KEY": "<YOUR_STRALE_API_KEY>"
      }
    }
  }
}

Strale

It publishes the evidence behind a check rather than a score you have to take on faith.

What it is

What you get

Requirements

Setup effort

Finding the right check without knowing what it is called

Deciding whether a capability is reliable enough to depend on

Trying it before paying for anything

Running a paid check without an open-ended bill

Auditing what a previous call actually did

8 tools

`strale_balance`

`strale_execute`

`strale_getting_started`

`strale_methodology`

`strale_ping`

`strale_search`

`strale_transaction`

`strale_trust_profile`

What to know first

Tools you get

Optional

Where it runs

Light Standing cost

Connect your client

Server setup

npx

Hosted endpoint

MCP Clients

Any MCP client — remote

Any MCP client — stdio

Strale

It publishes the evidence behind a check rather than a score you have to take on faith.

What it is

What you get

Requirements

Setup effort

Finding the right check without knowing what it is called

Deciding whether a capability is reliable enough to depend on

Trying it before paying for anything

Running a paid check without an open-ended bill

Auditing what a previous call actually did

8 tools

strale_balance

strale_execute

strale_getting_started

strale_methodology

strale_ping

strale_search

strale_transaction

strale_trust_profile

What to know first

Tools you get

Optional

Where it runs

Light Standing cost

Connect your client

Server setup

npx

Hosted endpoint

MCP Clients

Any MCP client — remote

Any MCP client — stdio

Same category

Dominion Observatory

Salestools Club

Agent Guild

KnyazevAI MCP Catalog

`strale_balance`

`strale_execute`

`strale_getting_started`

`strale_methodology`

`strale_ping`

`strale_search`

`strale_transaction`

`strale_trust_profile`