Home / MCP registry index / io.github.mcp-dir/hivecloud-mcp

HiveCloud CT-e / MDF-e

io.github.mcp-dir/hivecloud-mcp in the official MCP registry. Endpoint https://api.mcp.ai/p_hivecloud. Source: github.com/mcp-dir/hivecloud-mcp.

The registry describes it as: Transportation fiscal-document issuer from Bsoft by nstech (HiveCloud). Query CT-e (freight bill of

We read its 33 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 hivecloud-mcp https://api.mcp.ai/p_hivecloud

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "hivecloud-mcp": {
      "url": "https://api.mcp.ai/p_hivecloud"
    }
  }
}

VS Code

code --add-mcp '{"name":"hivecloud-mcp","type":"http","url":"https://api.mcp.ai/p_hivecloud"}'

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.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

hivecloud_list_accounts hivecloud_list_empresas hivecloud_list_ctes hivecloud_get_cte hivecloud_cte_dacte hivecloud_cte_xml hivecloud_nfe_info hivecloud_cte_criar_de_nfe hivecloud_list_dces hivecloud_list_inutilizacoes hivecloud_sefaz_status hivecloud_mdfe_empresas hivecloud_list_mdfes hivecloud_get_mdfe hivecloud_mdfe_damdfe hivecloud_mdfe_xml hivecloud_relatorio_viagens hivecloud_list_veiculos hivecloud_list_motoristas hivecloud_cte_emitir hivecloud_cte_cancelar hivecloud_cte_excluir hivecloud_cte_averbar hivecloud_cte_carta_correcao hivecloud_mdfe_emitir hivecloud_mdfe_encerrar hivecloud_mdfe_cancelar show_version report_bug connect toolkit_info marketplace authenticate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-hivecloud-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-hivecloud-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.