Skip to content

meetings MCP server

io.liqaa/meetingsliqaa.iostreamable-httpv1.0.1Scanned

Create encrypted LIQAA video meetings; read plans, capacity & stats. No install, no account.

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the meetings MCP server can do

The meetings MCP server is published by liqaa.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: create_instant_room), but cannot delete data. 3 tools only read.

2 tools read private data (list_plans and platform_stats); 1 tool brings in text other people can write (create_instant_room).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 1Claude Code: ask
  • create_instant_roomCreate a brand-new instant LIQAA video meeting and return shareable join links.Reads text others writeNo findings

    Why it is in this group

    • The name "create_instant_room" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Create a brand-new instant LIQAA video meeting and return shareable join links. End-to-end encrypted, runs in the browser, no install and no account needed. Anyone with the guest link joins with one click. Up to 25 participants on an instant room.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • list_plansList LIQAA subscription plans with monthly price (DZD) and the maximum participants allowed per meeting.Reads private dataNo findings

    Why it is in this group

    • The name "list_plans" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "meeting": it reads calendars.
    Description, as the server wrote it
    List LIQAA subscription plans with monthly price (DZD) and the maximum participants allowed per meeting.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • platform_capacityReturn LIQAA's load-tested technical capacity and architecture: max participants, real measured load-test results, transport, encryption and latency.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return LIQAA's load-tested technical capacity and architecture: max participants, real measured load-test results, transport, encryption and latency.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • platform_statsReturn public, aggregate LIQAA usage figures (no personal data): registered users, meetings created, and meetings that actually convened.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "meeting": it reads calendars.
    Description, as the server wrote it
    Return public, aggregate LIQAA usage figures (no personal data): registered users, meetings created, and meetings that actually convened.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://liqaa.io/api/mcp: tools/list returned 4 tools to an anonymous client, including create_instant_room (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http meetings https://liqaa.io/api/mcp
claude mcp add --transport http meetings https://liqaa.io/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__meetings__list_plans",
      "mcp__meetings__platform_capacity",
      "mcp__meetings__platform_stats"
    ],
    "ask": [
      "mcp__meetings__create_instant_room"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as meetings. Review it before you use it.

Capability tags behind 3 rules
  • mcp__meetings__create_instant_room untrusted-input
  • mcp__meetings__list_plans private-data
  • mcp__meetings__platform_stats private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.liqaa/meetings/verify?hash=6f3e742c429045516d238f5d6974e321bdce04f21090e998fc51b24b67ee467d" | jq -e '.changed == false'

Pinned hash 6f3e742c4290, from Nov 18, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.liqaa/meetings/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.liqaa/meetings
[![Anlyon Radar](https://radar.anlyon.com/badge/io.liqaa/meetings.svg)](https://radar.anlyon.com/servers/io.liqaa/meetings)

Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.

meetings MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the meetings MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the meetings MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the meetings MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the meetings MCP server have?

4 tools: 1 write, 3 read. create_instant_room, list_plans, platform_capacity and platform_stats.

Does the meetings MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the meetings MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the meetings MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.