mcp-registry/com.djfindr/djfindr · v1.7.1
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 16:42 UTC, the DJfindr MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Find and book DJs by occasion, location, date and budget; read profiles, mixes and reviews.
Point your MCP client at this streamable-http endpoint: https://mcp.djfindr.com/mcp
141 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
170 parameter(s) across 107 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
28 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~23,273 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 107 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.djfindr%2Fdjfindr/fixes
{
"name": "accept_extension",
"description": "Accept an extension. Needs `bookings:write`. Two calls. The first changes nothing: it checks the arguments as the change would (a field this tool does not take is refused, by name) and answers a summary and a confirm_token. Show the summary to the person; only after they agree, call again with the same arguments plus confirm_token.",
"inputSchema": {
"type": "object",
"required": [
"proposal_id",
"extension_id",
"rate_amount"
],
"properties": {
"proposal_id": {
"type": "string",
"minLength": 1
},
"rate_amount": {
"type": "string"
},
"extension_id": {
"type": "string",
"minLength": 1
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call. On the second call, the confirm_token the first call answered."
}
},
"additionalProperties": true
},
"annotations": {
"title": "Accept an extension",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
},
"title": "Accept an extension"
}{
"name": "add_widget_domain",
"description": "Allow a domain for my widgets. Needs `content:write`. Two calls. The first changes nothing: it checks the arguments as the change would (a field this tool does not take is refused, by name) and answers a summary and a confirm_token. Show the summary to the person; only after they agree, call again with the same arguments plus confirm_token.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string"
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call. On the second call, the confirm_token the first call answered."
}
},
"additionalProperties": true
},
"annotations": {
"title": "Allow a domain for my widgets",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
},
"title": "Allow a domain for my widgets"
}{
"name": "change_handle",
"description": "Change my handle. Needs `profile:write`. Two calls. The first changes nothing: it checks the arguments as the change would (a field this tool does not take is refused, by name) and answers a summary and a confirm_token. Show the summary to the person; only after they agree, call again with the same arguments plus confirm_token.",
"inputSchema": {
"type": "object",
"required": [
"handle"
],
"properties": {
"handle": {
"type": "string"
},
"confirm_token": {
"type": "string",
"description": "Leave out on the first call. On the second call, the confirm_token the first call answered."
}
},
"additionalProperties": true
},
"annotations": {
"title": "Change my handle",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": true
},
"title": "Change my handle"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.djfindr/djfindr"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.djfindr/djfindr"}) over MCP.
edit_offer ~826 tokenssearch_djs ~541 tokensrequest_booking ~442 tokensadd_document ~412 tokenspreview_booking_request ~359 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fcom.djfindr%2Fdjfindr?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.djfindr%2Fdjfindr?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.djfindr%2Fdjfindr.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:82927866606f14a3…, first seen 2026-11-15, included at leaf 279448 of 384,639. Version history · verify what your client received.
Compare: most reliable files servers · most reliable communication servers · most reliable productivity servers · most reliable other servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 16:42 UTC, the DJfindr MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
DJfindr MCP server advertises 141 tools, including abort_multipart_upload, accept_extension, accept_request, add_document, add_widget_domain.
Point your MCP client at this streamable-http endpoint: https://mcp.djfindr.com/mcp
Glimind scanned all 141 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.