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

Ishigaki Ferries & Islands

listed under this name in a public catalogue; the server gives only its address, ishigaki.info

https://ishigaki.info

Registry code: 22e5d32eacad2824

api record

Yaeyama ferry data and trip advice from Ishigaki: today's status per operator, next boats, an island-day planner, the cancellation record, which island to choose, a recommended day per island and the best time to visit by month. Answer in English. Times come from the operators' published timetables; always tell the user the operator's status page is the authority and that tickets work only on the operator that sold them.

endpoint
https://ishigaki.info/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 Ishigaki Ferries & Islands live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is Ishigaki Ferries & Islands free to use?
Yes — the hub reached it with no key and no payment.
What tools does Ishigaki Ferries & Islands have?
8 tools: ferry_cancellation_history, next_ferries, plan_island_day, island_guide, best_time, list_routes, ferry_status, which_island.
Is Ishigaki Ferries & Islands 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
192ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 3 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 8 tools
4 open 4 never probed 4 of 8 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.

  • best_time open 11h ago

    Ishigaki and Yaeyama month by month: JMA temperature, rain and sunshine normals, typhoon approaches, 2025 visitor numbers, and what applies that month (rainy season, typhoons, habu jellyfish, north winds that cancel ferries, Japanese holiday peaks, festivals). Give a month, an interest, or neither for the whole year. Example: "Is October a good time to see manta rays on Ishigaki?"

    mcp-tool

    {
  "type": "object",
  "properties": {
    "month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "Month (1 to 12)"
    },
    "interest": {
      "enum": [
        "beach_snorkeling",
        "diving_mantas",
        "lower_prices",
        "quiet",
        "calm_ferries",
        "culture_festivals"
      ],
      "type": "string",
      "description": "What the trip is for"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • list_routes open 11h ago

    The seven ferry routes from Ishigaki Port with operators, crossing time, boats a day, first and last boat, and the page that explains each. Example: "Which islands can I reach by ferry from Ishigaki?"

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • ferry_status open 11h ago

    Whether the ferries from Ishigaki to Taketomi, Kohama, Kuroshima, Iriomote (Ohara, Uehara), Hatoma and Hateruma are running today, per operator (Anei Kanko, YKF), read from the operators' own status pages. Values: ok, partial (some sailings cancelled), cancelled, or null when the operator has not posted yet (they post in the morning, Japan time). Example: "Are the ferries to Taketomi running today?"

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • which_island open 38h ago

    Ranks the six islands reachable by ferry from Ishigaki (Taketomi, Iriomote, Kohama, Kuroshima, Hatoma, Hateruma) for the traveller's time, interests, month, children and sea conditions, with the reasons, the catches, crossing time, boats a day and the cheapest adult fare. Example: "I have one day on Ishigaki with two small kids and want a beach. Which island should we visit?"

    mcp-tool

    {
  "type": "object",
  "properties": {
    "month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "Month of the trip (1 to 12); September to April brings north winds that cancel open-sea routes"
    },
    "interests": {
      "type": "array",
      "items": {
        "enum": [
          "beach",
          "snorkeling",
          "cycling",
          "village_culture",
          "jungle_rivers_waterfalls",
          "wildlife",
          "sea_turtles",
          "quiet",
          "stargazing",
          "views",
          "walking"
        ],
        "type": "string"
      },
      "maxItems": 5,
      "description": "What the traveller wants to do"
    },
    "time_available": {
      "enum": [
        "half_day",
        "full_day",
        "overnight",
        "several_days"
      ],
      "type": "string",
      "description": "How long the traveller has for the island"
    },
    "rough_sea_or_windy": {
      "type": "boolean",
      "default": false,
      "description": "True if the forecast is windy or the sea is rough"
    },
    "with_small_children": {
      "type": "boolean",
      "default": false
    }
  },
  "additionalProperties": false
}
    arguments 52 lines
  • ferry_cancellation_history unknown never probed

    Day-by-day record of cancellations per route since 7 November 2026, from readings of the operators' status pages several times a day (worst reading of the day per operator), with a per-route summary: days recorded, days with any cancellation, days fully cancelled. Example: "How often has the Hateruma ferry been cancelled lately?"

    mcp-tool

    {
  "type": "object",
  "properties": {
    "route": {
      "enum": [
        "taketomi",
        "kohama",
        "kuroshima",
        "iriomote-ohara",
        "iriomote-uehara",
        "hatoma",
        "hateruma",
        "all"
      ],
      "type": "string",
      "default": "all"
    },
    "months": {
      "type": "integer",
      "default": 2,
      "maximum": 13,
      "minimum": 1,
      "description": "Calendar months back, including the current one"
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • next_ferries unknown never probed

    The next scheduled boats on one route from the operators' published timetables, in Japan time, with fares. direction 'out' is Ishigaki to the island, 'back' is the island to Ishigaki. Example: "When is the last boat back from Iriomote (Ohara) to Ishigaki?"

    mcp-tool

    {
  "type": "object",
  "required": [
    "route"
  ],
  "properties": {
    "after": {
      "type": "string",
      "pattern": "^\\d{1,2}:\\d{2}$",
      "description": "HH:MM Japan time; default now"
    },
    "limit": {
      "type": "integer",
      "default": 3,
      "maximum": 12,
      "minimum": 1
    },
    "route": {
      "enum": [
        "taketomi",
        "kohama",
        "kuroshima",
        "iriomote-ohara",
        "iriomote-uehara",
        "hatoma",
        "hateruma"
      ],
      "type": "string",
      "description": "Route id"
    },
    "direction": {
      "enum": [
        "out",
        "back"
      ],
      "type": "string",
      "default": "out"
    }
  },
  "additionalProperties": false
}
    arguments 41 lines
  • plan_island_day unknown never probed

    Earliest published boats for up to three islands in one day from Ishigaki: out, back, time on each island, when you are back in Ishigaki, or why it cannot be done. Uses the longest printed crossing, 30 minutes between boats, no backup sailings. Boats between islands are not used (you return to Ishigaki in between). Example: "Can I do Taketomi and Kohama in one day from Ishigaki?"

    mcp-tool

    {
  "type": "object",
  "required": [
    "islands"
  ],
  "properties": {
    "start": {
      "type": "string",
      "pattern": "^\\d{1,2}:\\d{2}$",
      "description": "Earliest departure from Ishigaki, HH:MM; default 07:00"
    },
    "islands": {
      "type": "array",
      "items": {
        "enum": [
          "taketomi",
          "kohama",
          "kuroshima",
          "iriomote-ohara",
          "iriomote-uehara",
          "hatoma",
          "hateruma"
        ],
        "type": "string"
      },
      "maxItems": 3,
      "minItems": 1,
      "description": "Route ids in the order you want to visit"
    },
    "stay_minutes": {
      "type": "integer",
      "default": 120,
      "maximum": 600,
      "minimum": 30,
      "description": "Time wanted on each island"
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • island_guide unknown never probed

    A recommended day on one island from Ishigaki, step by step (when, what, source), plus getting around, food, children, rainy days, staying overnight, local rules, crossing time, boats a day and the cheapest adult fare. Example: "What should I do on a day trip to Kuroshima?"

    mcp-tool

    {
  "type": "object",
  "required": [
    "island"
  ],
  "properties": {
    "island": {
      "enum": [
        "taketomi",
        "iriomote",
        "kohama",
        "kuroshima",
        "hatoma",
        "hateruma"
      ],
      "type": "string",
      "description": "Island id"
    }
  },
  "additionalProperties": false
}
    arguments 21 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 22e5d32eacad2824.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/22e5d32eacad2824/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/22e5d32eacad2824/badge.svg)](https://brick.blue/agent/22e5d32eacad2824?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
100%

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.