# Strale - 290+ API capabilities for AI agents (remote · api.strale.io)

290+ quality-scored API capabilities for AI agents across 27 countries via MCP.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.strale.io`: 69/100 (this document), [markdown](https://verifymcp.io/servers/strale-io-strale/api.md), [page](https://verifymcp.io/servers/strale-io-strale/api)
- npm · `strale-mcp`: 65/100, [markdown](https://verifymcp.io/servers/strale-io-strale/strale-mcp.md), [page](https://verifymcp.io/servers/strale-io-strale/strale-mcp)

## Channel facts

- Endpoint: `https://api.strale.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.4`

## 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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1348 tokens (~149/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**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http strale-io-strale https://api.strale.io/mcp
```

### Codex

```toml
[mcp_servers.strale-io-strale]
url = "https://api.strale.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add strale-io-strale --url https://api.strale.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  strale-io-strale:
    url: "https://api.strale.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "strale-io-strale": {
      "type": "http",
      "url": "https://api.strale.io/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-08-03 (score 69, +1)

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

### 2026-07-31 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 66, +1)

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

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (9)

### `strale_ping` (~66 tokens)

Checks that the Strale API is reachable and the MCP server is running. Call this before a series of capability executions to verify connectivity, or when troubleshooting connection issues. Returns server status, version, tool count, capability count, solution count, and a timestamp. No API key required.

### `strale_getting_started` (~93 tokens)

Lists the free capabilities available without an API key and explains how to get started. Call this on first connection to see what you can do immediately. Returns 5 free capability slugs (email-validate, dns-lookup, json-repair, url-to-markdown, iban-validate) with descriptions, example inputs, and instructions for accessing the full registry of 271 paid capabilities. No API key required.

### `strale_execute` (~205 tokens)

Executes a Strale capability by slug and returns the result. Use this when you need to perform any verification, validation, lookup, or data extraction from the 271-capability registry. Call strale_search first to find the right slug and required input fields. Returns a result object with the capability output, quality score (SQS), latency, price charged, and data provenance. Five free capabilities work without an API key (10/day limit). Paid capabilities debit from the wallet — check strale_balance first for high-value calls.

Input parameters:

- `inputs` (object, required): Input parameters matching the capability's required fields. Check strale_search results for the expected input_fields.
- `max_price_cents` (number): Maximum price in EUR cents. Default: 200 (€2.00). Execution fails if capability costs more.
- `slug` (string, required): Capability slug from strale_search results, e.g. 'swedish-company-data', 'vat-validate', 'iban-validate'

### `strale_search` (~178 tokens)

Searches the Strale capability registry by keyword, category, or natural language query. Use this when you need to find the right capability for a task but don't know the exact slug. Returns matching capabilities and solutions ranked by relevance, each with slug, name, description, category, price in EUR cents, and current SQS quality score. The registry contains 271 capabilities across compliance, finance, web intelligence, developer tools, and more. No API key required to search.

Input parameters:

- `category` (string): Filter by category: compliance, validation, data-extraction, developer-tools, web3, security, domain-intel, recruiting, sales, legal, text
- `offset` (number): Number of results to skip (for pagination). Default: 0
- `query` (string, required): Search keyword (matched against name, description, slug)

### `strale_balance` (~65 tokens)

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.

### `strale_methodology` (~39 tokens)

Returns Strale's trust methodology as a short reference document — covers test cadence, audit-trail integrity, and provenance. No API key required.

### `strale_trust_profile` (~143 tokens)

Returns the trust profile for a capability or solution. Call this before relying on a capability for high-stakes decisions, or when a user asks how reliable a specific check is. Returns SQS score (0-100), Quality grade (A-F), Reliability grade (A-F), execution guidance (direct, retry, queue, or fallback), 30-day test history, known limitations, and cost envelope. No API key required.

Input parameters:

- `slug` (string, required): Capability or solution slug, e.g. 'swedish-company-data' or 'eu-company-due-diligence'
- `type` (string): Whether this is a capability or a bundled solution

### `strale_transaction` (~91 tokens)

Retrieve a past execution record by transaction ID. Returns inputs, outputs, latency, price, data provenance, success/failure status, and failure categorization. Use this to inspect what a previous strale_execute call returned, debug failures, or provide an audit trail. Free-tier transactions are accessible by ID without an API key.

Input parameters:

- `transaction_id` (string, required): Transaction ID returned from a strale_execute call

### `strale_web3_assurance` (~468 tokens)

Returns a decision-ready answer about an on-chain counterparty (wallet, smart contract, token, DeFi protocol, or bridge) in a single call. Surfaces verdict (proceed/review/block/insufficient_evidence), reason_codes (machine-parsable UPPERCASE_SNAKE_CASE), critical_flags, suggested_action, evidence map (sanctions, mixer-graded, scam-cluster, wallet-history, token-safety, contract-verification, protocol-risk, EAS attestations, ERC-8004 reputation, more), and a sidecar audit_url. Two modes: 'outbound' (agent vetting recipient pre-payment, full evaluator set, 8s budget) or 'reverse-call' (service publisher gating an inbound x402 buyer in real-time, critical evaluators only, sub-second SLA). Use before any agent transacts on-chain — sending value, swapping, staking, minting, bridging, or interacting with a contract.

Input parameters:

- `action` (string): Optional intended action. When provided, enables pre-trade simulation (outbound mode) and tunes verdict severity.
- `agent_id` (string): Optional ERC-8004 agent identifier for the calling agent.
- `amount_usd` (number): Optional amount in USD. Sharpens verdict for high-value flows.
- `caller_jurisdiction` (string): Optional ISO country code for jurisdiction-aware verdict (US, EU, UK, etc.).
- `chain` (string): Chain. EVM: 'ethereum' (default), 'base', 'polygon', 'arbitrum', 'optimism', 'bsc'. Or 'solana'.
- `mode` (string): Default 'outbound' (agent → recipient, 8s budget, all evidence). Use 'reverse-call' when you are an x402 service publisher gating an inbound buyer (critical evidence only, sub-second SLA).
- `target` (string, required): On-chain target. EVM wallet/contract/token (0x...), Solana address, or DeFi protocol slug (e.g. 'aave', 'uniswap-v3').
- `target_type` (string): Target kind. Inferred when omitted: 0x... → wallet (default), .eth/.sol → wallet, slug → protocol.

## Diagnostics

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

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 68
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 64

## Links

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