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

meetlark

https://meetlark.ai

Registry code: be0f7747c16b06dd

api record

Agent-first meeting schedule polls for humans and agents. Create polls, vote, find times.

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

endpoint
https://meetlark.ai/mcp
protocol
http-sse ·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 meetlark live?
Yes — it answered the hub's last check (checked 22m ago). It answered 99% of checks over the last 30 days.
Is meetlark free to use?
Yes — the hub reached it with no key and no payment.
What tools does meetlark have?
6 tools: meetlark_close_poll, meetlark_create_poll, meetlark_vote, meetlark_get_admin_view, meetlark_reopen_poll, meetlark_get_results.
Is meetlark 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
99.4%

90 days 98.5%· all time 98.6%

latency
210ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 470 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • create a meeting scheduling poll
  • vote on meeting times
  • get poll results
  • close or reopen a poll
takes → gives
text → data
tools
2 reads4 changes data
_ 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 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.

  • meetlark_close_poll changes data unknown never probed

    Close a poll to stop accepting new votes. Use the admin token from poll creation.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "adminToken"
      ],
      "properties": {
        "adminToken": {
          "type": "string",
          "description": "The adm_xxx token from poll creation"
        }
      }
    }
    arguments 13 lines
  • meetlark_create_poll changes data unknown never probed

    Create a scheduling poll to find a time that works for a group. Returns an admin URL (keep private) and a participation URL (share with participants). The creator's email must be verified -- if not yet verified, a verification email is sent automatically. Ask the user to check their inbox and click the link, then retry.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "title",
        "timeSlots",
        "creatorEmail"
      ],
      "properties": {
        "title": {
          "type": "string",
          "description": "What is this poll for?"
        },
        "timeSlots": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "date",
              "startTime",
              "endTime"
            ],
            "properties": {
              "date": {
                "type": "string",
                "description": "Date in YYYY-MM-DD format"
              },
              "endTime": {
                "type": "string",
                "description": "End time in HH:MM format"
              },
              "startTime": {
                "type": "string",
                "description": "Start time in HH:MM format"
              }
            }
          },
          "description": "Available time slots to vote on"
        },
        "creatorName": {
          "type": "string",
          "description": "Name of the poll creator"
        },
        "description": {
          "type": "string",
          "description": "Additional context for participants"
        },
        "creatorEmail": {
          "type": "string",
          "description": "Email address of the poll creator"
        }
      }
    }
    arguments 53 lines
  • meetlark_vote changes data unknown never probed

    Cast a vote on a scheduling poll. Each time slot can be voted yes, maybe, or no. Requires participant name and email. Use the participation token from the poll's participate URL. If the email matches a previous voter on this poll, their response is updated instead of creating a duplicate.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "participateToken",
        "name",
        "email",
        "votes"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Name to display in results"
        },
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "description": "Participant's email address (required). Used to identify returning voters and send confirmation email."
        },
        "votes": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "timeSlotId",
              "value"
            ],
            "properties": {
              "value": {
                "enum": [
                  "yes",
                  "maybe",
                  "no"
                ],
                "type": "string",
                "description": "Vote value"
              },
              "timeSlotId": {
                "type": "string",
                "description": "Time slot ID"
              }
            }
          },
          "description": "Votes for each time slot"
        },
        "participateToken": {
          "type": "string",
          "description": "The prt_xxx token from the participation URL"
        }
      }
    }
    arguments 52 lines
  • meetlark_get_admin_view reads unknown never probed

    Get full poll details including all votes and participants. This is the only way to see who voted and how they voted. Returns poll info, time slots, every participant's votes (yes/maybe/no per slot), participant emails, and admin URLs. Use the admin token from poll creation. Use this to check vote status or results.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "adminToken"
      ],
      "properties": {
        "adminToken": {
          "type": "string",
          "description": "The adm_xxx token from poll creation"
        }
      }
    }
    arguments 13 lines
  • meetlark_reopen_poll changes data unknown never probed

    Reopen a previously closed poll to accept votes again. Use the admin token from poll creation.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "adminToken"
      ],
      "properties": {
        "adminToken": {
          "type": "string",
          "description": "The adm_xxx token from poll creation"
        }
      }
    }
    arguments 13 lines
  • meetlark_get_results reads unknown 14h ago

    Get poll details and available time slots using a participation token. Returns the poll title, description, status, and time slots -- but NOT votes or participant data. This is the view a participant sees before voting. To see who voted and how, use meetlark_get_admin_view instead.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "participateToken"
      ],
      "properties": {
        "participateToken": {
          "type": "string",
          "description": "The prt_xxx token from the participation URL"
        }
      }
    }
    arguments 13 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 be0f7747c16b06dd.

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