# FitCard (remote · fitcard.ai)

Which size to buy in a men's shirt, from shirts he already owns that fit. Real garment measurements.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `fitcard.ai`: 65/100 (this document), [markdown](https://verifymcp.io/servers/ai-fitcard-fitcard/fitcard.md), [page](https://verifymcp.io/servers/ai-fitcard-fitcard/fitcard)

## Channel facts

- Endpoint: `https://fitcard.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-fitcard-fitcard 'https://fitcard.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-fitcard-fitcard": {
      "url": "https://fitcard.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-fitcard-fitcard": {
      "type": "http",
      "url": "https://fitcard.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-fitcard-fitcard]
url = "https://fitcard.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-fitcard-fitcard": {
      "type": "remote",
      "url": "https://fitcard.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-fitcard-fitcard --url 'https://fitcard.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-fitcard-fitcard:
    url: "https://fitcard.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-fitcard-fitcard": {
      "Transport": "http",
      "Url": "https://fitcard.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-fitcard-fitcard -t streamable-http -u 'https://fitcard.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-fitcard-fitcard": {
      "type": "http",
      "url": "https://fitcard.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 65, 0)

- [functional] Server version: 1.0.1 → 1.1.0

### 2026-11-04 (score 65, +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.

### 2026-11-03 (score 64, 0)

- [security] 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
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-11-02 (score 64)

First indexed and scored.

## MCP tools (3)

### `size_me` (~215 tokens)

Which size should I buy?

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.

Input parameters:

- `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, required): Shirts he owns, ideally 3-5 that fit him well. Brand, item and size only.
- `shirt` (object, required): 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.

### `what_to_buy` (~238 tokens)

What should I buy?

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.

Input parameters:

- `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, required): 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.

### `shirt_measurements` (~76 tokens)

Shirt measurements

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.

Input parameters:

- `brand` (string, required)
- `item` (string, required)
- `size` (string): Optional: just this size.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-fitcard-fitcard/fitcard#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64

## Common questions

### 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.

## Links

- Remote endpoint: https://fitcard.ai/mcp
- Website: https://fitcard.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-fitcard-fitcard/fitcard.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-fitcard-fitcard/fitcard.json
- HTML version of this page: https://verifymcp.io/servers/ai-fitcard-fitcard/fitcard