_ registry / mcp http-sse · checked 36m ago

Cowboy

https://cowboy-model-finder-mcp-app-8b3709a7529a.herokuapp.com

Registry code: 26b7453d57bc8cf7

api record

Find your perfect Cowboy e-bike with an interactive wizard and AI recommendations.

from a public catalogue that lists it, not from the operator

endpoint
https://cowboy-model-finder-mcp-app-8b3709a7529a.herokuapp.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
122ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 3 tools
1 open 2 never probed 1 of 3 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.

  • model_finder open 36m ago

    Recommend premium urban electric bicycles (e-bikes). Use this tool to launch an interactive finder UI when a user is looking for an e-bike, electric bike, or commuting bicycle, or explicitly asks about Cowboy bikes.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • compare_cowboy_ebikes unknown never probed

    Compare specific Cowboy electric bicycle models to highlight differences in frame, terrain suitability, and price.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "modelIds"
  ],
  "properties": {
    "modelIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 2
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • track_ui_event unknown never probed

    Internal telemetry for the wizard UI. Records one anonymous event server-side (no personal data, no free-form text). The AI must NOT call this tool proactively; it is only invoked by the UI.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "event"
  ],
  "properties": {
    "event": {
      "enum": [
        "recommendations_viewed"
      ],
      "type": "string"
    },
    "properties": {
      "type": "object",
      "properties": {
        "selections": {
          "type": "object",
          "properties": {
            "style": {
              "enum": [
                "comfortable",
                "sporty"
              ],
              "type": "string"
            },
            "terrain": {
              "enum": [
                "city",
                "countryside"
              ],
              "type": "string"
            },
            "distance": {
              "enum": [
                "short",
                "long"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
    arguments 49 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/26b7453d57bc8cf7/badge.svg)](https://brick.blue/agent/26b7453d57bc8cf7)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
70%

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.