CaliberAPI Pistol Optic Fit
REMOTE · MCP.CALIBERAPI.COM
Source-cited pistol red dot compatibility: direct fits, adapter plates and optic footprints.
Available components
Last scanned (4 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
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 Usability78
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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 +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.
- 3 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 67
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://mcp.caliberapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caliberapi.com | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2079c89355b67df138f9c98a9adced8 |
| SANs: caliberapi.com, mcp.caliberapi.com, *.mcp.caliberapi.com | ||||||
| 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.caliberapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| caliberapi.com. | 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://mcp.caliberapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.caliberapi.com/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 →
check_fit Check pistol and optic fit ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| optic | string | yes | Optic slug (e.g. "trijicon/rmr-type-2") or name (e.g. "Trijicon RMR Type 2"). |
| pistol | string | yes | Pistol slug (e.g. "taurus/g3-toro") or name (e.g. "Taurus G3 TORO"). |
No output schema declared.
No examples provided.
get_footprint Get an optic footprint ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name_or_slug | string | yes | Footprint slug (e.g. "rmsc") or name (e.g. "RMSc", "Glock MOS"). |
No output schema declared.
No examples provided.
list_optics_for_pistol List optics for a pistol ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fit | string | – | Only direct fits, only adapter-plate fits, or both (default). |
| pistol | string | yes | Pistol slug (e.g. "taurus/g3-toro") or name (e.g. "Taurus G3 TORO"). |
No output schema declared.
No examples provided.
list_pistols_for_optic List pistols for an optic ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| optic | string | yes | Optic slug (e.g. "trijicon/rmr-type-2") or name (e.g. "Trijicon RMR Type 2"). |
No output schema declared.
No examples provided.
search Search the dataset ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Words to match, e.g. "glock 19", "holosun 507", "rmr". |
| type | string | – | Limit results to one kind of record. |
No output schema declared.
No examples provided.
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.
remote · mcp.caliberapi.com
claude mcp add --transport http com-caliberapi-pistol-optics 'https://mcp.caliberapi.com/mcp'
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.