Developer · Remote MCP server
Gisti - AI Checklists
Read, AI-create, and edit your Gisti checklists in plain language from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.AntonChuraev99/gisti-mcp- Version
- 0.4.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-14
- Updated
- 2026-07-14
- Publisher
- AntonChuraev99 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/AntonChuraev99) · how
- Repository
- github.com/AntonChuraev99/AiChecklists
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://gisti-mcp.gisti.workers.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Gisti - AI Checklists
Gisti - AI Checklists is a remote MCP server: there is nothing to install. Its endpoint is https://gisti-mcp.gisti.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| GigaversePortable Roth IRA signups for gig workers: eligibility checks, signup initiation, partners, sandbox. | Remote · HTTPLive check: ✓ handshake |
| gildara.ioOperating contracts for AI agents. Structured instructions compiled into system prompts. | Local · stdio |
| Giljo HQContext engineering for AI coding agents: product context, project missions, and 360 memory. | Remote · HTTPLive check: sign-in required |
| GirderSaves AI coding-agent context by giving exact code instead of whole files, from a local graph. | Local · stdio |
| GitLocal Git via MCP: status, log, diff, file history, branches, and gated stage/commit. Pure-JS. | Local · stdio |
| GitGit log, diff, blame, branch stats for AI agents. | Local · stdio |
| Git ArchaeologistTrace code history, commit reasoning, and PR context directly from Git logs. | Local · stdio |
| Git EnhancedEnhanced Git MCP Server - Code review, commit analysis, and branch management. | Local · stdio |