Strale
REMOTE · API.STRALE.IO · 2 COMPONENTS
Hundreds of pay-per-call tools for agents: company records, screening, validation, web reading.
Available components
Last scanned (1 hour ago)
Scores higher than 54% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.23 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Tool “strale_execute” rewrote its description, which is the text the model reads security
- Tool “strale_execute” changed its title: Execute a paid tool → Run a Strale tool cosmetic
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.strale.io/mcp?src=mcp-registry
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.strale.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| strale.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.strale.io/mcp?src=mcp-registry | Unreachable | ||
| http (plaintext) | http://api.strale.io/mcp?src=mcp-registry | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
strale_balance Read wallet balance ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
strale_execute Run a Strale tool ~247
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 capability registry. Inputs follow the capability's own schema, which strale_search lists; the API is documented at https://strale.dev/docs. Call strale_search first to find the right slug and required input fields. Returns a result object with the capability output, latency, price charged, and data provenance. Several capabilities are free without an API key (monthly per-IP allowance; see GET /v1/platform/facts, static.free_tier_monthly_limit) — strale_search reports which. Paid capabilities debit from the wallet — check strale_balance first for high-value calls.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | object | yes | 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 | yes | Capability slug from strale_search results, e.g. 'swedish-company-data', 'vat-validate', 'iban-validate' |
No output schema declared.
No examples provided.
strale_getting_started Get started with Strale ~70
Explains how to start using Strale and what is available without credentials. Call this on first connection. Returns the current free-tier capability list with example inputs, the pay-per-call (x402) route that needs no signup, and how to reach the full registry. No API key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
strale_methodology Read testing and source notes ~26
Explains testing modes, source context and transaction retrieval. No API key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
strale_ping Check connection ~66
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
strale_search Search tools and bundles ~169
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, and price in EUR cents. The registry spans company data, compliance, finance, web intelligence, and developer tools. No API key required to search.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Search keyword (matched against name, description, slug) |
No output schema declared.
No examples provided.
strale_transaction Read a transaction record ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | string | yes | Transaction ID returned from a strale_execute call |
No output schema declared.
No examples provided.
strale_trust_profile Read current test and availability signals ~98
Reads current public test results for a tool or bundle: badge, tested flag, recent pass rate and last-tested time where available. Use the catalogue for inputs, limitations and sources. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 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 |
No output schema declared.
No examples provided.
strale_web3_assurance Check on-chain counterparty ~468
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, limited evaluator set). Use before any agent transacts on-chain — sending value, swapping, staking, minting, bridging, or interacting with a contract.
| Name | Type | Req | Description |
|---|---|---|---|
| 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, limited evaluator set). |
| target | string | yes | 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. |
No output schema declared.
No examples provided.
How do I install the Strale MCP server?
Strale is a hosted endpoint at https://api.strale.io/mcp?src=mcp-registry, 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.
remote · api.strale.io
claude mcp add --transport http strale-io-strale 'https://api.strale.io/mcp?src=mcp-registry'
What is the Strale MCP server?
Strale is an MCP server listed in the public MCP registry as io.github.strale-io/strale. Hundreds of pay-per-call tools for agents: company records, screening, validation, web reading. This page covers its hosted endpoint (https://api.strale.io/mcp?src=mcp-registry).
Is the Strale MCP server safe to use?
Strale scores 69 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 Strale MCP server expose?
Strale exposes 9 tools: strale_ping, strale_getting_started, strale_execute, strale_search, strale_balance, and 4 more. Their descriptions and schemas cost roughly 1,300 tokens of context every time the server is loaded.
Does the Strale MCP server require authentication?
Its publisher declares no required credentials for Strale. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Strale MCP server still maintained?
Strale is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.