# CaliberAPI Pistol Optic Fit (remote · mcp.caliberapi.com)

Source-cited pistol red dot compatibility: direct fits, adapter plates and optic footprints.

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

## Components

- remote · `mcp.caliberapi.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-caliberapi-pistol-optics/mcp.md), [page](https://verifymcp.io/servers/com-caliberapi-pistol-optics/mcp)

## Channel facts

- Endpoint: `https://mcp.caliberapi.com/mcp`
- 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. 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.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 717 tokens (~143/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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).

## Install

### How do I install the CaliberAPI Pistol Optic Fit MCP server?

CaliberAPI Pistol Optic Fit is a hosted endpoint at https://mcp.caliberapi.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.

### Claude

```bash
claude mcp add --transport http com-caliberapi-pistol-optics 'https://mcp.caliberapi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-caliberapi-pistol-optics": {
      "url": "https://mcp.caliberapi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-caliberapi-pistol-optics": {
      "type": "http",
      "url": "https://mcp.caliberapi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-caliberapi-pistol-optics]
url = "https://mcp.caliberapi.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-caliberapi-pistol-optics --url 'https://mcp.caliberapi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-caliberapi-pistol-optics:
    url: "https://mcp.caliberapi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-caliberapi-pistol-optics": {
      "Transport": "http",
      "Url": "https://mcp.caliberapi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-caliberapi-pistol-optics -t streamable-http -u 'https://mcp.caliberapi.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-caliberapi-pistol-optics": {
      "type": "http",
      "url": "https://mcp.caliberapi.com/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 72, +1)

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

### 2026-11-03 (score 71, +1)

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

### 2026-10-31 (score 70, +1)

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

### 2026-10-29 (score 69, +1)

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

### 2026-10-27 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 67)

First indexed and scored.

## MCP tools (5)

### `check_fit` (~227 tokens)

Check pistol and optic fit

Answer whether a specific red dot optic fits a specific pistol, from source-cited data. Returns fit "direct" (mounts on the slide cut, with the footprint), "adapter" (only through the adapter plate chain in via, with plate maker, model, mount and presented footprints, and plate sources), or "unknown" (no cited fit in the dataset, which is not evidence it does not fit). Returns "needs_clarification" with candidates when a name is ambiguous; call again with a candidate slug. Report the answer exactly as returned: never call an adapter fit a direct fit, and never turn "unknown" into "does not fit". Cite with the returned citation line and link html_url.

Input parameters:

- `optic` (string, required): Optic slug (e.g. "trijicon/rmr-type-2") or name (e.g. "Trijicon RMR Type 2").
- `pistol` (string, required): Pistol slug (e.g. "taurus/g3-toro") or name (e.g. "Taurus G3 TORO").

### `list_optics_for_pistol` (~166 tokens)

List optics for a pistol

List every optic with a cited fit on one pistol, each marked direct (with footprint) or adapter (with the plate chain in via). Use it for questions like "what red dots fit my pistol". Optics not listed have no cited fit, which is not evidence they do not fit. Report the answer exactly as returned: never call an adapter fit a direct fit, and never turn "unknown" into "does not fit". Cite with the returned citation line and link html_url.

Input parameters:

- `fit` (string): Only direct fits, only adapter-plate fits, or both (default).
- `pistol` (string, required): Pistol slug (e.g. "taurus/g3-toro") or name (e.g. "Taurus G3 TORO").

### `list_pistols_for_optic` (~133 tokens)

List pistols for an optic

List every pistol with a cited fit for one optic, each marked direct (with footprint) or adapter (with the plate chain in via). Use it for questions like "what pistols take this red dot". Report the answer exactly as returned: never call an adapter fit a direct fit, and never turn "unknown" into "does not fit". Cite with the returned citation line and link html_url.

Input parameters:

- `optic` (string, required): Optic slug (e.g. "trijicon/rmr-type-2") or name (e.g. "Trijicon RMR Type 2").

### `get_footprint` (~103 tokens)

Get an optic footprint

Describe one optic mounting footprint or plate system (for example RMR, RMSc, ACRO, DPP, Glock MOS): screw and recoil lug counts, the optics that use it, the pistols cut for it directly, and the adapter plates that mount or present it, with sources.

Input parameters:

- `name_or_slug` (string, required): Footprint slug (e.g. "rmsc") or name (e.g. "RMSc", "Glock MOS").

### `search` (~88 tokens)

Search the dataset

Find pistols, optics and footprints by name. Returns slugs, names and page URLs to pass to the other tools. Use it when you are unsure of an exact model name.

Input parameters:

- `query` (string, required): Words to match, e.g. "glock 19", "holosun 507", "rmr".
- `type` (string): Limit results to one kind of record.

## Diagnostics

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

## Score history

- 2026-11-05: 72
- 2026-11-04: 71
- 2026-11-03: 71
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 67

## Common questions

### What is the CaliberAPI Pistol Optic Fit MCP server?

CaliberAPI Pistol Optic Fit is an MCP server listed in the public MCP registry as com.caliberapi/pistol-optics. Source-cited pistol red dot compatibility: direct fits, adapter plates and optic footprints. This page covers its hosted endpoint (https://mcp.caliberapi.com/mcp).

### Is the CaliberAPI Pistol Optic Fit MCP server safe to use?

CaliberAPI Pistol Optic Fit scores 72 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 CaliberAPI Pistol Optic Fit MCP server expose?

CaliberAPI Pistol Optic Fit exposes 5 tools: check_fit, list_optics_for_pistol, list_pistols_for_optic, get_footprint, search. Their descriptions and schemas cost roughly 717 tokens of context every time the server is loaded.

### Does the CaliberAPI Pistol Optic Fit MCP server require authentication?

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

### Is the CaliberAPI Pistol Optic Fit MCP server still maintained?

CaliberAPI Pistol Optic Fit 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 CaliberAPI Pistol Optic Fit MCP server?

VerifyMCP ran 12 checks on CaliberAPI Pistol Optic Fit, 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 CaliberAPI Pistol Optic Fit: 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.

## Links

- Remote endpoint: https://mcp.caliberapi.com/mcp
- Website: https://caliberapi.com/data/
- Changelog RSS feed: https://verifymcp.io/servers/com-caliberapi-pistol-optics/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-caliberapi-pistol-optics/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-caliberapi-pistol-optics/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-caliberapi-pistol-optics/mcp