FitCard
REMOTE · FITCARD.AI
Which size to buy in a men's shirt, from shirts he already owns that fit. Real garment measurements.
Available components
Last scanned (5 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 707 tokens (~235/item across 3 items; 3 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 0
- Server version: 1.0.1 → 1.1.0 functional
- 4 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.
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “size_me” rewrote its description, which is the text the model reads security
- Tool “what_to_buy” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- 2 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 5 Nov 2026 · Probed https://fitcard.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fitcard.ai | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f55a94300fd0b75b0e5b696d2f24c5f8 |
| SANs: fitcard.ai, *.fitcard.ai | ||||||
| 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 fitcard.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| fitcard.ai. | 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://fitcard.ai/mcp | Verified | 200 | |
| http (plaintext) | http://fitcard.ai/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 →
shirt_measurements Shirt measurements ~76
The real garment measurements of a shirt (chest all the way around and length, in inches) in each size, from the brand's own chart or other checked sources. Not a body-size chart.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | – |
| item | string | yes | – |
| size | string | – | Optional: just this size. |
No output schema declared.
No examples provided.
size_me Which size should I buy? ~215
Recommends a size in one shirt for this man, from the shirts he already owns that fit. Returns the size, why (in terms of his own shirts), how it will fit, and a confidence. The size already accounts for his shirts, the fabric (including dryer shrinkage) and the cut.
| Name | Type | Req | Description |
|---|---|---|---|
| dress_shirt_size | string | – | His dress shirt size off the label, if he knows it, e.g. "17 34/35" (neck, sleeve). Helps with long sleeves. |
| fit_preference | string | – | How he likes shirts to fit, if he said. Default standard. |
| my_shirts | array | yes | Shirts he owns, ideally 3-5 that fit him well. Brand, item and size only. |
| shirt | object | yes | The shirt he is thinking of buying. |
| suit_size | string | – | His suit jacket size off the label, if he knows it, e.g. "44L" or "42 Regular". Helps with Tall sizes. |
No output schema declared.
No examples provided.
what_to_buy What should I buy? ~238
Builds his FitCard from the shirts he owns and returns the shirts that will fit him, each in the right size, with a buy link. Also returns a link to his full card on fitcard.ai. Each size already accounts for his shirts and the fabric; a "snugger" or "roomier" note describes how that size fits.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional: only this kind of shirt. |
| dress_shirt_size | string | – | His dress shirt size off the label, if he knows it, e.g. "17 34/35" (neck, sleeve). Helps with long sleeves. |
| fit_preference | string | – | How he likes shirts to fit, if he said. Default standard. |
| limit | integer | – | How many picks (default 8). |
| my_shirts | array | yes | Shirts he owns, ideally 3-5 that fit him well. Brand, item and size only. |
| suit_size | string | – | His suit jacket size off the label, if he knows it, e.g. "44L" or "42 Regular". Helps with Tall sizes. |
No output schema declared.
No examples provided.
How do I install the FitCard MCP server?
FitCard is a hosted endpoint at https://fitcard.ai/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 · fitcard.ai
claude mcp add --transport http ai-fitcard-fitcard 'https://fitcard.ai/mcp'
What is the FitCard MCP server?
FitCard is an MCP server listed in the public MCP registry as ai.fitcard/fitcard. Which size to buy in a men's shirt, from shirts he already owns that fit. Real garment measurements. This page covers its hosted endpoint (https://fitcard.ai/mcp).
Is the FitCard MCP server safe to use?
FitCard scores 65 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 FitCard MCP server expose?
FitCard exposes 3 tools: size_me, what_to_buy, shirt_measurements. Their descriptions and schemas cost roughly 529 tokens of context every time the server is loaded.
Does the FitCard MCP server require authentication?
No. We connected to FitCard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FitCard MCP server still maintained?
FitCard 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.