# ai.meetlark/mcp-server (remote · meetlark.ai)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `meetlark.ai`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ai-meetlark-mcp-server/meetlark.md), [page](https://verifymcp.io/servers/ai-meetlark-mcp-server/meetlark)
- npm · `@meetlark/mcp-server`: 61/100, [markdown](https://verifymcp.io/servers/ai-meetlark-mcp-server/meetlark-mcp-server.md), [page](https://verifymcp.io/servers/ai-meetlark-mcp-server/meetlark-mcp-server)

## Channel facts

- Endpoint: `https://meetlark.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 548 tokens (~91/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-meetlark-mcp-server https://meetlark.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-meetlark-mcp-server]
url = "https://meetlark.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-meetlark-mcp-server": {
      "type": "remote",
      "url": "https://meetlark.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-meetlark-mcp-server --url https://meetlark.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-meetlark-mcp-server:
    url: "https://meetlark.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-meetlark-mcp-server": {
      "type": "http",
      "url": "https://meetlark.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (6)

### `meetlark_create_poll` (~141 tokens)

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.

Input parameters:

- `creatorEmail` (string, required): Email address of the poll creator
- `creatorName` (string): Name of the poll creator
- `description` (string): Additional context for participants
- `timeSlots` (array, required): Available time slots to vote on
- `title` (string, required): What is this poll for?

### `meetlark_get_results` (~87 tokens)

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.

Input parameters:

- `participateToken` (string, required): The prt_xxx token from the participation URL

### `meetlark_vote` (~134 tokens)

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.

Input parameters:

- `email` (string, required): Participant's email address (required). Used to identify returning voters and send confirmation email.
- `name` (string, required): Name to display in results
- `participateToken` (string, required): The prt_xxx token from the participation URL
- `votes` (array, required): Votes for each time slot

### `meetlark_get_admin_view` (~95 tokens)

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.

Input parameters:

- `adminToken` (string, required): The adm_xxx token from poll creation

### `meetlark_close_poll` (~44 tokens)

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

Input parameters:

- `adminToken` (string, required): The adm_xxx token from poll creation

### `meetlark_reopen_poll` (~47 tokens)

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

Input parameters:

- `adminToken` (string, required): The adm_xxx token from poll creation

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-meetlark-mcp-server/meetlark#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 70
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://meetlark.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-meetlark-mcp-server/meetlark/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-meetlark-mcp-server/meetlark/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-meetlark-mcp-server/meetlark