Labsco
MCP SERVER

Strale

by strale-io

Search a registry of verified checks — company registries, compliance, financial validation, Web3 security — read the evidence behind one before relying on it, run it under a price ceiling, and pull the transaction record afterwards.

MCP Plumbing: Proxies, Registries & InspectorsVerified
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 plus a key — npx -y strale-mcp, then supply credentials