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.

PrecioSano

REMOTE · PRECIOSANO.CL

Medicine prices across Chilean pharmacies, same-ingredient brands (ISP) and on-duty pharmacies.

Available components

+2 this week 89 Trust /100

Last scanned (12 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Health and Science

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 393 tokens (~98/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

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

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.

  • 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
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

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 6 Nov 2026 · Probed https://preciosano.cl/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=preciosano.cl CN=YR2,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 RSA 2048 SHA256-RSA 65113813dd0ed6b0bb5c140af75750b8d93
SANs: preciosano.cl
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of preciosano.cl. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cl. DS published 21199 8 Verified
preciosano.cl. 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=63072000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://nominatim.openstreetmap.org https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com https://fcm.googleapis.com; frame-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://preciosano.cl/mcp Verified 200
http (plaintext) http://preciosano.cl/mcp HTTPS enforced 308 https://preciosano.cl/mcp
MCP tools · 4 exposed · ~320 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
buscar_precio ~102

Precio de un medicamento en las farmacias de Chile, de más barato a más caro, con stock, y otras marcas con el mismo principio activo (registro del ISP). Acepta nombre comercial, principio activo o nombre con dosis. Los precios se reponen cada 6 horas: no los memorices.

NameTypeReqDescription
remediostringyesNombre del remedio, ej. «losartan 50mg», «lipitor» o «paracetamol».

No output schema declared.

No examples provided.

farmacias_de_turno ~60

Farmacias de turno hoy y abiertas ahora en una comuna de Chile (directorio MINSAL), con dirección, teléfono y mapa.

NameTypeReqDescription
comunastringyesComuna, ej. «Providencia» o «Viña del Mar».

No output schema declared.

No examples provided.

ficha_medicamento ~63

Precio en cada farmacia, precio por unidad, principio activo, otras marcas y variación del precio en los últimos 30 días.

NameTypeReqDescription
remediostringyesNombre del medicamento, ej. «paracetamol» o «atorvastatina 20mg».

No output schema declared.

No examples provided.

marcas_mismo_principio ~95

Todas las marcas que llevan un principio activo, de la más barata a la más cara, según el registro sanitario del ISP. Es donde está el ahorro grande: cambiar de marca rinde más que cambiar de farmacia. No reemplaza la indicación de un médico o químico farmacéutico.

NameTypeReqDescription
principio_activostringyesPrincipio activo, ej. «atorvastatina» o «losartan».

No output schema declared.

No examples provided.

Install

How do I install the PrecioSano MCP server?

PrecioSano is a hosted endpoint at https://preciosano.cl/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 · preciosano.cl

# add to Claude Code
claude mcp add --transport http martinnovoa22-preciosano 'https://preciosano.cl/mcp'
Common questions

What is the PrecioSano MCP server?

PrecioSano is an MCP server listed in the public MCP registry as io.github.martinnovoa22/preciosano. Medicine prices across Chilean pharmacies, same-ingredient brands (ISP) and on-duty pharmacies. This page covers its hosted endpoint (https://preciosano.cl/mcp).

Is the PrecioSano MCP server safe to use?

PrecioSano scores 89 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 PrecioSano MCP server expose?

PrecioSano exposes 4 tools: buscar_precio, ficha_medicamento, marcas_mismo_principio, farmacias_de_turno. Their descriptions and schemas cost roughly 320 tokens of context every time the server is loaded.

Does the PrecioSano MCP server require authentication?

No. We connected to PrecioSano without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PrecioSano MCP server still maintained?

PrecioSano is still listed as active in the MCP registry. We last reached this channel on 6 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 PrecioSano MCP server?

VerifyMCP ran 13 checks on PrecioSano, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.