Koskamo

BitBusca MCP

Um servidor MCP que permite a agentes de IA consultar dados públicos e cadastrais brasileiros, incluindo CPF, CNPJ, veículos, advogados, publicações do DJEN, licitações e imóveis, através de uma API REST com autenticação por chave.

Visit BitBusca

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

BitBusca MCP logo, by BitBuscaVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by BitBusca
MCP endpoint (Streamable HTTP)
https://api.bitbusca.net/api/v1/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to bitbusca.net ·
  • Passed Endpoint is on the registry namespace domain ·
  • Uptime 100% over 90 days
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Consultar ficha de empresa pelo CNPJ
  • Buscar publicações do Diário de Justiça Eletrônico Nacional
  • Obter dados de veículos pela placa
  • Monitorar editais de licitações abertos

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: net.bitbusca/api@1.0.0Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

100% (16 of 16 checks answered)

  1. 2026-11-02: 4 of 4 checks answered
  2. 2026-11-03: 4 of 4 checks answered
  3. 2026-11-04: 4 of 4 checks answered
  4. 2026-11-05: 4 of 4 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
928 ms
95th percentile latency
928 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 928 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http bitbusca-mcp https://api.bitbusca.net/api/v1/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add bitbusca-mcp --url https://api.bitbusca.net/api/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable bitbusca-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "bitbusca-mcp": {
      "url": "https://api.bitbusca.net/api/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "bitbusca-mcp": {
      "type": "streamableHttp",
      "url": "https://api.bitbusca.net/api/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start bitbusca-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "bitbusca-mcp": {
      "type": "http",
      "url": "https://api.bitbusca.net/api/v1/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http bitbusca-mcp https://api.bitbusca.net/api/v1/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.bitbusca.net/api/v1/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "bitbusca-mcp": {
      "serverUrl": "https://api.bitbusca.net/api/v1/mcp"
    }
  }
}

Let your agent find its tools

Find servers like BitBusca MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,835

Do you run BitBusca MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing