# TrekkSoft MCP by usefulapi (remote · trekksoft.usefulapi.io)

Read activities, bookings, guests and open departures in TrekkSoft.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `trekksoft.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-trekksoft/trekksoft.md), [page](https://verifymcp.io/servers/io-usefulapi-trekksoft/trekksoft)

## Channel facts

- Endpoint: `https://trekksoft.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### How do I install the TrekkSoft MCP by usefulapi server?

TrekkSoft MCP by usefulapi is a hosted endpoint at https://trekksoft.usefulapi.io/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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-trekksoft 'https://trekksoft.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-trekksoft": {
      "url": "https://trekksoft.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-trekksoft": {
      "type": "http",
      "url": "https://trekksoft.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-trekksoft]
url = "https://trekksoft.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-trekksoft": {
      "type": "remote",
      "url": "https://trekksoft.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-trekksoft --url 'https://trekksoft.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-trekksoft:
    url: "https://trekksoft.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-trekksoft": {
      "Transport": "http",
      "Url": "https://trekksoft.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-trekksoft -t streamable-http -u 'https://trekksoft.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-trekksoft": {
      "type": "http",
      "url": "https://trekksoft.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 18, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 64)

First indexed and scored.

## MCP tools (10)

### `trekksoft_list_activities` (~178 tokens)

List activities

List the tours and activities of your TrekkSoft account, with filters for merchant, category, title, active and bookable state. TrekkSoft API: GET /activities.

Input parameters:

- `category` (string): Category filter.
- `id` (array): Only these activity ids.
- `is_active` (boolean): Only active (true) or inactive (false) activities.
- `language` (string): Language code such as en, de, fr (default en).
- `limit` (integer): Results per page (default 30, maximum 100).
- `merchant` (array): Only activities of these merchant codes.
- `offset` (integer): Number of results to skip (default 0).
- `only_bookable` (boolean): Only bookable activities.
- `title_like` (string): Part of the activity title.

### `trekksoft_get_activity` (~74 tokens)

Get an activity

Get one activity by id: description, schedule, price categories and settings. TrekkSoft API: GET /activities/{activityId}.

Input parameters:

- `activity_id` (string, required): The activity id (from trekksoft_list_activities).
- `language` (string): Language code such as en, de, fr (default en).

### `trekksoft_list_bookings` (~215 tokens)

List bookings

List recent bookings. Filter by merchant, user email, free text, booking date, activity date, or changes since a time. TrekkSoft API: GET /bookings.

Input parameters:

- `activity_date` (string): Activity start date yyyy-mm-dd.
- `booked_after` (string): ISO 8601 time: only bookings made after it.
- `booking_date` (string): Booking date yyyy-mm-dd.
- `cancelled_after` (string): ISO 8601 time: only bookings cancelled after it.
- `changed_after` (string): ISO 8601 time: only bookings changed after it.
- `limit` (integer): Results per page (default 30, maximum 100).
- `merchant` (array): Only bookings sold by these merchant codes.
- `offset` (integer): Number of results to skip (default 0).
- `q` (string): Free text: booking id, guest name or email, activity name, booking number.
- `user` (array): Only bookings of these user emails.

### `trekksoft_get_booking` (~56 tokens)

Get a booking

Get one booking by id: activity, guests, prices, payments and status. TrekkSoft API: GET /bookings/{id}.

Input parameters:

- `booking_id` (string, required): The booking id (from trekksoft_list_bookings).

### `trekksoft_list_guests` (~167 tokens)

List guests

List guests (participants) with filters for booking, trip departure, phone, name and cancellation. TrekkSoft API: GET /guests.

Input parameters:

- `availability_item_id` (array): Only guests of these departures (availability item ids).
- `booking_id` (string): Only guests of this booking.
- `cancellation_date` (string): Cancellation date yyyy-mm-dd.
- `cancelled_after` (string): ISO 8601 time: only guests cancelled after it.
- `id` (array): Only these guest ids.
- `limit` (integer): Results per page (default 30, maximum 100).
- `name` (string): Guest name.
- `offset` (integer): Number of results to skip (default 0).
- `phone` (string): Guest phone number.

### `trekksoft_get_guest` (~53 tokens)

Get a guest

Get one guest by id, including booking link and check-in state. TrekkSoft API: GET /guest/{id}.

Input parameters:

- `guest_id` (string, required): The guest id (from trekksoft_list_guests).

### `trekksoft_list_availabilities` (~209 tokens)

List availabilities

List departures with free seats across activities, for a date range. TrekkSoft API: GET /availabilities.

Input parameters:

- `activity_id` (array): Only these activity ids.
- `departure_time` (string): Departure time hh:mm:ss.
- `language` (string): Language code such as en, de, fr (default en).
- `limit` (integer): Results per page (default 30, maximum 100).
- `merchant` (string): Merchant code.
- `offset` (integer): Number of results to skip (default 0).
- `only_booked` (boolean): Only departures with bookings.
- `only_not_booked` (boolean): Only departures without bookings.
- `seats` (integer): Minimum free seats.
- `starts_from` (string): First start date yyyy-mm-dd.
- `starts_to` (string): Last start date yyyy-mm-dd.
- `title_like` (string): Part of the activity title.
- `type` (array): Availability types.

### `trekksoft_list_activity_availabilities` (~188 tokens)

List availabilities of one activity

List departures with free seats for one activity. TrekkSoft API: GET /activities/{activityId}/availabilities.

Input parameters:

- `activity_id` (string, required): The activity id.
- `departure_time` (string): Departure time hh:mm:ss.
- `language` (string): Language code such as en, de, fr (default en).
- `limit` (integer): Results per page (default 30, maximum 100).
- `offset` (integer): Number of results to skip (default 0).
- `only_booked` (boolean): Only departures with bookings.
- `only_not_booked` (boolean): Only departures without bookings.
- `seats` (integer): Minimum free seats.
- `starts_from` (string): First start date yyyy-mm-dd.
- `starts_to` (string): Last start date yyyy-mm-dd.
- `type` (array): Availability types.

### `trekksoft_list_merchants` (~69 tokens)

List merchants

List the merchants your key pair can access. TrekkSoft API: GET /merchants.

Input parameters:

- `id` (array): Only these merchant ids.
- `language` (string): Language code such as en, de, fr (default en).
- `slug` (string): Merchant code.

### `trekksoft_list_shop_items` (~116 tokens)

List shop items

List shop items (extras sold with activities), filterable by merchant, category and active state. TrekkSoft API: GET /shop/items.

Input parameters:

- `active` (boolean): Only active (true) or inactive (false) items.
- `category_id` (array): Only items of these category ids.
- `id` (array): Only these item ids.
- `language` (string): Language code such as en, de, fr (default en).
- `merchant_id` (array): Only items of these merchant ids.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-trekksoft/trekksoft#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 65
- 2026-10-31: 64

## Common questions

### What is the TrekkSoft MCP by usefulapi server?

TrekkSoft MCP by usefulapi is listed in the public MCP registry as io.usefulapi/trekksoft. Read activities, bookings, guests and open departures in TrekkSoft. This page covers its hosted endpoint (https://trekksoft.usefulapi.io/mcp).

### Is the TrekkSoft MCP by usefulapi server safe to use?

TrekkSoft MCP by usefulapi scores 18 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 TrekkSoft MCP by usefulapi server expose?

TrekkSoft MCP by usefulapi exposes 10 tools: trekksoft_list_activities, trekksoft_get_activity, trekksoft_list_bookings, trekksoft_get_booking, trekksoft_list_guests, and 5 more. Their descriptions and schemas cost roughly 1,325 tokens of context every time the server is loaded.

### Does the TrekkSoft MCP by usefulapi server require authentication?

Its publisher declares no required credentials for TrekkSoft MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the TrekkSoft MCP by usefulapi server still maintained?

TrekkSoft MCP by usefulapi 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.

### What did VerifyMCP test on the TrekkSoft MCP by usefulapi server?

VerifyMCP ran 4 checks on TrekkSoft MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about TrekkSoft MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.

## Links

- Remote endpoint: https://trekksoft.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/trekksoft/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-trekksoft/trekksoft.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-trekksoft/trekksoft/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-trekksoft/trekksoft.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-trekksoft/trekksoft