Conarium
What it does
Governed database access for AI assistants: masking, signed receipts, coverage reconciliation.
- Connects Runs on your computer
- Account or key No key needed
- Category Databases & datasets
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Install Node.js
One time only; it works for every server that needs Node.js
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "conarium": { "command": "npx", "args": [ "-y", "@conarium-ai/core" ] } } }Quit Claude and open it again
Try it
Use Conarium and tell me what you can do for me, then show me one thing✓ If Claude says it is using Conarium or shows a Conarium tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Conarium yet
Conarium runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Conarium
- Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
B · Others in Databases & datasets that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Supabase✓ ChatGPT
- Appwrite MCP✓ ChatGPT
- Pg Aiguide✓ ChatGPT
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user conarium -- npx -y @conarium-ai/coreType /mcp in Claude Code
You should see Conarium listed as connected
Try it
Use Conarium and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Conarium or shows a Conarium tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open the AI chat in Cursor in Agent mode
Try it
Use Conarium and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Conarium or shows a Conarium tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Install Node.js
One time only; it works for every server that needs Node.js
Open the AI chat in VS Code in Agent mode
Try it
Use Conarium and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Conarium or shows a Conarium tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user conarium -- npx -y @conarium-ai/coreClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"conarium": {
"command": "npx",
"args": [
"-y",
"@conarium-ai/core"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"conarium": {
"command": "npx",
"args": [
"-y",
"@conarium-ai/core"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"conarium": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@conarium-ai/core"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- 261/wk
- Connection
- Runs on your computer
- Latest versioni
- 0.3.6
- Categoryi
- Databases & datasets
- Published to registryi
- Nov 2, 2026
- Code last changedi
- Nov 12, 2026
- Maker
- dogrucanemek-alt
- Packages
npm: @conarium-ai/core- Website
- conarium.dev
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dogrucanemek-alt, which owns the repo
- ✓ Pass
Still maintained
Code last changed yesterday
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Databases & datasetsi
- More stars than 86% of the other 1178 servers in this category
- Published to the registry more recently than 80% of the other 1178 servers in this category
- Basic checks equal to or better than 100% of the other 1178 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Conarium safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed yesterday, and the latest version (0.3.6) reached the registry 11 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Dbx, MCP Toolbox for Databases, MCP Toolbox for Databases
Others in the same category
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Conarium The Third Eye for Your Company's Data. Part of VERAX , by VERAX Teknoloji. Start with the VERAX body: verax-ai/verax . Sister projects: Tugra · Cedulon . Listed on: npm · Glama · MCP Registry · MCP Market · LobeHub · Zenodo
A self-hosted, governed gateway that lets AI coding assistants (Cursor, Copilot, Claude) touch your real data under a policy you write—protected values masked before they leave. When a receipt sink is configured it writes a signed, independently verifiable receipt of every access it mediates; conarium-init sets that sink, so the default layout does.
The site lives at conarium.dev; this repository is the product.
Check it before you read the rest
Nothing below has to be taken on trust. There is a live receipt chain; verify it against its public key on your own machine, with no account and no data of yours:
npm i @conarium-ai/core
curl -fsS https://conarium.dev/proof/chain.jsonl -o chain.jsonl curl -fsS https://conarium.dev/proof/key.pem -o key.pem curl -fsS https://conarium.dev/proof/key.pem.keyid -o key.pem.keyid npx conarium-verify chain.jsonl --pubkey key.pem
note: tail truncation is not visible — this run did not see receipts deleted from the end of the file. Pin with --expect-count, --expect-last-hash, or --anchor-check. ok: 3 receipt(s) verified (3 with undeclared model, 3 with undeclared client)
Exit code 0. The three receipts are one ordinary read, one where five email addresses and a card number were masked before the model saw them, and one refusal. Change any field and the recomputed hash stops matching the stored one — exit 10. Change the signature instead — exit 13.
The verifier is a single file that imports nothing from the package it is checking, so a compromised Conarium cannot talk it into a passing result. Note that it volunteers what it did *not* check, in the first line of its own output, before the good news.
Limitations
What this repository has not done is in LIMITATIONS.md (Türkçe). The dated comparison page is conarium.dev/compare.html — that is the only copy; this repo does not keep a second one.
Standards
draft-dogru-scitt-disclosure-evidence is an individual submission. Not adopted by an IETF working group, and it carries no formal standing — an Internet-Draft is a dated public record, not a standard. It is published so the receipt format can be implemented without us. Source files live in standards/.
👁️ The Problem
Point Cursor or Copilot at a production database and it drinks the raw stream—SSNs, credit cards, salaries, and live keys. One rogue prompt can expose your most sensitive tables. Security teams simply can't allow that.
🛡️ The Solution: Conarium
Conarium acts as a high-performance MCP (Model Context Protocol) Proxy. It sits directly between the AI Assistant and your databases, evaluating policies in milliseconds to enforce row limits and mask PII (Personally Identifiable Information) on the wire.
The AI gets the context it needs to write code; the values your policy protects are masked before they reach it. Masking hides a value — it does not make it unlearnable, and where a request language allows predicates over a protected column, an allowed query can still answer questions about one. protectedColumns is the narrower answer to that, and the limit is stated in LIMITATIONS.md rather than left for you to discover.
Key Features
- Inline PII Masking: Emails, IDs, cards, and secrets are redacted in the response stream (
[MASKED_PII]/[MASKED_SECRET]) before the model sees a single character. - Allow / Deny Lists: Whitelist what AI can access. Your
secretsandfinancialstables stay invisible. - Row Caps: Hard per-query limits. Prevent the silent exfiltration of millions of rows.
- Tamper-Evident Audit Ledger: Every access *through Conarium* is logged (who, what, when, rows, decision). Hash-chained, which makes alteration and mid-chain removal detectable — not impossible: a file on disk can still be deleted or truncated, and catching truncation needs a pin from outside the file (see Coverage & Reconciliation below). PII-safe: no raw PII is written to the logs.
- Verifiable Receipts: Ed25519-signed, independently verifiable receipts — see below.
- Per-person masking profiles: what to mask for an AI agent is not what to mask for the data controller. A named profile relaxes masking for one identified person, and the receipt records which profile applied — see below.
- Coverage & Reconciliation: a signed coverage declaration over the receipt chain (
conarium-coverage), plus two-sided reconciliation against the database's own query counters (conarium-reconcile) — DB-recorded activity that no receipt covers is surfaced instead of staying invisible. - 100% Self-Hosted: Runs entirely on your infrastructure. Nothing we ship transmits your data anywhere: raw protected values stay inside your perimeter, and what reaches your AI client is the policy-approved disclosure — whose exact bytes the receipt records (
disclosure.hash). Saying your data never leaves at all would be the wrong claim: releasing a governed disclosure to an assistant is the job. The gateway makes exactly one outbound request that is not yours: at startup it asks the public npm registry whether a newer version exists, and prints one line to stderr if so. It sends nothing about you — no identifier, no config, no counts — and a remote gateway nobody looks at for weeks is the reason it exists at all. Disable it withCONARIUM_NO_UPDATE_CHECK=1, or point it at your internal mirror withCONARIUM_NPM_REGISTRY. It has a 2-second timeout and never blocks or fails startup. We list it here because a governance product that makes an undisclosed outbound connection has already lost the argument. - MCP-Native: Works out of the box with Cursor, GitHub Copilot, Claude Code, and Codex.
Verifiable Receipts
Conarium can emit portable receipts (Art. 12 / 19 shaped) that a third party verifies offline with a single file — no Conarium install required.
Official claim (do not widen): A Conarium Receipt proves that the records still in the file have not been altered, reordered, or backdated after they were created, and that none were removed from the middle of the chain (prevHash / seq). It does not prove they were correct at the moment of creation. It also cannot, by itself, prove that records were not dropped from the end: a shorter leftover chain is still internally consistent. Catching tail truncation needs a pin from outside the file — --expect-count, --expect-last-hash, an OpenTimestamps anchor, or conarium-reconcile against the database's own counters.
*(TR)* Conarium Makbuzu, dosyada hâlâ duran kayıtların oluşturulduktan sonra değiştirilmediğini, ortadan silinmediğini, yeniden sıralanmadığını ve geriye dönük tarihlenmediğini kanıtlar. Oluşturma anında doğru olduğunu kanıtlamaz. Sondan kesmeyi tek başına göremez: kalan zincir tutarlıdır, yalnızca kısadır. *(/TR)*
# Generate an Ed25519 keypair (private PEM + .pub.pem + .keyid sidecars).
The .keyid sidecars are not optional: without them the verifier answers 13
for every receipt, which reads like tampering and is not.
npx conarium-init
export CONARIUM_AUDIT_SIGNING_KEY=./audit-ed25519.pem
init writes keys and config, not receipts: your own audit file does not exist
until the gateway has served a query. The three commands below therefore run
against the demo chain downloaded above, so they work as written — swap in
your own sink (conarium.config.json → audit.sink) once it has records.
Verify a receipt chain (exit 0 = the records *in the file* are intact)
npx conarium-verify chain.jsonl --pubkey key.pem
Pin length / last hash if you need to catch records dropped from the end
npx conarium-verify chain.jsonl --pubkey key.pem --expect-count 3
Check the OpenTimestamps sidecar. The demo chain ships without one, so this
answers 14, deliberately not 0: an absent anchor is not a verified anchor.
A sidecar that exists but is not yet confirmed → exit 0 with a warning.
npx conarium-verify chain.jsonl --pubkey key.pem --anchor-check
A second verifier, Go and the standard library only, is in verifiers/go. go build -o conarium-verify . then the same arguments as conarium-verify; test-vectors/ is the contract.
Anchoring is a separate step. Stamp a document with npx conarium-stamp , or submit a chain-head hash with npx conarium-anchor-service. CONARIUM_ANCHOR_SINK=opentimestamps selects the in-tree calendar client those tools use; it does not stamp receipts as they are written. Upgrade pending proofs later with npx conarium-anchor-upgrade ./audit.jsonl.anchors.jsonl. The client is in-tree (Node crypto + calendar HTTPS). It does not install javascript-opentimestamps. See LIMITATIONS.md.
Per-person masking profiles
Masking that is correct for an AI agent is wrong for the person who owns the data. The owner asking *"which customer owes the most"* needs the name; the assistant summarising revenue does not. Answering that with a global on/off switch would disable the product's only real guarantee, so masking resolves per person:
{
"policy": { "allowTables": ["zion.customers", "zion.orders"], "maskColumns": ["*.customer_name", "*.email", "*.phone"], // default: everyone "maxRows": 100,
"profiles": { // The controller sees customer names; e