ai.meetlark/mcp-server
REMOTE · MEETLARK.AI · 2 COMPONENTS · SCANNED SEP 20
Agent-first meeting schedule polls for humans and agents. Create polls, vote, find times.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 548 tokens (~91/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
How do I install the ai.meetlark/mcp-server server?
ai.meetlark/mcp-server is a hosted endpoint at https://meetlark.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · meetlark.ai
claude mcp add --transport http ai-meetlark-mcp-server 'https://meetlark.ai/mcp'
{
"mcpServers": {
"ai-meetlark-mcp-server": {
"url": "https://meetlark.ai/mcp"
}
}
} {
"servers": {
"ai-meetlark-mcp-server": {
"type": "http",
"url": "https://meetlark.ai/mcp"
}
}
} [mcp_servers.ai-meetlark-mcp-server] url = "https://meetlark.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-meetlark-mcp-server": {
"type": "remote",
"url": "https://meetlark.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-meetlark-mcp-server --url 'https://meetlark.ai/mcp' --transport streamable-http
mcp_servers:
ai-meetlark-mcp-server:
url: "https://meetlark.ai/mcp" {
"McpServers": {
"ai-meetlark-mcp-server": {
"Transport": "http",
"Url": "https://meetlark.ai/mcp"
}
}
} assistant mcp add ai-meetlark-mcp-server -t streamable-http -u 'https://meetlark.ai/mcp'
{
"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.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 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.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 · Probed https://meetlark.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=meetlark.ai | CN=YR1,O=Let's Encrypt,C=US | 10 Aug 2026 | 8 Nov 2026 | RSA 2048 | SHA256-RSA | 5eeaba00a4ce4a794ca1a3445ac582c1a00 |
| SANs: meetlark.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of meetlark.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| meetlark.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meetlark.ai/mcp | Verified | 200 | |
| http (plaintext) | http://meetlark.ai/mcp | HTTPS enforced | 308 | https://meetlark.ai/mcp |
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 →
meetlark_close_poll ~44
Close a poll to stop accepting new votes. Use the admin token from poll creation.
| Name | Type | Req | Description |
|---|---|---|---|
| adminToken | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorEmail | string | yes | Email address of the poll creator |
| creatorName | string | – | Name of the poll creator |
| description | string | – | Additional context for participants |
| timeSlots | array | yes | Available time slots to vote on |
| title | string | yes | What is this poll for? |
No output schema declared.
No examples provided.
meetlark_get_admin_view ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| adminToken | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| participateToken | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| adminToken | string | yes | The adm_xxx token from poll creation |
No output schema declared.
No examples provided.
meetlark_vote ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Participant's email address (required). Used to identify returning voters and send confirmation email. | |
| name | string | yes | Name to display in results |
| participateToken | string | yes | The prt_xxx token from the participation URL |
| votes | array | yes | Votes for each time slot |
No output schema declared.
No examples provided.
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 hosted endpoint (https://meetlark.ai/mcp).
Is the ai.meetlark/mcp-server server safe to use?
ai.meetlark/mcp-server scores 82 out of 100 on VerifyMCP. 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 548 tokens of context every time the server is loaded.
Does the ai.meetlark/mcp-server server require authentication?
No. We connected to ai.meetlark/mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.