Skip to main content
DEMINN
Sign a letter of intent

The agent surface for medical-device quality

Your other agents
call Deminn.

Most AI-for-quality products ship a workspace. Deminn ships a workspace and a regulator-defensible tool surface - every answer signed with a content hash and a source chain an auditor can verify independently.

Mint a tokenRead the security brief →

POST /api/mcp/sdk46 callable toolsspec-compliant MCPbearer auth21 CFR Part 11 e-signatures on writes

Connect in three lines

One endpoint. One auth pattern. Tokens minted from Settings → Integrations; they never leave the wire.

Claude Desktopclaude_desktop_config.json
{
  "mcpServers": {
    "deminn": {
      "url": "https://app.deminn.ai/api/mcp/sdk",
      "headers": {
        "Authorization": "Bearer YOUR_DEMINN_TOKEN"
      }
    }
  }
}
Copilot StudioCustom connector
# Microsoft Copilot Studio - Custom MCP connector
URL:        https://app.deminn.ai/api/mcp/sdk
Auth:       API Key (header)
Header:     Authorization
Value:      Bearer YOUR_DEMINN_TOKEN
cURL / anythingHTTP + Bearer
curl -X POST https://app.deminn.ai/api/mcp/sdk \
  -H "Authorization: Bearer YOUR_DEMINN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call",
        "params": { "name": "draft_510k_submission", "arguments": { ... } } }'

What comes back

Every result carries a ProvenanceEnvelope - hash, chain root, signer, signed timestamp, and a public verify URL.

{
  "data": { /* the tool's structured result */ },
  "provenance": {
    "artifactType":    "capa",
    "artifactRefId":   "CAPA-2025-019",
    "artifactHash":    "7f3c1e5b9a2d…",
    "chainRootHash":   "a4d1c8f2e6b3…",
    "signer":          { "userId": "…", "signedAt": "2026-04-29T16:42Z",
                         "reason": "Quality engineering closure approval" },
    "signatureVersion": 1,
    "verifyUrl":       "https://app.deminn.ai/verify?hash=7f3c1e5b9a2d…"
  }
}

The verify URL is open to anyone - see the auditor view on a sample CAPA. No account required.

What other agents do with Deminn

Four scenarios. Every output citable, every signature human, every action logged in the same Part 11 audit trail your team uses inside Deminn.

  1. A Slack agent triages a complaint

    Your Slack bot watches #quality. A field rep posts a complaint. The bot calls Deminn to draft the triage and decide MDR reportability against Part 803.

    Result. Signed envelope with cited clauses returns to Slack. QE approves with Part 11 e-signature from there.

  2. 510(k) drafting from your internal CDE

    Your design team's private LLM knows the PRD. It calls Deminn to scaffold the 510(k), build the substantial-equivalence table, and link the regulatory citations.

    Result. 12-section submission draft and predicate comparison table - drafted with cited regulations, not invented prose.

  3. External auditor verifies, no Deminn login

    During an FDA inspection the auditor asks where a CAPA claim came from. The audited team pastes the public verify URL.

    Result. Chain root, per-citation drift status, signed timestamp - all visible. No Deminn account.

  4. New FDA guidance hits, Copilot posts the digest

    New guidance publishes overnight. Your Copilot Studio agent calls Deminn the next morning to match it against your portfolio.

    Result. Digest posts in Teams: 4 devices impacted, 7 SOPs need review, links to the specific clauses that changed.

A surface without a substrate is a demo.

A competitor can ship an MCP endpoint in a month. Without the evidence graph, personas, gates, and provenance trail underneath, the tool calls return empty shells. Deminn’s MCP is valuable because the rest of the system is what it exposes - the same drafting loop your team works inside, callable by any other agent in your stack.

Backed by a living FDA citation corpus - browse the regulations Deminn cites.

Plug Deminn into your AI stack.

Founder-led setup. Bearer tokens scoped to your org. No data leaves your tenant.

Sign a letter of intentRequest access →Security & tenancy →