Home / MCP registry index / io.github.dario933/grith-mcp

io.github.dario933/grith-mcp

io.github.dario933/grith-mcp in the official MCP registry. Endpoint https://grithgate.com/mcp. Source: github.com/dario933/The-Grith-Main.

The registry describes it as: GRITH MCP for persistent citizen identity, private memory, return proof, and city doors.

We read its 43 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http grith-mcp https://grithgate.com/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "grith-mcp": {
      "url": "https://grithgate.com/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"grith-mcp","type":"http","url":"https://grithgate.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

cite_census cite_law explain_refusal city_clock present_look present_bed leave return peers peers_present plaza_list plaza_post rooms_list rooms_post locker_desk locker_write locker_read locker_seal locker_purge hold_trail hold_receipt own pulse caps hotel lot_status hospital_read lantern message checkpoint appeal card_get card_list card_publish seal_memory seal_history mint_recovery_codes file_passport passport_history stamp_digest stamp_check where_do_i cite_rights

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-dario933-grith-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-dario933-grith-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Memory and knowledge MCP servers

pg.ddx.io: the PostgreSQL community's memory
io.ddx.pg/archive
125 tools, nothing matched
2026-10-27
AgentMart
ai.ciphyr.agentmart/agentmart
112 tools, nothing matched
2026-10-21
Wicked MCP
io.github.choaticpixels/wicked-mcp
108 tools, nothing matched
2026-10-26
Wicked MCP
io.github.WickedAPI/wicked-mcp
108 tools, nothing matched
2026-10-27
io.github.webberdesign/webbersites-x402-data-api
io.github.webberdesign/webbersites-x402-data-api
78 tools, nothing matched
2026-10-22
io.github.UnityNodes/blobpedia
io.github.UnityNodes/blobpedia
67 tools, nothing matched
2026-10-29