mcpbeat Sign in

Lexica MCP Server

by uselexica Your server? Claim it
answering

Lexica is answering right now. Last checked 6 min ago.

Language flashcards in your AI assistant: build decks, edit cards and review what's due in the chat.

Uptime history 8 days of history
8 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
309 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Lexica 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 6 min ago.

run in your terminal
claude mcp add lexica --transport http https://api.uselexica.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.uselexica.com/mcp
~/.codex/config.toml
[mcp_servers.lexica]
url = "https://api.uselexica.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "lexica": {
      "url": "https://api.uselexica.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "lexica": {
      "type": "http",
      "url": "https://api.uselexica.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://api.uselexica.com/mcp streamable-http sign-in 202 ms 6 min ago

Alternatives to Lexica

same job, measured the same way
Study Flashcards Exam Prep
by theluckystrike

Build study flashcards and exam-prep decks from your AI chat, all stored locally.

17 tools answering
Simplepages
by simplepages

Build and edit landing pages and websites from your AI assistant, and pull how they are performing.

answering
Kanban Importer
by njligames

Read and move Trello cards by the task ids your AI assistant invented.

706 installs/wk local only
trulyform
by trulyform

Build, edit and publish forms and read their responses from your AI assistant.

answering
Replo
by replohq

Research competitors and build, edit, and manage ecommerce sites from your AI assistant.

84 tools answering
OpenAdapt: your agent decides, OpenAdapt enters it and checks it saved
by openadaptai

Your AI agent decides what to enter. OpenAdapt enters it in the app and checks that it saved.

3 248 installs/wk local only
Spark
by plusdocs

Build, change, check and publish your Spark sites and apps from your AI assistant.

answering
DoLoop
by getdoloop

Recurring tasks in loops. Your assistant reads today's tasks, checks or skips them, edits loops.

answering

Lexica — questions

Answers built from our own checks of this server.

Why is there no tool list for Lexica?
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 Lexica 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 309 ms. The bar chart above shows every period we have measured.
How do I connect Lexica?
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 Lexica?
No API key is involved. Lexica 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 Lexica?
It answers our handshake in 309 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.