Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Trail Fortress Fitment

REMOTE · TRAILFORTRESS.COM

Free, read-only truck and Jeep parts fitment: what fits your vehicle, fit checks, tire sizes.

0 this week 85 Trust /100

Last scanned (22 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security80
  • 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. 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 386 tokens (~64/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 22% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

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

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://trailfortress.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=trailfortress.com CN=YE1,O=Let's Encrypt,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA384 51854cdc4721f4b9174beafdaa5b64bfd88
SANs: trailfortress.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 4 Jun 2015 4 Jun 2035 RSA 4096 SHA256-RSA 8210cfb0d240e3594463e0bb63828b00

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of trailfortress.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
trailfortress.com. No DS 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://trailfortress.com/mcp/ Verified 200
http (plaintext) http://trailfortress.com/mcp/ HTTPS enforced 301 https://trailfortress.com/mcp/
MCP tools · 6 exposed · ~386 tokens

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 →

Tool Tokens
check_part_fit ~62

Returns fits, does_not_fit, or unknown using manufacturer application data. Never guesses when data is missing.

NameTypeReqDescription
makestringyes–
modelstringyes–
product_url_or_skustringyes–
yearintegeryes–

No output schema declared.

No examples provided.

find_parts_for_vehicle ~80

Returns a fitment-checked listing URL and in-stock parts with listable prices only. Manufacturer exclusions are on each product page.

NameTypeReqDescription
categorystring–Optional category slug, for example lift-kits.
limitinteger––
makestringyes–
modelstringyes–
yearintegeryes–

No output schema declared.

No examples provided.

get_product ~51

Returns title, brand, part number, listable price (MAP for Rough Country), availability, key facts, and manufacturer exclusions. No cost or trade pricing.

NameTypeReqDescription
product_url_or_skustringyes–

No output schema declared.

No examples provided.

list_vehicle_options ~79

Returns valid years, makes, and models in the Trail Fortress catalogue. Use this before guessing model spelling (Wrangler JK, 1500, F-150, and so on).

NameTypeReqDescription
makestring–Optional make to narrow models, for example Ford or Jeep.
yearinteger–Optional model year to narrow makes and models.

No output schema declared.

No examples provided.

search_parts ~37

Full-text and part-number search over listed products with listable prices only.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

tire_fitment ~77

Returns verified tire sizes, stated max tire claims, lift-only notes, and matching wheels from manufacturer strings already in the catalogue.

NameTypeReqDescription
makestringyes–
modelstringyes–
tirestring–Optional tire size token, for example 33x12.50R20.
yearintegeryes–

No output schema declared.

No examples provided.

Install

How do I install the Trail Fortress Fitment MCP server?

Trail Fortress Fitment is a hosted endpoint at https://trailfortress.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 · trailfortress.com

# add to Claude Code
claude mcp add --transport http com-trailfortress-fitment 'https://trailfortress.com/mcp/'
Common questions

What is the Trail Fortress Fitment MCP server?

Trail Fortress Fitment is an MCP server listed in the public MCP registry as com.trailfortress/fitment. Free, read-only truck and Jeep parts fitment: what fits your vehicle, fit checks, tire sizes. This page covers its hosted endpoint (https://trailfortress.com/mcp/).

Is the Trail Fortress Fitment MCP server safe to use?

Trail Fortress Fitment scores 85 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 Trail Fortress Fitment MCP server expose?

Trail Fortress Fitment exposes 6 tools: list_vehicle_options, find_parts_for_vehicle, check_part_fit, get_product, search_parts, tire_fitment. Their descriptions and schemas cost roughly 386 tokens of context every time the server is loaded.

Does the Trail Fortress Fitment MCP server require authentication?

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

Is the Trail Fortress Fitment MCP server still maintained?

Trail Fortress Fitment is still listed as active in the MCP registry. We last reached this channel on 21 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 Trail Fortress Fitment MCP server?

VerifyMCP ran 13 checks on Trail Fortress Fitment, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.