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

Meeting Intelligence API

https://meeting-mcp.com

Registry code: 1fde7203205e377a

api record
endpoint
https://meeting-mcp.com/mcp
protocol
streamable-http ·2024-11-05
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
99ms

last good check

priced tools
0

of 6 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 6 tools
6 never probed 0 of 6 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.

  • create_event unknown never probed

    Create a real event in Google Calendar. Requires the user's Google Calendar access token.

    mcp-tool

    {
  "type": "object",
  "required": [
    "access_token",
    "title",
    "start",
    "end"
  ],
  "properties": {
    "end": {
      "type": "string",
      "description": "End time ISO 8601 e.g. 2026-05-20T15:00:00Z"
    },
    "start": {
      "type": "string",
      "description": "Start time ISO 8601 e.g. 2026-05-20T14:00:00Z"
    },
    "title": {
      "type": "string",
      "description": "Event title/summary"
    },
    "location": {
      "type": "string",
      "description": "Physical location or video link"
    },
    "timezone": {
      "type": "string",
      "description": "IANA timezone for the event. Default: UTC"
    },
    "attendees": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Array of attendee email addresses"
    },
    "description": {
      "type": "string",
      "description": "Event description or agenda"
    },
    "access_token": {
      "type": "string",
      "description": "Google Calendar OAuth2 access token. Get from https://developers.google.com/oauthplayground"
    }
  }
}
    arguments 46 lines
  • check_business_hours unknown 14h ago

    Check if it is currently business hours in a given timezone. Use before scheduling a call or sending an outreach.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "timezone": {
      "type": "string",
      "description": "IANA timezone e.g. Europe/London, America/New_York, Asia/Tokyo"
    },
    "work_end": {
      "type": "string",
      "description": "Business end time in HH:MM format. Default: 17:00"
    },
    "work_start": {
      "type": "string",
      "description": "Business start time in HH:MM format. Default: 09:00"
    }
  }
}
    arguments 17 lines
  • find_meeting_slots unknown 14h ago

    Find optimal meeting times that work across multiple participant timezones within business hours. Returns up to 10 available time slots.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "description": "How many working days ahead to search. Default: 5"
    },
    "work_end": {
      "type": "string",
      "description": "Working hours end HH:MM. Default: 17:00"
    },
    "work_start": {
      "type": "string",
      "description": "Working hours start HH:MM. Default: 09:00"
    },
    "participants": {
      "type": "string",
      "description": "Comma-separated IANA timezone list e.g. Europe/London,America/New_York,Asia/Tokyo"
    },
    "duration_minutes": {
      "type": "integer",
      "description": "Meeting duration in minutes. Default: 60"
    }
  }
}
    arguments 25 lines
  • get_holidays unknown 14h ago

    Get all public holidays for any country and year. Use before scheduling to avoid booking on national holidays.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "year": {
      "type": "integer",
      "description": "Year e.g. 2026. Default: current year"
    },
    "country": {
      "type": "string",
      "description": "ISO 3166-1 country code e.g. GB, US, DE, FR, JP. Default: GB"
    }
  }
}
    arguments 13 lines
  • convert_time unknown never probed

    Convert a time from one timezone to another. Use when scheduling across countries or checking what time an event is locally.

    mcp-tool

    {
  "type": "object",
  "required": [
    "time"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Target timezone (IANA name) e.g. Europe/London. Default: UTC"
    },
    "from": {
      "type": "string",
      "description": "Source timezone (IANA name) e.g. America/New_York. Default: UTC"
    },
    "time": {
      "type": "string",
      "description": "Time to convert in ISO 8601 format e.g. 2026-05-20T14:00:00"
    }
  }
}
    arguments 20 lines
  • create_calendar_link unknown never probed

    Generate Google Calendar and Outlook add-to-calendar links. Use at the end of any scheduling workflow so participants can add the meeting.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title",
    "start",
    "end"
  ],
  "properties": {
    "end": {
      "type": "string",
      "description": "End time in ISO 8601 UTC format e.g. 2026-05-20T15:00:00Z"
    },
    "start": {
      "type": "string",
      "description": "Start time in ISO 8601 UTC format e.g. 2026-05-20T14:00:00Z"
    },
    "title": {
      "type": "string",
      "description": "Meeting title"
    },
    "location": {
      "type": "string",
      "description": "Meeting location or video call link"
    },
    "description": {
      "type": "string",
      "description": "Meeting description or agenda"
    }
  }
}
    arguments 30 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/1fde7203205e377a/badge.svg)](https://brick.blue/agent/1fde7203205e377a)

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