Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.meetlark/mcp-server

NPM · @MEETLARK/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 20

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

0 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 495 tokens (~82/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the ai.meetlark/mcp-server server?

ai.meetlark/mcp-server runs locally as an npm package, launched with npx -y @meetlark/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @meetlark/mcp-server

# add to Claude Code
claude mcp add ai-meetlark-mcp-server -- npx -y @meetlark/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-meetlark-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@meetlark/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-meetlark-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@meetlark/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ai-meetlark-mcp-server -- npx -y @meetlark/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-meetlark-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@meetlark/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-meetlark-mcp-server --command npx --arg -y --arg @meetlark/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  ai-meetlark-mcp-server:
    command: "npx"
    args: ["-y", "@meetlark/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-meetlark-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@meetlark/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ai-meetlark-mcp-server -t stdio -c npx -a -y @meetlark/mcp-server
// mcp.json
{
  "mcpServers": {
    "ai-meetlark-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@meetlark/mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@meetlark/mcp-server@1.0.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~495 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
meetlark_close_poll ~44

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

NameTypeReqDescription
adminTokenstringyesThe adm_xxx token from poll creation

No output schema declared.

No examples provided.

meetlark_create_poll ~141

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.

NameTypeReqDescription
creatorEmailstringyesEmail address of the poll creator
creatorNamestringName of the poll creator
descriptionstringAdditional context for participants
timeSlotsarrayyesAvailable time slots to vote on
titlestringyesWhat is this poll for?

No output schema declared.

No examples provided.

meetlark_get_admin_view ~92

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), and admin URLs. Use the admin token from poll creation. Use this to check vote status or results.

NameTypeReqDescription
adminTokenstringyesThe adm_xxx token from poll creation

No output schema declared.

No examples provided.

meetlark_get_results ~87

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.

NameTypeReqDescription
participateTokenstringyesThe prt_xxx token from the participation URL

No output schema declared.

No examples provided.

meetlark_reopen_poll ~47

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

NameTypeReqDescription
adminTokenstringyesThe adm_xxx token from poll creation

No output schema declared.

No examples provided.

meetlark_vote ~84

Cast a vote on a scheduling poll. Each time slot can be voted yes, maybe, or no. Use the participation token from the poll's participate URL.

NameTypeReqDescription
namestringyesName to display in results
participateTokenstringyesThe prt_xxx token from the participation URL
votesarrayyesVotes for each time slot

No output schema declared.

No examples provided.

Common questions

What is the ai.meetlark/mcp-server server?

ai.meetlark/mcp-server is listed in the public MCP registry as ai.meetlark/mcp-server. Agent-first meeting schedule polls for humans and agents. Create polls, vote, find times. This page covers its npm package (@meetlark/mcp-server).

Is the ai.meetlark/mcp-server server safe to use?

ai.meetlark/mcp-server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ai.meetlark/mcp-server server expose?

ai.meetlark/mcp-server exposes 6 tools: meetlark_create_poll, meetlark_get_results, meetlark_vote, meetlark_get_admin_view, meetlark_close_poll, meetlark_reopen_poll. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.

Is the ai.meetlark/mcp-server server still maintained?

ai.meetlark/mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.