_ registry / mcp streamable-http · checked 6m ago

liqaa

https://liqaa.io

Registry code: 6c9ce986addfbfc9

api record

LIQAA is a sovereign, end-to-end-encrypted video-meeting platform (WebRTC over a LiveKit SFU) that runs in the browser with no install and no account. Use create_instant_room to spin up a meeting and get a shareable join link; list_plans for pricing and participant limits; platform_capacity for the load-tested technical specs; platform_stats for public figures.

endpoint
https://liqaa.io/api/mcp
protocol
streamable-http ·2024-11-05
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 liqaa live?
Yes — it answered the hub's last check (checked 6m ago). It answered 99% of checks over the last 30 days.
Is liqaa free to use?
Yes — the hub reached it with no key and no payment.
What tools does liqaa have?
4 tools: create_instant_room, list_plans, platform_capacity, platform_stats.
Is liqaa 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
98.7%

90 days 98.7%· all time 98.7%

latency
516ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 523 checks · signed record
  • down → live
  • degraded → down· HTTP 500
  • live → degraded· HTTP 500
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
communication chat & messaging
used for
  • create an instant video meeting
  • list video meeting plans
  • get platform capacity specs
takes → gives
text → data
tools
3 reads1 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

_ what it can do 4 tools
3 open 1 never probed 3 of 4 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.

  • list_plans reads open 12h ago

    List LIQAA subscription plans with monthly price (DZD) and the maximum participants allowed per meeting.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • platform_capacity reads open 12h ago

    Return LIQAA's load-tested technical capacity and architecture: max participants, real measured load-test results, transport, encryption and latency.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • platform_stats reads open 12h ago

    Return public, aggregate LIQAA usage figures (no personal data): registered users, meetings created, and meetings that actually convened.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • create_instant_room changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "description": "Optional display title for the meeting."
    }
  }
}
    arguments 9 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 6c9ce986addfbfc9.

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

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.