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.

DAIly outfits

REMOTE · DAILYOUTFITS.APP

What to wear today by city weather and travel packing lists by destination. Public, read-only.

Available components

72 Trust /100

Last scanned (11 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

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 Security74
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 282 tokens (~94/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 31 Oct 26 0
    • Tool “get_product_info” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 69

    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 5 Nov 2026 · Probed https://dailyoutfits.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dailyoutfits.app CN=YR1,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 RSA 4096 SHA256-RSA 59f8dcdf52b9c029d9b2481f01c617c083f
SANs: dailyoutfits.app
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 dailyoutfits.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
dailyoutfits.app. 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://dailyoutfits.app/mcp Verified 200
http (plaintext) http://dailyoutfits.app/mcp HTTPS enforced 302 https://dailyoutfits.app/mcp
MCP tools · 3 exposed · ~238 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_product_info ~59

What DAIly outfits is (AI outfit planner / digital closet app), who it's for, price (free, with optional Premium), platforms and download link.

NameTypeReqDescription
langstring–Idioma de la respuesta / response language (default es)

No output schema declared.

No examples provided.

travel_packing_list ~98

Capsule packing list for a trip (destination + number of days) based on the destination's forecast. Generic; the app builds it from the user's own closet with one outfit per day and plan.

NameTypeReqDescription
daysintegeryesTrip length in days
destinationstringyesDestination city, e.g. Cusco, Cancún, Madrid
langstring–Idioma de la respuesta / response language (default es)

No output schema declared.

No examples provided.

what_to_wear_today ~81

Clothing layers to wear today in a city, from today's weather forecast (Open-Meteo). Generic advice; the app personalizes it with the user's own closet.

NameTypeReqDescription
citystringyesCity, e.g. Lima, Cusco, Mexico City
langstring–Idioma de la respuesta / response language (default es)

No output schema declared.

No examples provided.

Install

How do I install the DAIly outfits MCP server?

DAIly outfits is a hosted endpoint at https://dailyoutfits.app/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 · dailyoutfits.app

# add to Claude Code
claude mcp add --transport http jonatanvazquez-daily-outfits 'https://dailyoutfits.app/mcp'
Common questions

What is the DAIly outfits MCP server?

DAIly outfits is an MCP server listed in the public MCP registry as io.github.jonatanvazquez/daily-outfits. What to wear today by city weather and travel packing lists by destination. Public, read-only. This page covers its hosted endpoint (https://dailyoutfits.app/mcp).

Is the DAIly outfits MCP server safe to use?

DAIly outfits scores 72 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 DAIly outfits MCP server expose?

DAIly outfits exposes 3 tools: get_product_info, what_to_wear_today, travel_packing_list. Their descriptions and schemas cost roughly 238 tokens of context every time the server is loaded.

Does the DAIly outfits MCP server require authentication?

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

Is the DAIly outfits MCP server still maintained?

DAIly outfits is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.