Strale
NPM · STRALE-MCP · 2 COMPONENTS
Hundreds of pay-per-call tools for agents: company records, screening, validation, web reading.
Available components
Last scanned (29 minutes ago)
Scores higher than 93% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to strale-io/strale). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1300 tokens (~144/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +16
- Stability: 0.97 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.2.10 → 0.2.11 functional
- Package version: 0.2.4 → 0.2.11 functional
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.4 → 0.2.10 functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −2
- Stability: pass → 0.90 functional
- 31 Oct 26 0
- Package version: 0.2.4 → 0.2.9 functional
- 29 Oct 26 0
- Package version: 0.2.4 → 0.2.9 functional
- 28 Oct 26 +11
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Provenance: fail → pass ▲ security
- Stability: 0.97 → pass security
- The attested source repository moved: strale-io/strale security
- Schema quality: 117 → 141 ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Package version: 0.2.4 → 0.2.9 functional
- 27 Oct 26 0
- Stability: pass → 0.97 functional
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 6 Nov 2026 · Analysed npm/strale-mcp@0.2.11
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | strale-io/strale |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/strale-io/strale/.github/workflows/release-npm.yml@refs/heads/main |
| Rekor log index | 3715230479 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:97e30dc03219641c529f4e4f72c71f9f55886f00daa377300a0f93616913521e140e3913e4bd754271421dee3d0f78fdd25d7c34afb91e9e103957e58 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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.io/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 runs locally as an npm package, launched with npx -y strale-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · strale-mcp
claude mcp add strale-io-strale -- npx -y strale-mcp
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 npm package (strale-mcp).
Is the Strale MCP server safe to use?
Strale scores 89 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.
Is the Strale MCP server still maintained?
Strale is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Strale MCP server under?
Strale declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Strale MCP server?
VerifyMCP ran 16 checks on Strale, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.