Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SigmaDiario — Datos de Argentina

REMOTE · SIGMADIARIO.COM

Live Argentina data: dolar rates, quiniela and lotteries, holidays, river levels, inflation, news.

Available components

0 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 317 tokens (~45/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 0
    • HSTS header: unverified → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://sigmadiario.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sigmadiario.com CN=WE1,O=Google Trust Services,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA256 4e45ff8829d7f46413837b9aa8c63761
SANs: sigmadiario.com, *.sigmadiario.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sigmadiario.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
sigmadiario.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sigmadiario.com/api/mcp Verified 200
http (plaintext) http://sigmadiario.com/api/mcp HTTPS enforced 308 https://sigmadiario.com/api/mcp
MCP tools · 7 exposed · ~271 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_dolar ~43

Cotizaciones del dólar en Argentina ahora (blue, oficial, MEP, CCL, tarjeta, cripto) con compra/venta y serie de 30 días.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_feriados ~29

Próximos feriados de Argentina, con cuántos días faltan para cada uno.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_inflacion ~28

Inflación de Argentina: IPC mensual e interanual del INDEC con serie histórica.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_loterias ~33

Últimos resultados de Quini 6, Loto Plus, Brinco y Telekino con pozos.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_quiniela ~40

Resultados de la quiniela argentina de hoy: cabezas por lotería (Nacional, Provincia y provinciales), sorteo por sorteo.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_rios ~38

Altura de los ríos Paraná, Paraguay y Uruguay hoy (parte oficial de Prefectura Naval), puerto por puerto con variación diaria.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_news ~60

Titulares recientes de SigmaDiario; opcionalmente filtrados por palabra clave.

NameTypeReqDescription
limitnumber–Máximo de titulares (1-25, default 10)
querystring–Palabra clave en el título (opcional)

No output schema declared.

No examples provided.

Install

How do I install the SigmaDiario — Datos de Argentina MCP server?

SigmaDiario — Datos de Argentina is a hosted endpoint at https://sigmadiario.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · sigmadiario.com

# add to Claude Code
claude mcp add --transport http com-sigmadiario-datos-argentina 'https://sigmadiario.com/api/mcp'
Common questions

What is the SigmaDiario — Datos de Argentina MCP server?

SigmaDiario — Datos de Argentina is an MCP server listed in the public MCP registry as com.sigmadiario/datos-argentina. Live Argentina data: dolar rates, quiniela and lotteries, holidays, river levels, inflation, news. This page covers its hosted endpoint (https://sigmadiario.com/api/mcp).

Is the SigmaDiario — Datos de Argentina MCP server safe to use?

SigmaDiario — Datos de Argentina scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SigmaDiario — Datos de Argentina MCP server expose?

SigmaDiario — Datos de Argentina exposes 7 tools: get_dolar, get_quiniela, get_loterias, get_feriados, get_rios, and 2 more. Their descriptions and schemas cost roughly 271 tokens of context every time the server is loaded.

Does the SigmaDiario — Datos de Argentina MCP server require authentication?

No. We connected to SigmaDiario — Datos de Argentina without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SigmaDiario — Datos de Argentina MCP server still maintained?

SigmaDiario — Datos de Argentina is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the SigmaDiario — Datos de Argentina MCP server?

VerifyMCP ran 12 checks on SigmaDiario — Datos de Argentina, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SigmaDiario — Datos de Argentina: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.