SizeRef Size Charts
REMOTE · MCP.SIZEREF.ONLINE
Audit, normalise and export size charts as clean tables and JSON-LD. No AI; keeps no charts sent.
Available components
Last scanned (20 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 641 tokens (~160/item across 4 items; 3 tools + 1 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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 →
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.
- 21 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.
- 19 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.
- 17 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.
- 16 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 64
First indexed and scored.
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://mcp.sizeref.online/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sizeref.online | CN=WE1,O=Google Trust Services,C=US | 15 Nov 2026 | 13 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | dc93aebb9bf5c73d13faddc13d42cda2 |
| SANs: sizeref.online, mcp.sizeref.online, *.mcp.sizeref.online | ||||||
| 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 mcp.sizeref.online. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| online. | DS published | 30961 | 13 | Verified |
| sizeref.online. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sizeref.online/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.sizeref.online/mcp | Inconclusive | 405 |
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 →
audit_size_chart Audit a size chart ~240
Checks a size chart and reports what is wrong with it or still unanswered, without changing it. Takes a size chart, never a person's measurements. Limits: one call per request; up to 60 sizes, 40 columns or measurements a size, and 64 characters a size label or measurement name; each table cell is read up to 200 characters. Send a chart in SizeRef chart format v1, or a table as html, csv, or headers and rows. variant_sizes compares the chart's size labels with the product's; product_title decides whether hips are kept for long tops such as a kurta or a dress; product_text gives the fit when the table does not state it. results[] holds one result per table found; the top-level verdict is the worst table's, so read results[] for each table. It cannot see the product page, so a pasted table is at best needs_fix until normalise_size_chart gets the answers.
| Name | Type | Req | Description |
|---|---|---|---|
| chart | object | – | – |
| product_text | string | – | – |
| product_title | string | – | – |
| table | object | – | – |
| variant_sizes | array | – | – |
No output schema declared.
No examples provided.
export_agent_ready_chart Export a size chart ~178
Writes a valid SizeRef chart v1 as SizeRef JSON, schema.org JSON-LD, CSV and plain text, and lists anything left out and why. Takes a size chart, never a person's measurements. Limits: one call per request; up to 60 sizes, 40 columns or measurements a size, and 64 characters a size label or measurement name; each table cell is read up to 200 characters. jsonld is a whole <script type="application/ld+json"> block, ready to paste into the product page, with its JSON escaped so no value can end the block. jsonld_note says how the theme can link each variant size to the matching @id; that step is optional.
| Name | Type | Req | Description |
|---|---|---|---|
| chart_v1 | object | yes | – |
| formats | array | – | – |
| product | object | – | – |
No output schema declared.
No examples provided.
normalise_size_chart Normalise a size chart ~202
Turns a size table, or a chart with gaps, into SizeRef chart format v1 from what the table states plus the answers you pass. Nothing is inferred from the numbers. Takes a size chart, never a person's measurements. Limits: one call per request; up to 60 sizes, 40 columns or measurements a size, and 64 characters a size label or measurement name; each table cell is read up to 200 characters. When something is left open it returns questions with the allowed answers instead of a chart. A page with several tables needs table_index. product_title decides whether hips are kept for long tops such as a kurta or a dress; product_text gives the fit when the table does not state it.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | – |
| chart | object | – | – |
| product_text | string | – | – |
| product_title | string | – | – |
| table | object | – | – |
| table_index | integer | – | – |
No output schema declared.
No examples provided.
How do I install the SizeRef Size Charts MCP server?
SizeRef Size Charts is a hosted endpoint at https://mcp.sizeref.online/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 · mcp.sizeref.online
claude mcp add --transport http online-sizeref-size-charts 'https://mcp.sizeref.online/mcp'
What is the SizeRef Size Charts MCP server?
SizeRef Size Charts is an MCP server listed in the public MCP registry as online.sizeref/size-charts. Audit, normalise and export size charts as clean tables and JSON-LD. No AI; keeps no charts sent. This page covers its hosted endpoint (https://mcp.sizeref.online/mcp).
Is the SizeRef Size Charts MCP server safe to use?
SizeRef Size Charts scores 67 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 SizeRef Size Charts MCP server expose?
SizeRef Size Charts exposes 3 tools: audit_size_chart, normalise_size_chart, export_agent_ready_chart. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.
Does the SizeRef Size Charts MCP server require authentication?
No. We connected to SizeRef Size Charts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SizeRef Size Charts MCP server still maintained?
SizeRef Size Charts 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 SizeRef Size Charts MCP server?
VerifyMCP ran 12 checks on SizeRef Size Charts, 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 SizeRef Size Charts: 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.