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.

Farmacia Santa Croce

REMOTE · FARMACIASANTACROCE.TO.IT

Servizi, giornate speciali e prenotazioni della Farmacia Santa Croce.

+3 this week 71 Trust /100

Last scanned (15 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 24 Oct 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 Security57
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1133 tokens (~80/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
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.

  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 26 +1

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

  • 15 Oct 26 +1

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

  • 13 Oct 26 +1

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

  • 12 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 10 Oct 26 64

    First indexed and scored.

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 24 Oct 2026 · Probed https://farmaciasantacroce.to.it/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=farmaciasantacroce.to.it CN=YR2,O=Let's Encrypt,C=US 21 Sept 2026 20 Dec 2026 RSA 2048 SHA256-RSA 69b6d0b724c633db466377bef81b6940330
SANs: cloud.farmaciasantacroce.to.it, farmaciasantacroce.to.it, www.farmaciasantacroce.to.it
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 farmaciasantacroce.to.it. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
it. present 51765 13 Verified
to.it. absent Delegated
farmaciasantacroce.to.it. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://farmaciasantacroce.to.it/mcp Verified 200
http (plaintext) http://farmaciasantacroce.to.it/mcp HTTPS enforced 301 https://farmaciasantacroce.to.it/mcp
MCP tools · 14 exposed · ~994 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
book ~135

Prenota a nome del cliente che ha effettuato l'accesso, senza codice. Conferma servizio, data e ora con la persona prima di chiamarlo.

NameTypeReqDescription
datestring–Solo per i servizi: data AAAA-MM-GG (da domani)
kindstringyes"service" per un servizio, "special_event" per una giornata speciale
session_tokenstringyessession_token restituito da complete_login o complete_registration
slugstringyesSlug del servizio o della giornata speciale
timestringyesOrario HH:MM tra quelli restituiti dalle availability

No output schema declared.

No examples provided.

cancel_my_booking ~79

Annulla una prenotazione futura a una giornata speciale del cliente che ha effettuato l'accesso. Le prenotazioni dei servizi si modificano contattando la farmacia.

NameTypeReqDescription
booking_idintegeryesbooking_id da list_my_bookings
session_tokenstringyessession_token restituito da complete_login o complete_registration

No output schema declared.

No examples provided.

complete_login ~93

Completa l'accesso con il codice WhatsApp. Restituisce un session_token. Se più persone condividono il numero, indicare first_name.

NameTypeReqDescription
codestringyesCodice di 6 cifre ricevuto via WhatsApp
first_namestring–Solo se richiesto: nome della persona che accede
request_idstringyesrequest_id restituito dal passo precedente

No output schema declared.

No examples provided.

complete_registration ~66

Completa la registrazione con il codice WhatsApp. Restituisce un session_token per gli strumenti dell'account.

NameTypeReqDescription
codestringyesCodice di 6 cifre ricevuto via WhatsApp
request_idstringyesrequest_id restituito dal passo precedente

No output schema declared.

No examples provided.

confirm_booking ~62

Secondo passo di request_booking: conferma con il codice ricevuto dalla persona via WhatsApp.

NameTypeReqDescription
codestringyesCodice di 6 cifre ricevuto via WhatsApp
request_idstringyesrequest_id restituito dal passo precedente

No output schema declared.

No examples provided.

get_service_availability ~58

Orari liberi di un servizio in una data (da domani fino a 90 giorni).

NameTypeReqDescription
datestringyesData AAAA-MM-GG
servicestringyesSlug del servizio (da list_services)

No output schema declared.

No examples provided.

get_special_event_availability ~37

Orari ancora liberi di una giornata speciale.

NameTypeReqDescription
eventstringyesSlug della giornata (da list_special_events)

No output schema declared.

No examples provided.

list_my_bookings ~42

Prenotazioni future del cliente che ha effettuato l'accesso.

NameTypeReqDescription
session_tokenstringyessession_token restituito da complete_login o complete_registration

No output schema declared.

No examples provided.

list_services ~27

Elenco dei servizi della farmacia prenotabili online (slug, durata, prezzo, giorni).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_special_events ~30

Giornate speciali in programma (screening, consulenze…) con data e fascia oraria.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

logout ~39

Chiude la sessione aperta con complete_login / complete_registration.

NameTypeReqDescription
session_tokenstringyessession_token restituito da complete_login o complete_registration

No output schema declared.

No examples provided.

request_booking ~184

Prenotazione senza account o senza accesso: invia un codice WhatsApp al cellulare della persona. Il posto è riservato solo dopo confirm_booking. Se la persona ha già una sessione usa book.

NameTypeReqDescription
datestring–Solo per i servizi: data AAAA-MM-GG (da domani)
first_namestringyesNome della persona da prenotare
kindstringyes"service" per un servizio, "special_event" per una giornata speciale
last_namestringyesCognome della persona da prenotare
phonestringyesCellulare con WhatsApp, es. +39 333 1234567
slugstringyesSlug del servizio o della giornata speciale
timestringyesOrario HH:MM tra quelli restituiti dalle availability

No output schema declared.

No examples provided.

start_login ~50

Accesso per chi è già cliente: invia un codice WhatsApp al cellulare registrato.

NameTypeReqDescription
phonestringyesCellulare registrato, es. +39 333 1234567

No output schema declared.

No examples provided.

start_registration ~92

Registra la persona al sito della farmacia: invia un codice WhatsApp al suo cellulare. Se è già registrata con quel numero e quel nome, il passo successivo effettua l'accesso.

NameTypeReqDescription
first_namestringyesNome
last_namestringyesCognome
phonestringyesCellulare con WhatsApp, es. +39 333 1234567

No output schema declared.

No examples provided.

Install

How do I install the Farmacia Santa Croce MCP server?

Farmacia Santa Croce is a hosted endpoint at https://farmaciasantacroce.to.it/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 · farmaciasantacroce.to.it

# add to Claude Code
claude mcp add --transport http it-to-farmaciasantacroce-prenotazioni 'https://farmaciasantacroce.to.it/mcp'
Common questions

What is the Farmacia Santa Croce MCP server?

Farmacia Santa Croce is an MCP server listed in the public MCP registry as it.to.farmaciasantacroce/prenotazioni. Servizi, giornate speciali e prenotazioni della Farmacia Santa Croce. This page covers its hosted endpoint (https://farmaciasantacroce.to.it/mcp).

Is the Farmacia Santa Croce MCP server safe to use?

Farmacia Santa Croce scores 71 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 Farmacia Santa Croce MCP server expose?

Farmacia Santa Croce exposes 14 tools: list_services, get_service_availability, list_special_events, get_special_event_availability, request_booking, and 9 more. Their descriptions and schemas cost roughly 994 tokens of context every time the server is loaded.

Does the Farmacia Santa Croce MCP server require authentication?

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

Is the Farmacia Santa Croce MCP server still maintained?

Farmacia Santa Croce is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.