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

Bsoft TMS

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

The registry describes it as: Official Bsoft TMS API, the leading transportation management system for Brazilian carriers (Bsoft b

We read its 51 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 bsoft-mcp https://api.mcp.ai/p_bsoft

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "bsoft-mcp": {
      "url": "https://api.mcp.ai/p_bsoft"
    }
  }
}

VS Code

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

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

bsoft_list_accounts bsoft_documentos_fiscais bsoft_documentos_fiscais_evento bsoft_transporte bsoft_transporte_write_create bsoft_transporte_write_create_lote bsoft_transporte_write_update bsoft_transporte_write_patch bsoft_transporte_write_delete bsoft_financeiro bsoft_financeiro_write_create bsoft_financeiro_write_create_lote bsoft_financeiro_write_update bsoft_financeiro_write_patch bsoft_financeiro_write_delete bsoft_controle_viagens bsoft_controle_viagens_write_create bsoft_controle_viagens_write_create_lote bsoft_controle_viagens_write_update bsoft_controle_viagens_write_patch bsoft_controle_viagens_write_delete bsoft_pessoas bsoft_pessoas_write_create bsoft_pessoas_write_create_lote bsoft_pessoas_write_update bsoft_pessoas_write_patch bsoft_pessoas_write_delete bsoft_manutencao bsoft_manutencao_write_create bsoft_manutencao_write_create_lote bsoft_manutencao_write_update bsoft_manutencao_write_patch bsoft_manutencao_write_delete bsoft_os bsoft_os_write_create bsoft_os_write_create_lote bsoft_os_write_update bsoft_os_write_patch bsoft_os_write_delete bsoft_recursos bsoft_recursos_write_create bsoft_recursos_write_create_lote bsoft_recursos_write_update bsoft_recursos_write_patch bsoft_recursos_write_delete 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-bsoft-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-bsoft-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.