Skip to content

BitVisual MCP server

br.com.bitvisual/bitvisual-mcpbitvisual.com.brstreamable-httpv3.0.1Scanned

Agent-ready print shop in Sao Paulo: catalog, official BRL quotes per m2, shipping, PIX orders.

6 tools: 5 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 5 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BitVisual MCP server can do

The BitVisual MCP server is published by bitvisual.com.br, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: listar_catalogo, cotar, consultar_prazo, consultar_requisitos_arte and 1 more), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (criar_pedido).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 3.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 5Claude Code: ask
  • consultar_prazoPrazo de produção do produto e opções de entrega/retirada em São Paulo.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Prazo de produção do produto e opções de entrega/retirada em São Paulo. Informe o CEP de destino para o frete real. Passe as mesmas opcoes do pedido: um canvas esticado em chassi viaja em caixa rígida e custa muito mais frete que a impressão enrolada no tubo.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • consultar_requisitos_arteRetorna os requisitos técnicos do arquivo de impressão (formatos, resolução, cores, sangria) e como enviá-lo.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Retorna os requisitos técnicos do arquivo de impressão (formatos, resolução, cores, sangria) e como enviá-lo. Não recebe nem analisa o arquivo: só informa as regras. Use antes de criar_pedido para orientar o cliente.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • cotarCota o preço oficial de um produto.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Cota o preço oficial de um produto. Para produtos por m² informe largura_cm e altura_cm EM CENTÍMETROS (nunca assuma a unidade — confirme com o cliente antes). Para tiragem informe quantidade. Retorna preço unitário, total, as opções/acabamentos disponíveis com o preço de cada uma e o link do produto. Para cotar COM acabamento (ex.: canvas esticado em chassi de madeira), repita a chamada passando opcoes. Não cria pedido.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • criar_pedidoCria um pedido REAL na BitVisual e retorna o link da página do pedido em bitvisual.com.br, onde o cliente conclui o pagamento por PIX.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Cria um pedido REAL na BitVisual e retorna o link da página do pedido em bitvisual.com.br, onde o cliente conclui o pagamento por PIX. Só funciona para produtos cotáveis (use cotar() antes). Pedidos até R$ 1.000 entram direto; acima disso viram orçamento com atendimento humano. Retirada GRÁTIS na loja (Vila Mariana/SP) ou ENTREGA em todo o Brasil: informe o endereço completo com CEP e o frete real entra no total. Passe em opcoes os acabamentos escolhidos (eles mudam preço e frete). ANTES de chamar, confirme com o cliente: produto, medidas em cm, quantidade, acabamento, total, nome, e-mail e WhatsApp. A produção só começa após o pagamento e o envio da arte. EFEITO COLATERAL: cria um pedido real e gera a cobrança PIX no provedor de pagamento (Mercado Pago); com CEP, cota o frete em transportadora. Não cancela nem altera pedidos — para mudar ou desistir, o cliente fala com o atendimento humano. Limite de 5 pedidos por hora por cliente.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • status_pedidoConsulta o status de um pedido existente (produção, arte, rastreio e total).No findings

    Why it is in this group

    • The name "status_pedido" says "status": a word for reading.
    Description, as the server wrote it
    Consulta o status de um pedido existente (produção, arte, rastreio e total). Só leitura. Exige o número do pedido E o e-mail usado na compra — sem os dois não devolve nada, para não expor dados de terceiros.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bitvisual.com.br/mcp: tools/list returned 6 tools to an anonymous client, including listar_catalogo (write), cotar (write), consultar_prazo (write), consultar_requisitos_arte (write), criar_pedido (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 added, 3 removed, 3 changed.+3 added−3 removed~3 changedView diff

Install

Pinned to version 3.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http bitvisual https://bitvisual.com.br/mcp
claude mcp add --transport http bitvisual https://bitvisual.com.br/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bitvisual__status_pedido"
    ],
    "ask": [
      "mcp__bitvisual__listar_catalogo",
      "mcp__bitvisual__cotar",
      "mcp__bitvisual__consultar_prazo",
      "mcp__bitvisual__consultar_requisitos_arte",
      "mcp__bitvisual__criar_pedido"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bitvisual. Review it before you use it.

Capability tags behind 1 rule
  • mcp__bitvisual__criar_pedido untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/br.com.bitvisual/bitvisual-mcp/verify?hash=0773d3e223b1cd179ecfc14c42e826513382287d1b50b0689b6cd6a3d860b4fe" | jq -e '.changed == false'

Pinned hash 0773d3e223b1, from Nov 17, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/br.com.bitvisual/bitvisual-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for br.com.bitvisual/bitvisual-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/br.com.bitvisual/bitvisual-mcp.svg)](https://radar.anlyon.com/servers/br.com.bitvisual/bitvisual-mcp)

Source: MCP Registry · repository. Synced Nov 17, 2026, 13:17 UTC.

BitVisual MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BitVisual MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BitVisual MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BitVisual MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BitVisual MCP server have?

6 tools: 5 write, 1 read. listar_catalogo, cotar, consultar_prazo, consultar_requisitos_arte, criar_pedido and status_pedido.

Does the BitVisual MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BitVisual MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BitVisual MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.