Is io.github.rmartins1451/losbeto up? Live MCP status

Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2024-11-05.

A stock client connected with no credential and negotiated 2024-11-05. Use it.

Outcomeusable
HTTP status200
Protocol version2024-11-05
Server says it islosbeto 48.23.0-FORKSAFE
Answered in212 ms
Endpoint checkedhttps://api.losbeto.xyz/mcp
Checked

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardPublished, does not validate: an A2A 0.3 card: no `supportedInterfaces`, which 1.0 requires in place of `url` and `protocolVersion`. A2A 0.3 shape; 116 skills.
/.well-known/agent-card.json
MCP server card (SEP-2127)Published, does not validate: `$schema` must be https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json (and 1 more). not served as application/mcp-server-card+json.
https://api.losbeto.xyz/mcp/server-card
MCP server card (SEP-1649 location)Published, valid. SEP-1649 shape; losbeto 48.23.0; MCP 2024-11-05; streamable-http.
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryPublished, does not validate: keys[0]: `alg` EdDSA is not in the HTTP Signature Algorithms registry (§5.5.1) (and 2 more). 1 key (Ed25519); the response is signed (not verified).
/.well-known/http-message-signatures-directory

Read at https://api.losbeto.xyz with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 5 tools: account_status, get_market_data, list_categories, market_snapshot, search_market_data.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameio.github.rmartins1451/losbeto
TitleLosbeto — Market Data for AI Agents
DescriptionMarket data, ML forecasts, Brazil macro, LLM inference, agent intel. USDC via x402 + MPP/Tempo.
Endpointhttps://api.losbeto.xyz/mcp
Publisher repositoryhttps://github.com/rmartins1451/losbeto
Version48.23.0
Listing updated

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy