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.

Measured Size

REMOTE · API.MEASUREDSIZE.COM

Bra sizes from measurements, in each brand's own labels, with the confidence behind each.

+3 this week 77 Trust /100

Last scanned (12 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

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
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 914 tokens (~228/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 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 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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • 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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 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.

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “bra_size_at_brand” rewrote its description, which is the text the model reads security
  • 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.

  • 21 Oct 26 +1
    • “bra_size_at_brand” reworded the description of “unit” cosmetic
    • “bra_size_from_measurements” reworded the description of “unit” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 19 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “translate_bra_size” rewrote its description, which is the text the model reads security
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://api.measuredsize.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=measuredsize.com CN=WE1,O=Google Trust Services,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA256 6b7ff16184af8d740edee8564f3ecc30
SANs: measuredsize.com, api.measuredsize.com, *.api.measuredsize.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 api.measuredsize.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
measuredsize.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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.measuredsize.com/mcp Verified 200
http (plaintext) http://api.measuredsize.com/mcp Inconclusive 405
MCP tools · 4 exposed · ~689 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
bra_size_at_brand ~241

Her size at one brand, in that brand's own labels (for example 32E at a UK-lettered brand where her US size is 32DDD), for its band and cup bras and for its letter-sized styles, each with a confidence badge and a reason. Use this when a shopper names a brand. If the brand doesn't carry her size, the answer says so and why (for example its bands start at 34, or its cups stop at DD) and names the closest size it makes (closest_made); pass that on rather than guessing. Use list_bra_brands if the brand isn't found.

NameTypeReqDescription
brandstringyesA brand name as shoppers write it (aliases accepted, any case), or an id from the brand list.
bustnumberyesAround the fullest part of the bust, the tape flat and not pressing in. Decimals allowed.
underbustnumberyesSnug around the ribcage, just under the bust, after breathing out. Decimals allowed.
unitstring–The unit both measurements are in: inches (in) or centimeters (cm).

No output schema declared.

No examples provided.

bra_size_from_measurements ~190

Her bra size from her underbust and bust measurements (inches or cm, decimals allowed): her base US size, sister sizes one band each way, the UK size, EU and French sizes where their tables give the whole size, and the usual letter size (S/M/L). Use this when a shopper gives her measurements and wants her size in general. The answer includes a confidence badge and a reason: pass both on with the size. If the measurements are refused, tell her the reason given.

NameTypeReqDescription
bustnumberyesAround the fullest part of the bust, the tape flat and not pressing in. Decimals allowed.
underbustnumberyesSnug around the ribcage, just under the bust, after breathing out. Decimals allowed.
unitstring–The unit both measurements are in: inches (in) or centimeters (cm).

No output schema declared.

No examples provided.

list_bra_brands ~101

The brands Measured Size has researched, with their other names, whether they sell band and cup sizes or letter sizes, their cup letters, band and cup ranges, whether their own letter chart is on file, and when their record was last researched. Use it to find a brand's name before the other tools, or to say which brands are covered.

NameTypeReqDescription
qstring–Optional: only brands whose name or an alias contains this text.

No output schema declared.

No examples provided.

translate_bra_size ~157

Translate a band and cup size she wears at one brand (for example 34DD at Wacoal) into another brand's label, through Measured Size's base size. Use this only when the shopper has no measurements; measurements give a better answer. Translated sizes are rated no higher than Good Match: tell her so. It refuses letter sizes (S/M/L), labels the first brand's record doesn't give, and brands that sell letter sizes only, with the reason.

NameTypeReqDescription
from_brandstringyesThe brand whose size she knows.
sizestringyesHer band and cup size at from_brand, as that brand labels it.
to_brandstringyesThe brand to translate the size into.

No output schema declared.

No examples provided.

Install

How do I install the Measured Size MCP server?

Measured Size is a hosted endpoint at https://api.measuredsize.com/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 · api.measuredsize.com

# add to Claude Code
claude mcp add --transport http com-measuredsize-fit 'https://api.measuredsize.com/mcp'
Common questions

What is the Measured Size MCP server?

Measured Size is an MCP server listed in the public MCP registry as com.measuredsize/fit. Bra sizes from measurements, in each brand's own labels, with the confidence behind each. This page covers its hosted endpoint (https://api.measuredsize.com/mcp).

Is the Measured Size MCP server safe to use?

Measured Size scores 77 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 Measured Size MCP server expose?

Measured Size exposes 4 tools: bra_size_from_measurements, bra_size_at_brand, translate_bra_size, list_bra_brands. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.

Does the Measured Size MCP server require authentication?

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

Is the Measured Size MCP server still maintained?

Measured Size 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.

What did VerifyMCP test on the Measured Size MCP server?

VerifyMCP ran 12 checks on Measured Size, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Measured Size: HTTPS. 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.