# Joinerycalc (remote · joinerycalc.com)

Exact joinery layouts for agents. Dovetails: tail and pin widths, positions, angles, router template

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `joinerycalc.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-joinerycalc-dovetail/joinerycalc.md), [page](https://verifymcp.io/servers/com-joinerycalc-dovetail/joinerycalc)

## Channel facts

- Endpoint: `https://joinerycalc.com/mcp?via=registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 65/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 688 tokens (~344/item across 2 items; 1 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Joinerycalc MCP server?

Joinerycalc is a hosted endpoint at https://joinerycalc.com/mcp?via=registry, 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 com-joinerycalc-dovetail 'https://joinerycalc.com/mcp?via=registry'
```

### Cursor

```json
{
  "mcpServers": {
    "com-joinerycalc-dovetail": {
      "url": "https://joinerycalc.com/mcp?via=registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-joinerycalc-dovetail": {
      "type": "http",
      "url": "https://joinerycalc.com/mcp?via=registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-joinerycalc-dovetail]
url = "https://joinerycalc.com/mcp?via=registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-joinerycalc-dovetail": {
      "type": "remote",
      "url": "https://joinerycalc.com/mcp?via=registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-joinerycalc-dovetail --url 'https://joinerycalc.com/mcp?via=registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-joinerycalc-dovetail:
    url: "https://joinerycalc.com/mcp?via=registry"
```

### Netclaw

```json
{
  "McpServers": {
    "com-joinerycalc-dovetail": {
      "Transport": "http",
      "Url": "https://joinerycalc.com/mcp?via=registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-joinerycalc-dovetail -t streamable-http -u 'https://joinerycalc.com/mcp?via=registry'
```

### Other

```json
{
  "mcpServers": {
    "com-joinerycalc-dovetail": {
      "type": "http",
      "url": "https://joinerycalc.com/mcp?via=registry"
    }
  }
}
```

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-04 (score 68, +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.

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

### 2026-10-31 (score 66, +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-10-30 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 65)

First indexed and scored.

## MCP tools (1)

### `dovetail_layout` (~674 tokens)

Dovetail layout

Exact layout of a through dovetail joint, for hand-cut joints and router templates. Hand mode: give the board width, the thicknesses of both boards, the number of tails, the pin width at its narrow end and the angle (degrees per side, 1:N slope ratio, included angle or degrees from horizontal), in mm or inches; the tail width is computed. Router mode: give the tail width instead; the pins are spaced evenly and the router template is sized. Returns every tail and pin position and width on both faces (they sum exactly to the board width), tail and pin lengths, the angle in all four conventions, and warnings. Given measured socket dimensions, also recommends tail widths that fit them. Deterministic: use this instead of computing dovetail geometry yourself.

Input parameters:

- `angle` (number, required): Dovetail angle, read according to angleFormat. It must give a per-side angle from 1° to under 45°.
- `angleFormat` (string): How to read angle: degrees per side from vertical (router bits: 7, 8, 14), slope ratio N for 1:N (6 for 1:6), included angle in degrees, or degrees from horizontal.
- `boardWidth` (number, required): Width of both boards across the joint. Between 0.5 and 5000 mm (0.02 to 196.85 in).
- `guideBushingDiameter` (number): Router mode: guide bushing diameter, larger than the bit. Default: the bit diameter plus 7 mm. Between 0.5 and 5000 mm (0.02 to 196.85 in).
- `measuredSockets` (object): Socket dimensions as actually cut, measured on both sides. When given, the response recommends tail widths that fit them.
- `mode` (string): hand: give pinWidth, the tail width is computed. router: give tailWidth, the pins are spaced evenly.
- `numberOfTails` (integer, required): Number of tails.
- `pinBoardThickness` (number, required): Thickness of the board the pins are cut on. Between 0.5 and 5000 mm (0.02 to 196.85 in).
- `pinWidth` (number): Required in hand mode: pin width at its narrow end (the outside face of the pin board). Edge pins get the same narrow width. Between 0.5 and 5000 mm (0.02 to 196.85 in).
- `routerBitDiameter` (number): Router mode: dovetail bit diameter, at most the tail width. Default: 8 mm, or the smallest bit that cuts the depth of the tails if larger. Between 0.5 and 5000 mm (0.02 to 196.85 in).
- `tailBoardThickness` (number, required): Thickness of the board the tails are cut on. Between 0.5 and 5000 mm (0.02 to 196.85 in).
- `tailWidth` (number): Required in router mode: tail width at its wide end. Between 0.5 and 5000 mm (0.02 to 196.85 in).
- `unit` (string): Unit of every length in the request and in the response.

## Diagnostics

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

## Score history

- 2026-11-05: 68
- 2026-11-04: 68
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 66
- 2026-10-31: 66
- 2026-10-30: 65
- 2026-10-29: 65

## Common questions

### What is the Joinerycalc MCP server?

Joinerycalc is an MCP server listed in the public MCP registry as com.joinerycalc/dovetail. Exact joinery layouts for agents. Dovetails: tail and pin widths, positions, angles, router template. This page covers its hosted endpoint (https://joinerycalc.com/mcp?via=registry).

### Is the Joinerycalc MCP server safe to use?

Joinerycalc scores 68 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 Joinerycalc MCP server expose?

Joinerycalc exposes 1 tool: dovetail_layout. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.

### Does the Joinerycalc MCP server require authentication?

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

### Is the Joinerycalc MCP server still maintained?

Joinerycalc 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://joinerycalc.com/mcp?via=registry
- Website: https://joinerycalc.com/dovetail
- Changelog RSS feed: https://verifymcp.io/servers/com-joinerycalc-dovetail/joinerycalc.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-joinerycalc-dovetail/joinerycalc.json
- HTML version of this page: https://verifymcp.io/servers/com-joinerycalc-dovetail/joinerycalc