Home / MCP registry index / com.djfindr/djfindr
DJfindr
com.djfindr/djfindr in the official MCP registry.
Endpoint https://mcp.djfindr.com/mcp.
The registry describes it as: Find and book DJs by occasion, location, date and budget; read profiles, mixes and reviews.
We read its 141 tools on 2026-11-07. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http djfindr https://mcp.djfindr.com/mcp{
"mcpServers": {
"djfindr": {
"url": "https://mcp.djfindr.com/mcp"
}
}
}code --add-mcp '{"name":"djfindr","type":"http","url":"https://mcp.djfindr.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-pluginsTools it advertises
search_djs get_dj get_dj_content list_reference get_reference list_locations get_location book_dj get_me get_account get_account_billing list_booking_events get_booking_event list_booking_proposals get_booking_proposal get_booking_invitation list_pending_reviews request_booking preview_booking_request reject_offer withdraw_booking request_extension cancel_extension review_booking claim_invitation get_booking_overview list_booking_clients get_booking_client list_booking_reviews get_review_summary get_offer_defaults list_document_templates get_travel_estimate accept_request decline_request edit_offer send_offer set_offer_defaults add_document edit_document remove_document convert_document accept_extension decline_extension create_sourced_booking list_payments get_payment list_received_payments get_received_payment get_payout_summary get_payout_setup list_transfers list_paylinks get_transfer get_paylink create_paylink send_paylink cancel_paylink list_calendar_blocks list_calendar_events and 81 more
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-07):
ea858a598f004258. 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: 
[](https://lazaretto.dev/mcp-registry/com-djfindr-djfindr)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.