# Triremes (remote · triremes.com)

Search real problems people have and business websites with poor SEO/AEO. Read-only, free.

- Trust score: 71/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `triremes.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-triremes-triremes/triremes.md), [page](https://verifymcp.io/servers/com-triremes-triremes/triremes)

## Channel facts

- Endpoint: `https://triremes.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 813 tokens (~203/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Triremes MCP server?

Triremes is a hosted endpoint at https://triremes.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.

### Claude

```bash
claude mcp add --transport http com-triremes-triremes 'https://triremes.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-triremes-triremes": {
      "url": "https://triremes.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-triremes-triremes": {
      "type": "http",
      "url": "https://triremes.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-triremes-triremes]
url = "https://triremes.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-triremes-triremes --url 'https://triremes.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-triremes-triremes:
    url: "https://triremes.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-triremes-triremes": {
      "Transport": "http",
      "Url": "https://triremes.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-triremes-triremes -t streamable-http -u 'https://triremes.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-triremes-triremes": {
      "type": "http",
      "url": "https://triremes.com/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-05 (score 71, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_website_gap_score” rewrote its description, which is the text the model reads
- [security] Tool “search_website_gaps” rewrote its description, which is the text the model reads
- [cosmetic] “search_website_gaps” reworded the description of “gap_score”
- [cosmetic] Tool “get_website_gap_score” changed its title: A website's gap score → A website's SEO score

### 2026-11-04 (score 70, 0)

- [security] Tool “get_website_gap_score” rewrote its description, which is the text the model reads
- [security] Tool “search_problems” rewrote its description, which is the text the model reads
- [security] Tool “search_website_gaps” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 174 → 203
- [functional] Server version: 2025-06-18 → 1.0.0
- [cosmetic] “search_website_gaps” reworded the description of “gap_score”

### 2026-11-03 (score 70, −1)

- [security] Tool “search_problems” rewrote its description, which is the text the model reads
- [security] Tool “get_website_gap_score” rewrote its description, which is the text the model reads
- [security] Tool “search_website_gaps” rewrote its description, which is the text the model reads
- [security] Tool “show_samples” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 137 → 174
- [cosmetic] “search_problems” added an optional parameter “max_sold”
- [cosmetic] “search_website_gaps” added an optional parameter “max_sold”

### 2026-11-02 (score 71, +1)

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

### 2026-11-01 (score 70, 0)

- [security] Tool “get_website_gap_score” rewrote its description, which is the text the model reads

### 2026-10-30 (score 70, +1)

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

### 2026-10-28 (score 69, +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.

### 2026-10-27 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `search_problems` (~187 tokens)

Search problems

Search the problems people have that Triremes lists, biggest first: each with its title, tier, how many reports and when the first and the last were, the day Triremes listed it, its summary as its page shows it, whether it is sold as a lead (businesses that have it) or an idea report, its price, how many times a lead has been sold and when it last was, and its page. Leads and idea reports are bought on that page.

Input parameters:

- `cursor` (string): The next_cursor of the answer before, for the next page.
- `kind` (string): Only leads, or only idea reports.
- `max_sold` (integer): Only leads sold at most this many times; 0 for those never sold.
- `query` (string): Words to find in a problem's title or summary; empty for every problem.

### `search_website_gaps` (~331 tokens)

Search websites with poor SEO / AEO

Search the business websites Triremes measured with gaps in what search engines and AI answer engines can read, each one sold on its own: what kind of business and where, its SEO score and its label, the checks it failed by name, when it was measured, its price, how many times it has been sold and when it last was, and its page. The business, its website and its contacts are bought on that page. One with no SEO score yet is being measured (being_measured): no price, and it can be bought once it has an SEO score.

Input parameters:

- `business` (string): A kind of business, such as Dentists or Roofing Contractors; when several kinds match, the answer lists them.
- `city` (string): A city.
- `country` (string): A country, as its two-letter ISO code (US, DE).
- `cursor` (string): The next_cursor of the answer before, for the next page.
- `gap_score` (string): Only websites with an SEO score in this band: catastrophic (Catastrophic: 100%), badly-flawed (Badly flawed: 50% to 99%), flawed (Flawed: 20% to 49%), lightly-flawed (Lightly flawed: 1% to 19%), no-g…
- `max_sold` (integer): Only websites sold at most this many times; 0 for those never sold.

### `get_website_gap_score` (~185 tokens)

A website's SEO score

One website on sale by its id (3f9a1c07b2e85d64): its SEO score, the share of Triremes' checks of what search engines can read on its homepage that it fails, weighted by how serious each check is (0% means no gaps; higher is worse), with its label (No gaps, Lightly flawed, Flawed, Badly flawed or Catastrophic), the checks it failed by name, when it was measured, its price, how many times it has been sold and the time of each sale, and its page. A website with no SEO score yet is being measured: being_measured is true, it has no price and it can be bought once it has an SEO score.

Input parameters:

- `site_id` (string, required): The website's id, as search_website_gaps gives it.

### `show_samples` (~35 tokens)

Free samples

The free sample lead, idea report and website with poor SEO / AEO: what a buyer gets, on pages anyone may read.

## Diagnostics

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

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68

## Common questions

### What is the Triremes MCP server?

Triremes is an MCP server listed in the public MCP registry as com.triremes/triremes. Search real problems people have and business websites with poor SEO/AEO. Read-only, free. This page covers its hosted endpoint (https://triremes.com/mcp).

### Is the Triremes MCP server safe to use?

Triremes scores 71 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 Triremes MCP server expose?

Triremes exposes 4 tools: search_problems, search_website_gaps, get_website_gap_score, show_samples. Their descriptions and schemas cost roughly 738 tokens of context every time the server is loaded.

### Does the Triremes MCP server require authentication?

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

### Is the Triremes MCP server still maintained?

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

## Links

- Remote endpoint: https://triremes.com/mcp
- Website: https://triremes.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-triremes-triremes/triremes.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-triremes-triremes/triremes.json
- HTML version of this page: https://verifymcp.io/servers/com-triremes-triremes/triremes