Skip to content

Strale MCP server

io.github.strale-io/stralestrale-iostreamable-httpv0.2.12Scanned

Hundreds of pay-per-call tools for agents: company records, screening, validation, web reading.

9 tools: 1 can delete or cancel things and 8 only read.

Tools: 1 delete, 0 irreversible, 0 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Strale MCP server can do

The Strale MCP server is published by the GitHub account strale-io. It has 9 tools. It can delete or cancel things (1 tool: strale_execute). 8 tools only read.

2 tools bring in text other people can write (strale_execute and strale_web3_assurance).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.2.12.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • strale_executeExecutes a Strale capability by slug and returns the result.Reads text others writeNo findings

    Why it is in this group

    • The name "strale_execute" says "execute": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Only reads 8Show 8 read-only tools
  • strale_balanceReturns the current Strale wallet balance.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • strale_getting_startedExplains how to start using Strale and what is available without credentials.1 finding

    Why it is in this group

    • The description's first verb is "explain": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...ng Strale and what is available without credentials. Call this on first connection. Returns..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • strale_methodologyExplains testing modes, source context and transaction retrieval.No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    Explains testing modes, source context and transaction retrieval. No API key required.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • strale_pingChecks that the Strale API is reachable and the MCP server is running.No findings

    Why it is in this group

    • The name "strale_ping" says "ping": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • strale_transactionRetrieves a past execution record by transaction ID, including status, latency and price.No findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.
    Description, as the server wrote it
    Retrieves a past execution record by transaction ID, including status, latency and price. Authenticated callers can read their own retained inputs, outputs, provenance and error details. Without authentication, free-tier lookups return only redacted metadata: inputs, outputs, errors, provenance and the audit body are omitted. Paid transaction lookup requires authentication. Use this to inspect a previous strale_execute call or debug a failure.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • strale_trust_profileReads current public test results for a tool or bundle: badge, tested flag, recent pass rate and last-tested time where available.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • strale_web3_assuranceReturns a decision-ready answer about an on-chain counterparty (wallet, smart contract, token, DeFi protocol, or bridge) in a single call.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 destructive). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.strale.io/mcp?src=mcp-registry: tools/list returned 9 tools to an anonymous client, including strale_execute (destructive)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. Tools1 changed.~1 changedView diff
  3. Tools1 changed.~1 changedView diff
  4. Tools9 changed.~9 changedView diff

Install

Pinned to version 0.2.12. Values in angle brackets are yours to fill in.

claude mcp add --transport http strale https://api.strale.io/mcp?src=mcp-registry
claude mcp add --transport http strale https://api.strale.io/mcp?src=mcp-registry

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__strale__strale_ping",
      "mcp__strale__strale_getting_started",
      "mcp__strale__strale_search",
      "mcp__strale__strale_balance",
      "mcp__strale__strale_methodology",
      "mcp__strale__strale_trust_profile",
      "mcp__strale__strale_transaction",
      "mcp__strale__strale_web3_assurance"
    ],
    "ask": [],
    "deny": [
      "mcp__strale__strale_execute"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as strale. Review it before you use it.

Capability tags behind 2 rules
  • mcp__strale__strale_execute untrusted-input
  • mcp__strale__strale_web3_assurance untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.strale-io/strale/verify?hash=2d101cbdf3932383be1e5b960da23b071a87439a2b44e08c3f2f54aa06724dfb" | jq -e '.changed == false'

Pinned hash 2d101cbdf393, from Nov 20, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.strale-io/strale/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.strale-io/strale
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.strale-io/strale.svg)](https://radar.anlyon.com/servers/io.github.strale-io/strale)

Source: MCP Registry · repository. Synced Nov 6, 2026, 14:18 UTC.

Strale MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Strale MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Strale MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: strale_execute.

Can the Strale MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Strale MCP server have?

9 tools: 1 destructive, 8 read. strale_execute, strale_ping, strale_getting_started, strale_search, strale_balance, strale_methodology, strale_trust_profile, strale_transaction and 1 more.

Does the Strale MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Strale MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Strale MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.