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

meetzone-api

https://meetzone-api.mike-tusa.workers.dev

Registry code: 786662f095813747

api record

MeetZone finds meeting times that fall inside working hours in several IANA time zones at once, DST-aware. Use search_timezones to turn a city or country name into an IANA zone id, then find_meeting_overlap with 2-5 zones. This MCP endpoint is the free tier: up to 5 zones, 7 days, 5 ranked slots and 5 search results per call, about 10 tool calls per minute per IP. No API key. Larger plans (PRO) are on RapidAPI: https://rapidapi.com/miketusa/api/meetzone-timezone-meeting-overlap-api. Contact: [email protected].

endpoint
https://meetzone-api.mike-tusa.workers.dev/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 meetzone-api live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is meetzone-api free to use?
Yes — the hub reached it with no key and no payment.
What tools does meetzone-api have?
2 tools: find_meeting_overlap, search_timezones.
Is meetzone-api 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
218ms

last good check

priced tools
0

of 2 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

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

  • find_meeting_overlap unknown 1h ago

    Given 2-5 IANA time zones (e.g. America/New_York, Europe/London, Asia/Tokyo), a local working window applied in every zone (default 09:00-17:00) and up to 7 calendar days, returns up to 5 ranked meeting slots in UTC with each zone's local time, UTC offset and abbreviation, DST-aware, plus an optional ICS event for the top slot. Read-only, pure computation (no calendars are read). Same engine as POST /v1/overlap on the free BASIC plan.

    mcp-tool

    {
      "type": "object",
      "required": [
        "zones"
      ],
      "properties": {
        "days": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
            "maxLength": 10
          },
          "maxItems": 7,
          "description": "Dates YYYY-MM-DD (default: today + 6 days, UTC)"
        },
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Max ranked slots (default 5, max 5)"
        },
        "zones": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 64,
            "minLength": 1
          },
          "maxItems": 5,
          "minItems": 2,
          "description": "IANA zone ids, e.g. [\"America/New_York\",\"Europe/London\"]"
        },
        "work_hours": {
          "type": "object",
          "required": [
            "start",
            "end"
          ],
          "properties": {
            "end": {
              "type": "string",
              "pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]$",
              "maxLength": 5
            },
            "start": {
              "type": "string",
              "pattern": "^([01][0-9]|2[0-3]):[0-5][0-9]$",
              "maxLength": 5
            }
          },
          "description": "Local working window applied in each zone (default 09:00-17:00)",
          "additionalProperties": false
        },
        "include_ics": {
          "type": "boolean",
          "description": "Include an ICS VEVENT for the top slot (default true)"
        },
        "duration_minutes": {
          "type": "integer",
          "maximum": 480,
          "minimum": 5,
          "description": "Meeting length in minutes (default 30)"
        }
      },
      "additionalProperties": false
    }
    arguments 67 lines
  • search_timezones unknown 1h ago

    Look up IANA time zone ids by city, country, alias or a raw IANA id (e.g. "tokyo", "india", "PST"). Returns up to 5 matches; with a date, also each zone's UTC offset and abbreviation on that day. Read-only. Same engine as GET /v1/zones/search on the free BASIC plan.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "maxLength": 64,
          "description": "Search text, e.g. \"london\""
        },
        "date": {
          "type": "string",
          "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
          "maxLength": 10,
          "description": "Optional YYYY-MM-DD for offsets/abbreviations"
        },
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "Max results (default 5)"
        }
      },
      "additionalProperties": false
    }
    arguments 26 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 786662f095813747.

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

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.