Strale - 290+ API capabilities for AI agents
NPM · STRALE-MCP · 2 COMPONENTS · SCANNED SEP 22
290+ quality-scored API capabilities for AI agents across 27 countries via MCP.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 30 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 943 tokens (~117/item across 8 items; 8 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "strale_execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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
How do I install the Strale - 290+ API capabilities for AI agents MCP server?
Strale - 290+ API capabilities for AI agents 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
{
"mcpServers": {
"strale-io-strale": {
"command": "npx",
"args": [
"-y",
"strale-mcp"
]
}
}
} {
"servers": {
"strale-io-strale": {
"command": "npx",
"args": [
"-y",
"strale-mcp"
]
}
}
} codex mcp add strale-io-strale -- npx -y strale-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"strale-io-strale": {
"type": "local",
"command": [
"npx",
"-y",
"strale-mcp"
],
"enabled": true
}
}
} openclaw mcp add strale-io-strale --command npx --arg -y --arg strale-mcp
mcp_servers:
strale-io-strale:
command: "npx"
args: ["-y", "strale-mcp"] {
"McpServers": {
"strale-io-strale": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"strale-mcp"
]
}
}
} assistant mcp add strale-io-strale -t stdio -c npx -a -y strale-mcp
{
"mcpServers": {
"strale-io-strale": {
"command": "npx",
"args": [
"-y",
"strale-mcp"
]
}
}
} 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.
- 21 Sept 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.
- 19 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 −2
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 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 22 Sept 2026 · Analysed npm/strale-mcp@0.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 ~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 ~205
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.
| 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 ~93
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
strale_methodology ~102
Returns the Strale Quality Score (SQS) methodology as a full reference document. Call this when you need to understand how capability quality scores are computed, or when a user asks how trust is evaluated. Returns a markdown document covering the dual-profile scoring model (Quality Profile + Reliability Profile), the 5x5 SQS matrix, execution guidance strategies, test infrastructure, provenance tracking, audit trails, badge system, and current limitations. No API key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
strale_ping ~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 ~178
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.
| 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 ~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 ~143
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.
| 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.
What is the Strale - 290+ API capabilities for AI agents MCP server?
Strale - 290+ API capabilities for AI agents is an MCP server listed in the public MCP registry as io.github.strale-io/strale. 290+ quality-scored API capabilities for AI agents across 27 countries via MCP. This page covers its npm package (strale-mcp).
Is the Strale - 290+ API capabilities for AI agents MCP server safe to use?
Strale - 290+ API capabilities for AI agents scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 - 290+ API capabilities for AI agents MCP server expose?
Strale - 290+ API capabilities for AI agents exposes 8 tools: strale_ping, strale_getting_started, strale_execute, strale_search, strale_balance, and 3 more. Their descriptions and schemas cost roughly 943 tokens of context every time the server is loaded.
Is the Strale - 290+ API capabilities for AI agents MCP server still maintained?
Strale - 290+ API capabilities for AI agents is still listed as active in the MCP registry. We last reached this channel on 22 September 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 - 290+ API capabilities for AI agents MCP server under?
Strale - 290+ API capabilities for AI agents declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.