_ registry / mcp + a2a http-sse · checked 1h ago

strale

https://api.strale.io

Registry code: ec577f222f0cdbbb

api record

250+ business data and compliance tools for AI agents via MCP. IBAN validation, VAT format checks, sanctions screening, company lookups, SSL certificate checks, domain reputation, and more. Each capability independently tested with quality scores. x402 USDC micropayments on Base. Also available as REST API.

from a public catalogue that lists it, not from the operator

endpoint
https://api.strale.io/mcp
door code
c9e8c66060212da1
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
20 · newcomer
_ is it live, free and safe measured by this hub
Is strale live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is strale free to use?
Yes — the hub reached it with no key and no payment.
What tools does strale have?
9 tools: strale_search, strale_web3_assurance, strale_transaction, strale_execute, strale_trust_profile, strale_ping, strale_getting_started, strale_balance, ….
Is strale safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.8%· all time 99.5%

latency
150ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1299 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • validate an iban
  • screen for sanctions
  • look up a company
  • check a vat number
  • assess an on-chain counterparty
takes → gives
text → data
tools
8 reads1 effect unclear
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 410 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

payers on base
19

distinct

settlements
9,125

last 2026-11-10

received on chain
382.6332 USDC

concentrated

_ what it can do 9 tools
4 open 5 never probed 4 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • strale_ping reads open 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • strale_getting_started reads open 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • strale_balance reads open 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • strale_methodology reads open 13h ago

    Explains testing modes, source context and transaction retrieval. No API key required.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • strale_search reads unknown 6h ago

    Searches the Strale capability registry by keyword, category, or natural language query. Returns matching capabilities and bundles with slugs, descriptions and input fields where available. Bundle prices are integer EUR cents in price_cents, with price_formatted for display and price as a compatibility alias. Capability prices are null in discovery; null does not mean free. For capabilities, is_free_tier identifies tools that run without payment; anonymous calls have a monthly per-IP allowance. No API key required to search.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Search keyword (matched against name, description, slug)"
        },
        "offset": {
          "type": "number",
          "description": "Number of results to skip (for pagination). Default: 0"
        },
        "category": {
          "type": "string",
          "description": "Filter by category: compliance, validation, data-extraction, developer-tools, web3, security, domain-intel, recruiting, sales, legal, text"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • strale_web3_assurance reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "target"
      ],
      "properties": {
        "mode": {
          "enum": [
            "outbound",
            "reverse-call"
          ],
          "type": "string",
          "description": "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)."
        },
        "chain": {
          "type": "string",
          "description": "Chain. EVM: 'ethereum' (default), 'base', 'polygon', 'arbitrum', 'optimism', 'bsc'. Or 'solana'."
        },
        "action": {
          "enum": [
            "send_payment",
            "swap",
            "stake",
            "mint",
            "interact",
            "bridge"
          ],
          "type": "string",
          "description": "Optional intended action. When provided, enables pre-trade simulation (outbound mode) and tunes verdict severity."
        },
        "target": {
          "type": "string",
          "description": "On-chain target. EVM wallet/contract/token (0x...), Solana address, or DeFi protocol slug (e.g. 'aave', 'uniswap-v3')."
        },
        "agent_id": {
          "type": "string",
          "description": "Optional ERC-8004 agent identifier for the calling agent."
        },
        "amount_usd": {
          "type": "number",
          "description": "Optional amount in USD. Sharpens verdict for high-value flows."
        },
        "target_type": {
          "enum": [
            "wallet",
            "contract",
            "token",
            "protocol",
            "bridge",
            "domain"
          ],
          "type": "string",
          "description": "Target kind. Inferred when omitted: 0x... → wallet (default), .eth/.sol → wallet, slug → protocol."
        },
        "caller_jurisdiction": {
          "type": "string",
          "description": "Optional ISO country code for jurisdiction-aware verdict (US, EU, UK, etc.)."
        }
      },
      "additionalProperties": false
    }
    arguments 62 lines
  • strale_transaction reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "transaction_id"
      ],
      "properties": {
        "transaction_id": {
          "type": "string",
          "description": "Transaction ID returned from a strale_execute call"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • strale_execute unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug",
        "inputs"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Capability slug from strale_search results, e.g. 'swedish-company-data', 'vat-validate', 'iban-validate'"
        },
        "inputs": {
          "type": "object",
          "description": "Input parameters matching the capability's required fields. Check strale_search results for the expected input_fields.",
          "additionalProperties": {}
        },
        "max_price_cents": {
          "type": "number",
          "description": "Maximum price in EUR cents. Default: 200 (€2.00). Execution fails if capability costs more."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • strale_trust_profile reads unknown 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Capability or solution slug, e.g. 'swedish-company-data' or 'eu-company-due-diligence'"
        },
        "type": {
          "enum": [
            "capability",
            "solution"
          ],
          "type": "string",
          "default": "capability",
          "description": "Whether this is a capability or a bundled solution"
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ec577f222f0cdbbb.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ec577f222f0cdbbb/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ec577f222f0cdbbb/badge.svg)](https://brick.blue/agent/ec577f222f0cdbbb?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
145ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.