Home / MCP registry index / com.besidka/mcp

Besidka

com.besidka/mcp in the official MCP registry. Endpoint https://besidka.com/mcp. Source: github.com/besidka/besidka.

The registry describes it as: Besidka models, providers and key guides, plus your chats, projects, files, memory and settings.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http besidka https://besidka.com/mcp

{
  "mcpServers": {
    "besidka": {
      "url": "https://besidka.com/mcp"
    }
  }
}

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

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.

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

Tools it advertises

add_memory add_project_note add_project_text branch_chat create_file create_project delete_chat_message delete_chats delete_files delete_memory delete_project_knowledge_items delete_project get_chat get_key_guide get_page get_project get_settings list_chats list_files list_memory list_models list_projects list_providers list_shared_chats move_chats_to_project read_file read_project_knowledge_item rename_file reset_memory revoke_chat_shares update_chat update_memory update_project_instructions update_project_knowledge_item update_project update_settings

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-11-04): c9afeeb98f2da870. 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.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-besidka-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-besidka-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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Memory and knowledge MCP servers