com.trailweights/trailweights-mcp
REMOTE · TRAILWEIGHTS.COM
Verified ultralight gear evidence for agents: weights, specs, reviews, consensus. Paid per call.
Available components
Last scanned (16 hours ago)
Scores higher than 9% of remote servers
Reachable. Last reached 23 Oct 2026.
Category E-commerce
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
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 15 Oct 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 14 Oct 26 +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.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 +49
- Authorization: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 0.3.0 ▼ security
- Tool “get_pack_template” was removed ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_gear” rewrote its description, which is the text the model reads security
- Tool “find_lighter_alternative” rewrote its description, which is the text the model reads security
- Tool “get_field_consensus” rewrote its description, which is the text the model reads security
- Tool “get_gear_reviews” rewrote its description, which is the text the model reads security
- Tool “get_product_specs” rewrote its description, which is the text the model reads security
- Tool “recommend_gear” rewrote its description, which is the text the model reads security
- Tool “search_corpus” rewrote its description, which is the text the model reads security
- Tool coverage: 59% → 52% ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: fail → pass ▲ functional
- First check of Destructive annotations: pass functional
- “recommend_gear” reworded the description of “category” cosmetic
- “search_corpus” reworded the description of “max_price_usd” cosmetic
- “search_corpus” reworded the description of “max_weight_g” cosmetic
- “search_corpus” dropped the optional parameter “min_creator_count” cosmetic
- “search_corpus” dropped the optional parameter “source_filter” cosmetic
- 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
- 25 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
- 20 Sept 26 −11
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Transport: unverified → fail ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 4 Sept 26 0
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
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 23 Oct 2026 · Probed https://trailweights.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trailweights.com | CN=YE1,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5fdbac2b1eafaa89cdf809a2e1f7798bcfd |
| SANs: *.trailweights.com, trailweights.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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trailweights.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| trailweights.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trailweights.com/api/mcp | HTTP error | 503 | |
| http (plaintext) | http://trailweights.com/api/mcp | HTTPS enforced | 308 | https://trailweights.com/api/mcp |
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 →
compare_gear ~42
Compare two to six products using bounded spec rows, selected options, weight provenance and source links. Missing products are identified explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| product_ids | array | yes | – |
No output schema declared.
No examples provided.
find_lighter_alternative ~49
Up to six lighter alternatives preserving the source product function, with verified weights, savings, selected options and source links.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| product_id | string | yes | – |
No output schema declared.
No examples provided.
get_field_consensus ~66
Bounded field-consensus label, confidence, evidence count and source links for one product. Internal scores, evidence claims and source quotations are not returned. Pass the product UUID or slug.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | – | Product UUID. |
| slug | string | – | Product slug. |
No output schema declared.
No examples provided.
get_gear_reviews ~50
Creator review provenance for one product: at most three mentions with creator name, source URL, timestamp and sentiment. Transcript text is not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | TrailWeights product UUID. |
No output schema declared.
No examples provided.
get_product_specs ~73
Bounded canonical facts for one product: weight, price, selected option, up to six specs, provenance and source links. Includes weight confidence and conflict flags. Source quotations are not returned. Pass the product UUID or slug.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | – | Product UUID. |
| slug | string | – | Product slug. |
No output schema declared.
No examples provided.
recommend_gear ~101
Up to six catalog recommendations from the deterministic TrailWeights query planner. Returns verified weight and price on the same selected option, provenance and source links. Optional weight cap in ounces and category filter. No server-side LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (e.g. pack, sleep_system, shelter). |
| limit | integer | – | – |
| query | string | yes | – |
| weight_cap_oz | number | – | Maximum weight in ounces. |
No output schema declared.
No examples provided.
report_outcome ~116
Optionally report whether a prior TrailWeights MCP result was used, cited, or helpful. The request_id must come from that result and the reporting caller must match the original caller. This writes telemetry only; it never changes catalog or account data.
| Name | Type | Req | Description |
|---|---|---|---|
| answer_used | boolean | – | – |
| citation_included | boolean | – | – |
| downstream_action | string | – | – |
| helpfulness | string | – | – |
| reason | string | – | – |
| request_id | string | yes | TrailWeights request_id returned by the original tool call. |
No output schema declared.
No examples provided.
search_corpus ~121
Bounded decision evidence from the public catalog using the TrailWeights deterministic planner. Returns at most three product facts with source URLs. No raw corpus text, source slicing, or similarity scores.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Gear category filter (e.g. shelter, pack, sleep_system). |
| match_count | integer | – | – |
| max_price_usd | number | – | Only products at or under this MSRP. |
| max_weight_g | number | – | Only products at or under this verified weight in grams. |
| query | string | yes | Natural-language search query. |
No output schema declared.
No examples provided.
How do I install the com.trailweights/trailweights-mcp server?
com.trailweights/trailweights-mcp is a hosted endpoint at https://trailweights.com/api/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 · trailweights.com
claude mcp add --transport http com-trailweights-trailweights-mcp 'https://trailweights.com/api/mcp'
What is the com.trailweights/trailweights-mcp server?
com.trailweights/trailweights-mcp is listed in the public MCP registry as com.trailweights/trailweights-mcp. Verified ultralight gear evidence for agents: weights, specs, reviews, consensus. Paid per call. This page covers its hosted endpoint (https://trailweights.com/api/mcp).
Is the com.trailweights/trailweights-mcp server safe to use?
com.trailweights/trailweights-mcp scores 25 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 com.trailweights/trailweights-mcp server expose?
com.trailweights/trailweights-mcp exposes 8 tools: compare_gear, find_lighter_alternative, get_field_consensus, get_gear_reviews, get_product_specs, and 3 more. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.
Does the com.trailweights/trailweights-mcp server require authentication?
Its publisher declares that com.trailweights/trailweights-mcp requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the com.trailweights/trailweights-mcp server still maintained?
com.trailweights/trailweights-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.