mcp-registry/io.github.dynamitecircle/dc · v2.4.3
As of 2026-10-22 19:31 UTC, the Dynamitecircle Dc MCP server is up (it requires sign-in) with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 1 minutes.
Read and act on your own Dynamite Circle membership data via the public DC Member API.
Claude Code
claude mcp add --transport http dynamitecircle-dc-mcp-server https://api.dynamitecircle.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"dynamitecircle-dc-mcp-server": {
"type": "http",
"url": "https://api.dynamitecircle.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: profile_update, ~1,629).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,029 tokens every session. How to fix →
85 of 85 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
85 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 →
30 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~19,205 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 →
Handshake + tools/list takes ~1,952 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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 →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.dynamitecircle%2Fdc/fixes
{
"name": "alerts_by_id_delete",
"description": "DELETE /alerts/:alertID — Deactivate an alert\n\nSoft-delete an alert by setting `active: false`. The alert's history is preserved for past digests. Use `PATCH /alerts/:alertID` with `active: true` to reactivate.\n\n⚠️ WRITE operation: this mutates your DC account data.",
"inputSchema": {
"type": "object",
"required": [
"alertID"
],
"properties": {
"alertID": {
"type": "string",
"description": "The alert ID to delete"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "alerts_by_id_update",
"description": "PATCH /alerts/:alertID — Update an alert\n\nUpdate one or more fields on an existing alert. Only provide the fields you want to change.\n\n⚠️ WRITE operation: this mutates your DC account data.",
"inputSchema": {
"type": "object",
"required": [
"alertID"
],
"properties": {
"name": {
"type": "string",
"description": "New alert name"
},
"active": {
"type": "boolean",
"description": "Whether the alert is active"
},
"alertID": {
"type": "string",
"description": "The alert ID to update"
},
"description": {
"type": "string",
"description": "New alert description"
},
"notifyDaily": {
"type": "boolean",
"description": "Whether daily digests are enabled"
},
"notifyWeekly": {
"type": "boolean",
"description": "Whether weekly digests are enabled"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": true
}
}{
"name": "alerts_create",
"description": "POST /alerts — Create an alert\n\nCreate a new alert. The system will search for matching content and deliver digests on the configured frequency. Maximum 10 active alerts per user.\n\n⚠️ WRITE operation: this mutates your DC account data.",
"inputSchema": {
"type": "object",
"required": [
"description",
"notifyDaily",
"notifyWeekly"
],
"properties": {
"description": {
"type": "string",
"description": "Alert description — what the alert should look for (max 500 chars)"
},
"notifyDaily": {
"type": "boolean",
"description": "Whether daily digests are enabled"
},
"notifyWeekly": {
"type": "boolean",
"description": "Whether weekly digests are enabled"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/io.github.dynamitecircle/dc"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.dynamitecircle/dc"}) over MCP.
profile_update ~1,629 tokensprofile_match_create ~1,033 tokenstrips_create ~432 tokenstrip_update ~380 tokenssearch_events ~365 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. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.dynamitecircle%2Fdc?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.dynamitecircle%2Fdc?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dynamitecircle%2Fdc.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dynamitecircle%2Fdc.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.dynamitecircle%2Fdc?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ec2a0433dba9bb36…, first seen 2026-10-17, included at leaf 4286 of 47,709. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable calendar servers · most reliable retrieval servers · most reliable data servers · most reliable event 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
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 19:31 UTC, the Dynamitecircle Dc MCP server is up (it requires sign-in) with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 1 minutes.
Dynamitecircle Dc MCP server advertises 87 tools, including alerts, alerts_by_id_delete, alerts_by_id_update, alerts_create, announcements.
Point your MCP client at this streamable-http endpoint: https://api.dynamitecircle.com/mcp
Glimind scanned all 85 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.