Community · Official remote MCP server

The Gisti — AI Checklists MCP server,
connected in one click.

Read, AI-create, and edit your Gisti checklists in plain language from any MCP client. Connect the official Gisti — AI Checklists MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.

Connect Gisti — AI Checklists free How it works

Free to start · No credit card · No hosting needed

Use this server

Add Gisti — AI Checklists to your AI in one minute

Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.

claude mcp add --transport http gisti-ai-checklists https://gisti-mcp.gisti.workers.dev/mcp

Run in your terminal, then restart Claude Code. The client will open the vendor's sign-in the first time you use it.

Gisti — AI Checklists · https://gisti-mcp.gisti.workers.dev/mcp

What you can do

What your AI can do with Gisti — AI Checklists

Real prompts you can type the moment it's connected — no setup, no docs to read.

“What can Gisti — AI Checklists do for me?”

“Show me the tools Gisti — AI Checklists exposes.”

Security check

How secure is the Gisti — AI Checklists MCP server?

Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Gisti — AI Checklists holds up.

✓ Verified directory serverGisti — AI Checklists · workers.dev

Official endpoint

Operated by Gisti — AI Checklists (workers.dev) at its documented MCP endpoint — not a third-party mirror or community re-host.

OAuth sign-in — your account, your rules

You grant access from your own Gisti — AI Checklists account and can revoke it there at any time. gate never sees your password.

Scanned before it goes live

gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.

Watched for drift

If Gisti — AI Checklists adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.

Gisti — AI Checklists's server requires OAuth, so it can't be scanned anonymously — connect it in gate and the same scan runs automatically before it goes live.

How it works

Connected in three steps

Connect your gate

Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.

Pick Gisti — AI Checklists

Choose Gisti — AI Checklists in the gate directory. Sign in to your Gisti — AI Checklists account to grant access.

Use it anywhere

Gisti — AI Checklists's tools are live in every AI client you've connected — with rules and logging built in.

Connect Gisti — AI Checklists free

Free to start · No credit card · No hosting needed

Author

Who runs the Gisti — AI Checklists MCP server?

workers.dev

More servers from workers.dev →

Own this server? Claim the listing →

Server facts

The Gisti — AI Checklists MCP server at a glance

Endpointhttps://gisti-mcp.gisti.workers.dev/mcp

Operated byGisti — AI Checklists (workers.dev)

CategoryCommunity

Sign-inOAuth — your account, revocable anytime

Available in gateYes — one-click connect

Works withClaude, ChatGPT, Cursor & any MCP client

FAQ

Questions, answered

Is there an official Gisti — AI Checklists MCP server?

Yes — Gisti — AI Checklists operates its own remote MCP server at gisti-mcp.gisti.workers.dev. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.

How do I connect Gisti — AI Checklists to Claude or ChatGPT?

Add gate's gateway URL to your AI client once, then pick Gisti — AI Checklists in the directory. You sign in to Gisti — AI Checklists via OAuth to grant access. From then on, Gisti — AI Checklists's tools are available in every client you've connected to gate.

Do I need to host anything?

No. Gisti — AI Checklists runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.

Is the Gisti — AI Checklists MCP server safe to connect?

It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.