IntakeQ MCP
IntakeQ/PracticeQ MCP connector with HIPAA §164.312(b) audit logging on every PHI read/write
The current version, v1.0.1, was published to the official MCP registry on 2026-07-02. It is distributed as @oktopeak/intakeq-mcp on npm, filed under Monitoring & Logs by this index, and declares 7 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using IntakeQ MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“Declared PHI access, logs audit”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-08-17).
Contracts can change after screening, with no version bump. The gate pins IntakeQ MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for IntakeQ MCP](https://mcpindex.ai/server/io-github-oktopeak-intakeq-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-oktopeak-intakeq-mcp">Independent trust record for IntakeQ MCP</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-oktopeak-intakeq-mcp)<a href="https://mcpindex.ai/server/io-github-oktopeak-intakeq-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-oktopeak-intakeq-mcp" alt="mcpindex verdict" height="20" /></a>INTAKEQ_API_KEYIntakeQ API key (optional — prefer the set_api_key tool)
INTAKEQ_API_BASEOverride the default IntakeQ API base URL (https://intakeq.com/api/v1)
MCP_API_KEYBearer token gate on the HTTP /mcp endpoint. Required in http mode unless MCP_ALLOW_NO_AUTH is true
MCP_ALLOW_NO_AUTHSet to true to allow HTTP mode without MCP_API_KEY (local development only)
TRANSPORTTransport mode: stdio (default) or http
MCP_BASE_URLBase URL for HTTP transport (e.g. http://127.0.0.1:3000)
PORTHTTP listen port (default 3000). HTTP transport only.
Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.
Log, query, and edit expenses, budgets, and accounts in Ledgy from any MCP-compatible AI assistant.
Read-only MCP server to inspect an Android device over ADB: hardware, packages, permissions, logs.