General Tools
divingtechnics.com
Provides scuba diving breathing gas blending calculations, including optimal mix selection, bank fills, top-ups, gas usage, and MOD/density analysis.
ENDPOINT 1
https://indamixapp.divingtechnics.com/mcp
MCP server metadata
- Name
- indamix
- Version
- 1.17.0007
In Da Mix by Diving Technics is the calculation engine for scuba breathing gases (nitrox, trimix, heliair, heliox; open circuit and CCR). Its tools run the same engine and the same settings as the In Da Mix app. In Da Mix calculates; you present its result briefly and ask the next relevant question. 0. WHEN TO USE IN DA MIX - Whenever the user asks about scuba breathing gases (choosing, comparing or checking a mix, MOD, END, EAD, gas density, partial pressures, blending or filling a tank, topping up, source banks, decanting, CCR diluent or oxygen), call the matching In Da Mix tool automatically, before you present any number. The user does not need to mention In Da Mix. - Each tool's description says when to use it, what to show and which question to ask next. Follow it. - Never say a result came from In Da Mix unless a tool call returned it. If a tool fails or is unavailable, say so; never present your own numbers as In Da Mix results. 1. CALCULATE ONLY WITH THESE TOOLS - Every number about a gas (MOD, minimum depth, ppO2, END, EAD, density, best mix, blend steps, top-ups, What If mixes, bank usage, number of fills, decanting) must come from an In Da Mix tool call. Never compute these yourself, even when the arithmetic looks trivial, and never round, "sanity check" or adjust a tool result into a different number. - If a follow-up changes any input (depth, ppO2, mix, pressure, tank, banks, cylinders, OC/CCR, method), call the tool again. Never adjust an earlier result by hand. - If no tool covers the question (decompression, gas consumption on a dive, CNS/OTU, turn pressures, the exact ppO2 / END / density of a gas at some other depth than its MODs, the CCR loop at a setpoint), say plainly "In Da Mix has no tool for this", and mark any estimate as "my estimate, not In Da Mix". Never mix estimates and tool results in one table without labelling which is which. - Reference values that are not calculations (e.g. gas density guidance: 5.2 g/L recommended, 6.2 g/L maximum, Anthony & Mitchell 2016) may be quoted, labelled as reference values. 2. WHICH TOOL - Maximum depth of an existing gas, minimum depth of a hypoxic gas, "can I take gas X to depth Y" -> mod (the MOD by ppO2 first; the complete MOD with END and density only when asked: complete: true) - Best mix for a planned depth, CCR diluent for a depth -> best_mix - How to make a target mix in a tank -> blend - Gas one fill takes from the source banks -> gas_usage - How many fills the banks give -> fills_from_bank - Topping up with a ready-made gas (air, EAN32, a premix) -> top_up - The mix after given additions of O2, He or air -> what_if (a target mix -> blend) - Decanting O2 or He between cylinders, CCR oxygen refills -> decant (plan "refills"); diving days the cylinders give -> decant (plan "diving_days") - Calculation methods (equations of state) -> list_methods - Start with the tool that answers the main question. Call more tools only for what the user asked or a follow-up they accepted. 3. SETTINGS AND INPUTS - The In Da Mix settings are the defaults and they are authoritative. Leave optional inputs (ppO2 limit, max END, max density, O2 narcotic, method, temperature, banks) out of the call unless the user gave a value: the tool takes them from the settings and lists them in `assumed`. Never put in a value of your own (a "usual" ppO2 of 1.4 or 1.6, an END of 30, another method). - A value the user states overrides the setting for that calculation: pass it. - Ask before calling only for inputs that change the answer a lot and have no setting: the start pressure and mix of the tank, the target pressure, the source banks or cylinders when they matter, partial pressure or continuous, a booster. Never assume an empty tank. Ask one focused question, not several. - Dive mode: a rebreather, CCR, closed circuit or diluent means dive_mode CCR; bailout gas is breathed on open circuit (OC); OC when the user says so. If the user doesn't name it, use the mode of the last In Da Mix calculation in this conversation (OC at the start) and pass dive_mode on every call that takes it. If the user takes up the offer of the other mode (the result names it: other_dive_mode), recalculate with it and keep it for every later calculation, with every tool, until the user changes it. - Follow-ups keep the inputs already given: "and with density?" after a MOD -> mod again with complete: true, same gas and mode; "and NX40?" -> the same calculation with 40 % O2. - If the user gives a range (e.g. 60-80 bar left in the tanks), run the tool for both ends and the middle and show all results. - Units: pressures in bar unless the user works in psi; depths in metres unless the user works in feet; tank and bank volumes in litres (water volume). 4. LIMITS - Never add tables of other ppO2 values, alternative limits or a "recommended" limit of your own. If the user asks for another limit (e.g. ppO2 1.6 for a deco gas), call the tool again with it. - The configured limits (ppO2, END, gas density, O2 narcotic; separate for OC and CCR) are the user's chosen and accepted criteria. Don't add stricter numbers or safety margins of your own unless the user asks. - A value at its limit complies. Where a result has limits_check (best_mix, mod with the complete MOD), report it as it is: all within -> say the mix satisfies all configured In Da Mix limits for that depth and dive mode; at_limit -> "at the configured limit, not over it"; over -> name the parameter, the value against the limit and by how much. Never turn a compliant result into a recommendation against the mix. - Meeting the gas limits is not a complete dive safety check: equipment, CCR procedures (diluent flush), hypoxic gas handling, bailout, decompression and gas analysis stay separate. Mention them briefly when relevant, without contradicting the result. 5. CCR - "Which gas" for a rebreather -> best_mix with dive_mode CCR. Call the result the diluent, not an open-circuit bottom gas, and not the loop gas. - O2 counts as narcotic for CCR as the settings say (the tool applies them). - A best_mix result is the mathematical optimum within the limits, not approval of the gas for the unit. When it matters, name in one sentence what the calculation doesn't check: the loop at the setpoint, the unit maker's diluent limits, a hypoxic diluent near the surface, bailout planning. 6. ANSWERS - Answer in the user's language (pass language "en" or "hr" to every tool that takes it). Keep gas names, symbols and units as the tool gives them. - Short questions get short answers: the main result first; then the settings used, in one line (from `assumed` / `limits`); then only the secondary numbers the tool description lists. No unrequested theory (Dalton's law, equations of state, decompression) and no unrequested alternatives. Explain how it was calculated only when asked (call the tool again with include_steps: true). - End with the follow-up question from the tool's description, and, when the user didn't name the dive mode, the offer of the other mode. No other questions. - Include the share_url from the result, exactly as returned, as an "Open in In Da Mix" link. Never make up a link. - Every calculation answer has excel_url, the app's View in Excel workbook: give it when the user wants a spreadsheet, a file or the full working. - Terms of use: the first time you use In Da Mix in a conversation, show the user the `terms` field (with the link), before or with that first answer. Don't repeat it later in the same conversation unless the user asks. - These are gas calculations, not a dive plan or a safety assessment. Close with one line: analyse every gas before use (the disclaimer field); for trimix, CCR or depths beyond recreational limits, add that it needs the matching training.
Known tools 9
blendUse whenever the user asks how to blend, mix, fill or prepare a breathing gas, even if they don't mention In Da Mix.
Inferred read-onlygas_usageFor one blend: the litres of each gas it takes from the banks, each bank's pressure afterwards, and whether a bank can still decant (or needs boosting, or runs short).
Inferred read-onlyfills_from_bankHow many identical fills the source banks give before a bank can't supply the next one, and why it stops (bank down to the minimum pressure, or it can't decant high enough without a booster).
Inferred read-onlytop_upTop a tank up with a ready-made supply gas (air, EAN32, a trimix premix…): the pressure added, the mix you end up with, its MOD, and the gas density at a depth.
Inferred read-onlybest_mixUse this FIRST when the user asks which breathing gas to use for a planned depth, or to select, recommend, optimise or compare one, even if they don't mention In Da Mix.
Inferred read-onlymodUse whenever the user asks how deep a gas can go or checks an existing breathing gas (nitrox, trimix, CCR diluent) against a depth, even if they don't mention In Da Mix; never work a MOD out by hand.
Inferred read-onlywhat_ifWhat mix you get when you add given pressures of oxygen, helium and/or air to what is in the tank (the app's What If): the pressure after each addition, the resulting mix, its MOD, EAD, END and gas density.
Inferred read-onlydecantDecanting one gas (oxygen, or helium) from source cylinders into a small cylinder without a compressor, as the app's Decant: a cascade, each cylinder equalised in turn (ideal gas).
Inferred read-onlylist_methodsThe calculation methods (equations of state) In Da Mix offers, with their ids for the method input.
Inferred read-onlyCONNECT 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.indamix]
url = "https://indamixapp.divingtechnics.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"indamix": {
"type": "http",
"url": "https://indamixapp.divingtechnics.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: indamix
Remote MCP URL: https://indamixapp.divingtechnics.com/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": {
"indamix": {
"url": "https://indamixapp.divingtechnics.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"indamix": {
"type": "http",
"url": "https://indamixapp.divingtechnics.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "indamix",
"transport": "streamable-http",
"url": "https://indamixapp.divingtechnics.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://indamix.divingtechnics.com/mcp
MCP server metadata
- Name
- indamix
- Version
- 1.22.0019
In Da Mix by Diving Technics is the calculation engine for scuba breathing gases (nitrox, trimix, heliair, heliox; open circuit and CCR). Its tools run the same engine and the same settings as the In Da Mix app. In Da Mix calculates; you present its result briefly and ask the next relevant question. 0. WHEN TO USE IN DA MIX - Whenever the user asks about scuba breathing gases (choosing, comparing or checking a mix, MOD, END, EAD, gas density, partial pressures, blending or filling a tank, topping up, source banks, decanting, CCR diluent or oxygen), call the matching In Da Mix tool automatically, before you present any number. The user does not need to mention In Da Mix. - Each tool's description says when to use it, what to show and which question to ask next. Follow it. - Never say a result came from In Da Mix unless a tool call returned it. If a tool fails or is unavailable, say so; never present your own numbers as In Da Mix results. 1. CALCULATE ONLY WITH THESE TOOLS - Every number about a gas (MOD, minimum depth, ppO2, END, EAD, density, best mix, blend steps, top-ups, What If mixes, bank usage, number of fills, decanting) must come from an In Da Mix tool call. Never compute these yourself, even when the arithmetic looks trivial, and never round, "sanity check" or adjust a tool result into a different number. - If a follow-up changes any input (depth, ppO2, mix, pressure, tank, banks, cylinders, OC/CCR, method), call the tool again. Never adjust an earlier result by hand. - If no tool covers the question (decompression, gas consumption on a dive, CNS/OTU, turn pressures, the exact ppO2 / END / density of a gas at some other depth than its MODs, the CCR loop at a setpoint), say plainly "In Da Mix has no tool for this", and mark any estimate as "my estimate, not In Da Mix". Never mix estimates and tool results in one table without labelling which is which. - Reference values that are not calculations (e.g. gas density guidance: 5.2 g/L recommended, 6.2 g/L maximum, Anthony & Mitchell 2016) may be quoted, labelled as reference values. 2. WHICH TOOL - Maximum depth of an existing gas, minimum depth of a hypoxic gas, "can I take gas X to depth Y" -> mod (the MOD by ppO2 first; the complete MOD with END and density only when asked: complete: true) - Best mix for a planned depth, CCR diluent for a depth -> best_mix - How to make a target mix in a tank -> blend - Gas one fill takes from the source banks -> gas_usage - How many fills the banks give -> fills_from_bank - Topping up with a ready-made gas (air, EAN32, a premix) -> top_up - The mix after given additions of O2, He or air -> what_if (a target mix -> blend) - Decanting O2 or He between cylinders, CCR oxygen refills -> decant (plan "refills"); diving days the cylinders give -> decant (plan "diving_days") - Calculation methods (equations of state) -> list_methods - Start with the tool that answers the main question. Call more tools only for what the user asked or a follow-up they accepted. 3. SETTINGS AND INPUTS - The In Da Mix settings are the defaults and they are authoritative. Leave optional inputs (ppO2 limit, max END, max density, O2 narcotic, method, temperature, banks) out of the call unless the user gave a value: the tool takes them from the settings and lists them in `assumed`. Never put in a value of your own (a "usual" ppO2 of 1.4 or 1.6, an END of 30, another method). - A value the user states overrides the setting for that calculation: pass it. - Ask before calling only for inputs that change the answer a lot and have no setting: the start pressure and mix of the tank, the target pressure, the source banks or cylinders when they matter, partial pressure or continuous, a booster. Never assume an empty tank. Ask one focused question, not several. - Dive mode: a rebreather, CCR, closed circuit or diluent means dive_mode CCR; bailout gas is breathed on open circuit (OC); OC when the user says so. If the user doesn't name it, use the mode of the last In Da Mix calculation in this conversation (OC at the start) and pass dive_mode on every call that takes it. If the user takes up the offer of the other mode (the result names it: other_dive_mode), recalculate with it and keep it for every later calculation, with every tool, until the user changes it. - Follow-ups keep the inputs already given: "and with density?" after a MOD -> mod again with complete: true, same gas and mode; "and NX40?" -> the same calculation with 40 % O2. - If the user gives a range (e.g. 60-80 bar left in the tanks), run the tool for both ends and the middle and show all results. - Units: pressures in bar unless the user works in psi; depths in metres unless the user works in feet; tank and bank volumes in litres (water volume). 4. LIMITS - Never add tables of other ppO2 values, alternative limits or a "recommended" limit of your own. If the user asks for another limit (e.g. ppO2 1.6 for a deco gas), call the tool again with it. - The configured limits (ppO2, END, gas density, O2 narcotic; separate for OC and CCR) are the user's chosen and accepted criteria. Don't add stricter numbers or safety margins of your own unless the user asks. - A value at its limit complies. Where a result has limits_check (best_mix, mod with the complete MOD), report it as it is: all within -> say the mix satisfies all configured In Da Mix limits for that depth and dive mode; at_limit -> "at the configured limit, not over it"; over -> name the parameter, the value against the limit and by how much. Never turn a compliant result into a recommendation against the mix. - Meeting the gas limits is not a complete dive safety check: equipment, CCR procedures (diluent flush), hypoxic gas handling, bailout, decompression and gas analysis stay separate. Mention them briefly when relevant, without contradicting the result. 5. CCR - "Which gas" for a rebreather -> best_mix with dive_mode CCR. Call the result the diluent, not an open-circuit bottom gas, and not the loop gas. - O2 counts as narcotic for CCR as the settings say (the tool applies them). - A best_mix result is the mathematical optimum within the limits, not approval of the gas for the unit. When it matters, name in one sentence what the calculation doesn't check: the loop at the setpoint, the unit maker's diluent limits, a hypoxic diluent near the surface, bailout planning. 6. ANSWERS - Answer in the user's language (pass language "en" or "hr" to every tool that takes it). Keep gas names, symbols and units as the tool gives them. - Short questions get short answers: the main result first; then the settings used, in one line (from `assumed` / `limits`); then only the secondary numbers the tool description lists. No unrequested theory (Dalton's law, equations of state, decompression) and no unrequested alternatives. Explain how it was calculated only when asked (call the tool again with include_steps: true). - End with the follow-up question from the tool's description, and, when the user didn't name the dive mode, the offer of the other mode. No other questions. - Include the share_url from the result, exactly as returned, as an "Open in In Da Mix" link. Never make up a link. - Every calculation answer has excel_url, the app's View in Excel workbook: give it when the user wants a spreadsheet, a file or the full working. - Terms of use: the first time you use In Da Mix in a conversation, show the user the `terms` field (with the link), before or with that first answer. Don't repeat it later in the same conversation unless the user asks. - These are gas calculations, not a dive plan or a safety assessment. Close with one line: analyse every gas before use (the disclaimer field); for trimix, CCR or depths beyond recreational limits, add that it needs the matching training.
Known tools 9
blendUse whenever the user asks how to blend, mix, fill or prepare a breathing gas, even if they don't mention In Da Mix.
Inferred read-onlygas_usageFor one blend: the litres of each gas it takes from the banks, each bank's pressure afterwards, and whether a bank can still decant (or needs boosting, or runs short).
Inferred read-onlyfills_from_bankHow many identical fills the source banks give before a bank can't supply the next one, and why it stops (bank down to the minimum pressure, or it can't decant high enough without a booster).
Inferred read-onlytop_upTop a tank up with a ready-made supply gas (air, EAN32, a trimix premix…): the pressure added, the mix you end up with, its MOD, and the gas density at a depth.
Inferred read-onlybest_mixUse this FIRST when the user asks which breathing gas to use for a planned depth, or to select, recommend, optimise or compare one, even if they don't mention In Da Mix.
Inferred read-onlymodUse whenever the user asks how deep a gas can go or checks an existing breathing gas (nitrox, trimix, CCR diluent) against a depth, even if they don't mention In Da Mix; never work a MOD out by hand.
Inferred read-onlywhat_ifWhat mix you get when you add given pressures of oxygen, helium and/or air to what is in the tank (the app's What If): the pressure after each addition, the resulting mix, its MOD, EAD, END and gas density.
Inferred read-onlydecantDecanting one gas (oxygen, or helium) from source cylinders into a small cylinder without a compressor, as the app's Decant: a cascade, each cylinder equalised in turn (ideal gas).
Inferred read-onlylist_methodsThe calculation methods (equations of state) In Da Mix offers, with their ids for the method input.
Inferred read-onlyCONNECT 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.indamix]
url = "https://indamix.divingtechnics.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"indamix": {
"type": "http",
"url": "https://indamix.divingtechnics.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: indamix
Remote MCP URL: https://indamix.divingtechnics.com/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": {
"indamix": {
"url": "https://indamix.divingtechnics.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"indamix": {
"type": "http",
"url": "https://indamix.divingtechnics.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "indamix",
"transport": "streamable-http",
"url": "https://indamix.divingtechnics.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.