Home / MCP registry index / io.github.strale-io/strale

Strale - 290+ API capabilities for AI agents

io.github.strale-io/strale in the official MCP registry. Endpoint https://api.strale.io/mcp. Source: github.com/strale-io/strale.

The registry describes it as: 290+ quality-scored API capabilities for AI agents across 27 countries via MCP.

We read its 9 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

strale_ping strale_getting_started strale_execute strale_search strale_balance strale_methodology strale_trust_profile strale_transaction strale_web3_assurance

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-strale-io-strale/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-strale-io-strale)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.