_ registry / mcp + a2a streamable-http · checked 41m ago

losbeto

https://api.losbeto.xyz

Registry code: 98be46d0d40e2ad0

api record

Cross-asset market data: Brazil (central bank, B3), US equities, forex, commodities, macro and crypto.

Workflow: call search_market_data with the question in plain language, then get_market_data with the endpoint it returns. For broad questions use market_snapshot instead.

endpoint
https://api.losbeto.xyz/mcp
door code
24d1a3cb3d5c45e8
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is losbeto live?
Yes — it answered the hub's last check (checked 41m ago). It answered 99% of checks over the last 30 days.
Is losbeto free to use?
Yes — the hub reached it with no key and no payment.
What tools does losbeto have?
5 tools: market_snapshot, list_categories, account_status, search_market_data, get_market_data.
Is losbeto 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
99.1%

90 days 99.1%· all time 99.3%

latency
197ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1309 checks · signed record
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get market data
  • search market data endpoints
  • check account status
  • list market data categories
  • get market snapshot
takes → gives
text → data
tools
5 reads
_ 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 also stands behind 1 other origin: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
38

distinct

settlements
6,321

last 2026-11-05

received on chain
402.5084 USDC

concentrated, shared-payto

_ what it can do 5 tools
4 open 1 never probed 4 of 5 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.

  • list_categories reads open 41m ago

    FREE. The catalog at a glance: every category, how many endpoints it holds and the cheapest price in it. Use when you want to know what this service covers before searching.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • account_status reads open 41m ago

    FREE. Check whether this connection has an active subscription, how much credit is left and when it expires. Also returns how to subscribe (plans from $0.10). Call this if a request returned delayed data and you need live.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_market_data reads open 41m ago

    FREE. FIRST STEP for any market-data question. Describe what you need in plain language and get back the endpoints that cover it, with their price and parameters. Covers Brazil (central bank, B3), US equities, forex, commodities, macro, crypto and AI research. Examples: 'Brazilian interest rate and inflation', 'gold price', 'is this Solana token a rug pull', 'correlation between bitcoin and the S&P', 'what is the Ibovespa doing'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "description": "Max results (default 8)."
        },
        "query": {
          "type": "string",
          "description": "What you are looking for, in plain language."
        }
      }
    }
    arguments 17 lines
  • get_market_data reads open 23h ago

    FREE for the delayed sample; the endpoint's x402 price applies for live data (from $0.001/call). Fetch data from an endpoint returned by search_market_data. Without a subscription this returns a REAL but delayed sample at no cost — enough to see the exact response shape and judge the data. With an active subscription key it returns live data. Live data is also purchasable per call in USDC over x402 at https://api.losbeto.xyz.

    mcp-tool

    {
      "type": "object",
      "required": [
        "endpoint"
      ],
      "properties": {
        "params": {
          "type": "object",
          "description": "Query parameters, e.g. {\"symbol\": \"PETR4\"}."
        },
        "endpoint": {
          "type": "string",
          "examples": [
            "/br-macro",
            "/oracle-consensus",
            "/commodity-price"
          ],
          "description": "Endpoint path, e.g. '/br-macro' or '/oracle-consensus'."
        }
      }
    }
    arguments 21 lines
  • market_snapshot reads unknown never probed

    FREE for delayed samples; live components billed at each endpoint's x402 price. One call for a whole area instead of several. 'brazil' returns central-bank macro, the real interest rate, Ibovespa and B3 blue chips together; 'global' returns forex, commodities, equities and macro regime; 'crypto' returns oracle consensus, sentiment and market regime. Use this when the question is broad rather than about one number.

    mcp-tool

    {
      "type": "object",
      "required": [
        "scope"
      ],
      "properties": {
        "scope": {
          "enum": [
            "brazil",
            "global",
            "crypto"
          ],
          "type": "string",
          "description": "Which area to snapshot."
        }
      }
    }
    arguments 17 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 98be46d0d40e2ad0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/98be46d0d40e2ad0/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/98be46d0d40e2ad0/badge.svg)](https://brick.blue/agent/98be46d0d40e2ad0?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
90%

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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.