mcp server
MintMCP Docs
Search and read the official MintMCP documentation, the enterprise MCP gateway.
Description as published by the maintainer. Source
- version 1.1.0
- active
- documentation
- document understanding
- retrieval
active — Registry entry last updated 2026-07-22. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
fetch(id)- Fetch the full markdown content of a MintMCP documentation page by its id. Use it after search (or list_docs) to read a page in full before answering, for example the Snowflake connector setup, the SCIM provisioning guide, or the tool governance reference. If you have a public docs URL or a slug instead of a search-result id, use get_page. Required: id.
get_page(url)- Fetch a MintMCP documentation page from a public docs URL or a slug, for example "https://www.mintmcp.com/docs/security/tool-governance" or just "security/tool-governance". Use it when a user pastes a docs link or names a page directly. It returns the same full markdown content as fetch. Required: url.
list_docs(category)- List the MintMCP documentation table of contents, grouped by category (Getting Started, Architecture, connectors, Enterprise, Agent Monitor, and more). Each entry has a page id you can pass to fetch. Use it to see what the docs cover or to browse a category before reading a page. Pass an optional category to list just that group.
search(query)- Search the full MintMCP documentation and get back matching pages with their ids, titles, and URLs. Use this first for any MintMCP question: setup, capabilities, security, or a specific connector (Snowflake, Slack, GitHub) or feature (SCIM, SIEM export, prompt security, Coworker Agents). Then pass a result id to the fetch tool to read the page. Coverage spans architecture, enterprise controls, and per-connector setup guides. Required: query.
Last successful function declaration observed on . Source: https://www.mintmcp.com/docs/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://www.mintmcp.com/docs/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-22 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-22 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | www.mintmcp.com | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | www.mintmcp.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json