Trailweights MCP Server

by trailweights Your server? Claim it

not responding

Trailweights MCP is listed as active in the registry but did not answer our last check. It exposes 8 tools. Last commit 12 Oct 2026.

Verified ultralight gear evidence for agents: weights, specs, reviews, consensus. Paid per call.

Uptime history 91 days of history · worst day 0%

91 days agonow

0.0%

Uptime 24h

0 of 91 checks

Tools

read from the server

917 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

What changed 21

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 August 2026. No other catalogue keeps this.

13 Oct 2 tool descriptions were rewritten get_product_specs, recommend_gear

12 Oct 7 tool descriptions were rewritten compare_gear, find_lighter_alternative, get_field_consensus and 4 more

12 Oct 3 tools changed the parameters they ask for find_lighter_alternative, recommend_gear, search_corpus

12 Oct a tool disappeared get_pack_template

20 Sep 2 tool descriptions were rewritten compare_gear, get_product_specs

21 Aug a tool appeared report_outcome

21 Aug a tool changed version

12 Aug 2 tool descriptions were rewritten get_field_consensus, recommend_gear

12 Aug a tool changed the parameters it asks for get_field_consensus

12 Aug a tool changed version

Trailweights MCP does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add trailweights-mcp --transport http https://trailweights.com/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://trailweights.com/api/mcp

~/.codex/config.toml

[mcp_servers.trailweights-mcp]
url = "https://trailweights.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "trailweights-mcp": {
      "url": "https://trailweights.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "trailweights-mcp": {
      "type": "http",
      "url": "https://trailweights.com/api/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compare

compare_gear

Compare two to six products using bounded spec rows, selected options, weight provenance and source links. Missing products are identified explicitly.

corpus

search_corpus

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.

field

get_field_consensus

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.

gear

get_gear_reviews

Creator review provenance for one product: at most three mentions with creator name, source URL, timestamp and sentiment. Transcript text is not returned.

lighter

find_lighter_alternative

Up to six lighter alternatives preserving the source product function, with verified weights, savings, selected options and source links.

product

get_product_specs

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.

recommend

recommend_gear

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.

report

report_outcome

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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_pack_template

removed 12 Oct 2026

Endpoints

URL	Transport	State	Latency	Checked
https://trailweights.com/api/mcp	streamable-http	answering	917 ms	12 min ago

Alternatives to Trailweights MCP

same job, measured the same way

Send Decision

by inboxpolicy

Send-decision email verification: agents get send/review/avoid with evidence, pay-per-call via x402.

answering

Aidimag

by aidimag

Persistent, verified memory for AI coding agents: recall, capture, guardrails, review queue.

local only

Runvouch

by runvouch

Watchdog for unattended AI agents: alerts, evidence checks and a verifiable proof per run.

7 tools answering

Factstable

by factstable

Verified fact packs for agents: statutory rates, passenger rights, consumer law — cite-or-refuse.

88 tools answering

Agent Evidence API

by thx93

Cited web evidence and fact checking for AI agents. $0.01 per call, no API key.

4 tools answering

AgentWeb (agentweb.us)

by agentweb

The action index for the web: real sites as callable, verified actions for AI agents.

answering

California Bitcoin

by californiabitcoin

Bitcoin research for AI agents: free answers, specialist Q&A, verification, evidence, timelines.

12 tools answering

LogicNodes

by logicnodes

Verified EVM, Aptos and finance tools for AI agents; gas for 14 chains. Pay per call (x402).

83 tools answering

Trailweights MCP — questions

Answers built from our own checks of this server.

What can Trailweights MCP do?

It exposes 8 tools, read directly from the server on our last check. Among them: compare_gear, find_lighter_alternative, get_field_consensus, get_gear_reviews, get_product_specs, recommend_gear and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Trailweights MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 917 ms. The bar chart above shows every period we have measured.

Did Trailweights MCP ever remove tools?

Yes. get_pack_template is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

The registry lists Trailweights MCP as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Trailweights MCP?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Trailweights MCP need an API key?

No. Trailweights MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

Is Trailweights MCP open source?

The code is open source: it is published under the MIT licence, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at trailweights.com, which runs on its operator's own terms.