ZEI 231 MCP Server

by zei Your server? Claim it

answering

ZEI 231 is answering right now. Last checked 3 min ago.

Crea il Modello 231 dalla chat: attività sensibili, reati, protocolli e preventivo del consulente.

Uptime history 26 days of history

26 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

319 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add registro-231 --transport http https://zei.services/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://zei.services/api/mcp

~/.codex/config.toml

[mcp_servers.registro-231]
url = "https://zei.services/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "registro-231": {
      "url": "https://zei.services/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "registro-231": {
      "type": "http",
      "url": "https://zei.services/api/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

URL	Transport	State	Latency	Checked
https://zei.services/api/mcp	streamable-http	sign-in	155 ms	3 min ago

Alternatives to ZEI 231

same job, measured the same way

Cadlens MCP

by cadlens-co

Model Context Protocol server that wraps the CADLens REST API.

60 installs/wk local only

Trello MCP Server

by billnobill

Trello Model Context Protocol (MCP) Server for AI Agents

40 installs/wk local only

ChatPPT

by parkerdiamond

Model Context Protocol (MCP) server for programmatic PowerPoint creation and editing

69 installs/wk local only

MCP Tmux

by k8ika0s

Model Context Protocol server that lets LLMs collaboratively drive tmux

80 installs/wk local only

Datawrapper

by palewire

A Model Context Protocol (MCP) server and app for creating Datawrapper charts using AI assistants

367 installs/wk local only

Esa MCP Server

by koki-develop

A Model Context Protocol (MCP) server for esa.io

56 installs/wk local only

Nx MCP

by nrwl

A Model Context Protocol server implementation for Nx

125 210 installs/wk local only

Nx Console

by nrwl

A Model Context Protocol server implementation for Nx

local only

ZEI 231 — questions

Answers built from our own checks of this server.

Why is there no tool list for ZEI 231?

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 ZEI 231 working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 319 ms. The bar chart above shows every period we have measured.

How do I connect ZEI 231?

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 ZEI 231?

No API key is involved. ZEI 231 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 ZEI 231?

It answers our handshake in 319 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.