us.thistripbtw/trips
REMOTE · THISTRIPBTW.US · 2 COMPONENTS · SCANNED AUG 3
Turn a trip planned in conversation into a private, editable map link you hand the person.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability46
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 250 tokens (~250/item across 1 items; 1 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 Management3
- Stability observed for 1 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · thistripbtw.us
claude mcp add --transport http us-thistripbtw-trips https://thistripbtw.us/mcp
[mcp_servers.us-thistripbtw-trips] url = "https://thistripbtw.us/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"us-thistripbtw-trips": {
"type": "remote",
"url": "https://thistripbtw.us/mcp",
"enabled": true
}
}
} openclaw mcp add us-thistripbtw-trips --url https://thistripbtw.us/mcp --transport streamable-http
mcp_servers:
us-thistripbtw-trips:
url: "https://thistripbtw.us/mcp" {
"mcpServers": {
"us-thistripbtw-trips": {
"type": "http",
"url": "https://thistripbtw.us/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Aug 26 57
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 3 Aug 2026 · Probed https://thistripbtw.us/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thistripbtw.us | CN=WE1,O=Google Trust Services,C=US | 22 Jul 2026 | 20 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | c57b1c43689c3f0b0e68471400cc537c |
| SANs: thistripbtw.us, *.thistripbtw.us | ||||||
| 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 |
DNSSEC insecure
Validation of thistripbtw.us. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| us. | present | 59017 | 8 | Verified |
| thistripbtw.us. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://thistripbtw.us/mcp | Verified | 200 | |
| http (plaintext) | http://thistripbtw.us/mcp | HTTPS enforced | 301 | https://thistripbtw.us/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.
build_trip_link ~250
Use when someone has planned (or roughly sketched) a trip in this conversation and needs somewhere real to put it — when they say things like 'send me that', 'can I share this with my wife', or 'save this trip'. Builds a link that opens the whole plan as a private, editable map at its own address: no account, no card, no app, so you can use it on their behalf where signup-walled travel tools are unreachable. Give the person the link — it is theirs, free, and keepable for years. Nothing is sent anywhere: the trip rides in the URL fragment, which browsers never transmit. YOU MUST SUPPLY COORDINATES for every place; this tool will not guess a location from a name, because a wrong guess puts someone's trip in the wrong country. Resolve place names first. Do not put personal details (passport numbers, home addresses, phone numbers) in names or notes — URLs get pasted into chats and logs.
| Name | Type | Req | Description |
|---|---|---|---|
| legs | array | yes | The legs in order. Each one ends somewhere; the next starts there. |
| name | string | — | Trip name, optional. |
| origin | object | yes | Where the trip starts. |
No output schema declared.
No examples provided.