mcpbeat Sign in

Lyssna MCP Server

answering

Lyssna is answering right now. Last checked 7 min ago.

Query and summarize research data across tests and surveys

Uptime history 62 days of history · worst day 98%
62 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
526 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Lyssna every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.lyssna.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.lyssna.com/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.lyssna.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.lyssna.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.lyssna.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.lyssna.com/mcp streamable-http sign-in 584 ms 7 min ago

Alternatives to Lyssna

same job, measured the same way
mabl
by mabl

AI-powered test automation: run tests, analyze failures, query results across mabl workspaces.

answering
Userbrain
by userbrain

Explore your Userbrain user test data, summarize feedback, and uncover actionable insights faster.

answering
The Wiley Rule (public data)
by thewileyrule

Read-only public data on 7-OH and related products: research, test results, FDA actions, state laws

11 tools answering
Chainstack
by chainstack

Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.

23 tools answering
O
Openapi Navigator
by mgaruccio

Navigate and query OpenAPI specs with fuzzy search, pagination, and API testing

54 installs/wk local only
Applitools
by applitools

Create, update, review, and resolve visual tests with Applitools Eyes across any supported SDK.

1 401 installs/wk local only
ReactionMetric MCP
by 7l7

Five-trial reaction-time summary and links to browser-based reaction tests.

2 tools answering
Versive
by getversive

Create, launch, and analyze user research studies, AI interviews, and AI tests from your AI agent.

answering

Lyssna — questions

Answers built from our own checks of this server.

Why is there no tool list for Lyssna?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Lyssna working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 526 ms. The bar chart above shows every period we have measured.
How do I connect Lyssna?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Lyssna?
No API key is involved. Lyssna answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Lyssna?
It answers our handshake in 526 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.