Home / MCP registry index / com.bokdaeri/consultation

복대리 · Bokdaeri

com.bokdaeri/consultation in the official MCP registry. Endpoint https://mcp.bokdaeri.com/mcp/agent.

The registry describes it as: Bokdaeri (복대리) connects people with lawyers in South Korea for user-confirmed consultations.

We read its 19 tools on 2026-10-31. 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 consultation https://mcp.bokdaeri.com/mcp/agent

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "consultation": {
      "url": "https://mcp.bokdaeri.com/mcp/agent"
    }
  }
}

VS Code

code --add-mcp '{"name":"consultation","type":"http","url":"https://mcp.bokdaeri.com/mcp/agent"}'

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

get_consultation_service_info prepare_consultation_request continue_consultation_request get_consultation_connection_status submit_consultation_request pause_consultation_preparation cancel_consultation_preparation get_consultation_status get_consultation_change_options prepare_consultation_change get_consultation_change_status discard_consultation_change list_consultation_requests apply_consultation_change revoke_consultation_permission begin_consultation_permission begin_contact_change get_contact_change_status begin_contact_verification

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): 8a9af2d0b63f038b. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

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/com-bokdaeri-consultation/badge.svg)](https://lazaretto.dev/mcp-registry/com-bokdaeri-consultation)

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.