Developer Tools

dhq-boiler.dev

A debugging tool for AI agents and workflows that integrates with the Model Context Protocol.

1 endpoint5 known toolsFirst detected May 30, 2026Last detected August 28, 2026

ENDPOINT 1

https://jidodebugger.dhq-boiler.dev/mcp

No auth detected

MCP server metadata

Name: JidoDebugger.Web
Version: 1.5.0.0

Capabilities

loggingtools.listChanged

Known tools 5

jidodebugger_feature

[Single-feature deep dive] Explain ONE specific JidoDebugger feature in depth — implementation surface, when to use it, related MCP tools.

Inferred read-only

explain_mcp_concept

[Protocol-level / vendor-neutral] Explain the Model Context Protocol (MCP) itself — what the protocol is, how it differs from a plain REST API, and why it matters for AI agents.

Inferred read-only

jidodebugger_grandfather

[Pre-launch grandfather offer specifically] Explain the early-user offer mechanics: the 500-user free cap, why the cap exists, what happens once it's reached, refresh-token silent auto-renew, and the 20%-off-first-year discount that pre-launch users keep after incorporation.

Inferred read-only

jidodebugger_overview

[Product framing + onboarding] Explain what JidoDebugger is, who it is for, how it fits into the user's existing AI-coding workflow, AND how to get started (sign-up + install + MCP-wire-up steps).

Inferred read-only

jidodebugger_pricing

[Tier comparison] Describe JidoDebugger's pricing tiers (Free pre-launch / Individual post-incorporation / Organization post-incorporation), with what's included and what's roadmap in each.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.jidodebugger-web]
url = "https://jidodebugger.dhq-boiler.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "jidodebugger-web": {
      "type": "http",
      "url": "https://jidodebugger.dhq-boiler.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: jidodebugger-web
Remote MCP URL: https://jidodebugger.dhq-boiler.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "jidodebugger-web": {
      "url": "https://jidodebugger.dhq-boiler.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "jidodebugger-web": {
      "type": "http",
      "url": "https://jidodebugger.dhq-boiler.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "jidodebugger-web",
  "transport": "streamable-http",
  "url": "https://jidodebugger.dhq-boiler.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for dhq-boiler.dev was fetched 2026-07-25T23:06:35.904Z and is being refreshed.

Trust status Trusted

dhq-boiler.dev is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.