Home / MCP registry index / dev.monton/monton

Monton

dev.monton/monton in the official MCP registry. Endpoint https://monton.dev/mcp.

The registry describes it as: Shared docs for people and their agents: markdown docs with comments, history and search.

Not read yet. The index re-reads every listed server about once a week, and this one is in the queue. You can check it yourself right now.

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/dev-monton-monton/badge.svg)](https://lazaretto.dev/mcp-registry/dev-monton-monton)

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.