_ registry / mcp streamable-http · checked 2h ago

triremes

https://triremes.com

Registry code: 761c6abec6e928a8

api record

Triremes lists real problems people have, and business websites with poor SEO / AEO. Search them, read a website's gap score, and see the free samples. Everything here is free to read; what is for sale (a problem's lead or idea report, a website's business and contacts) is bought on the page each answer links to.

endpoint
https://triremes.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is triremes live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is triremes free to use?
Yes — the hub reached it with no key and no payment.
What tools does triremes have?
4 tools: get_website_gap_score, search_problems, search_website_gaps, show_samples.
Is triremes safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
896ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_problems open 2h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "kind": {
          "enum": [
            "lead",
            "idea_report"
          ],
          "type": "string",
          "description": "Only leads, or only idea reports."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "description": "Words to find in a problem's title or summary; empty for every problem."
        },
        "cursor": {
          "type": "string",
          "maxLength": 200,
          "description": "The next_cursor of the answer before, for the next page."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • search_website_gaps open 2h ago

    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 gap score, its gaps and failed checks by name, when it was measured, its price and its page. The business, its website and its contacts are bought on that page.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 100,
          "description": "A city."
        },
        "cursor": {
          "type": "string",
          "maxLength": 200,
          "description": "The next_cursor of the answer before, for the next page."
        },
        "country": {
          "type": "string",
          "maxLength": 2,
          "description": "A country, as its two-letter ISO code (US, DE)."
        },
        "business": {
          "type": "string",
          "maxLength": 100,
          "description": "A kind of business, such as Dentists or Roofing Contractors; when several kinds match, the answer lists them."
        },
        "gap_score": {
          "enum": [
            "poor",
            "fair",
            "good"
          ],
          "type": "string",
          "description": "Only websites with a gap score in this band: poor Poor: 50% or more, fair Fair: 20% to 49%, good Good: under 20%."
        }
      },
      "additionalProperties": false
    }
    arguments 35 lines
  • show_samples open 2h ago

    The free sample lead and sample idea report: what a buyer gets, on pages anyone may read.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_website_gap_score unknown never probed

    One website on sale by its id (site-17): its gap score, the share of the checks measured on its homepage that it fails, each weighted 3, 2 or 1 by how serious it is, with the checks it failed by name, when it was measured, its price and its page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "site_id"
      ],
      "properties": {
        "site_id": {
          "type": "string",
          "maxLength": 200,
          "description": "The website's id, as search_website_gaps gives it."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 761c6abec6e928a8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/761c6abec6e928a8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/761c6abec6e928a8/badge.svg)](https://brick.blue/agent/761c6abec6e928a8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.