# io.github.mrfentmen/deepgram-mcp (npm · deepgram-mcp)

Query the Deepgram API: projects, project balances, and API keys.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- npm · `deepgram-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-deepgram-mcp/deepgram-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-deepgram-mcp/deepgram-mcp)

## Channel facts

- Registry: `npm`
- Package: `deepgram-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 13/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it.
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 64 tokens (~21/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.mrfentmen/deepgram-mcp server?

io.github.mrfentmen/deepgram-mcp runs locally as an npm package, launched with npx -y deepgram-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mrfentmen-deepgram-mcp -- npx -y deepgram-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-deepgram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "deepgram-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-deepgram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "deepgram-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-deepgram-mcp -- npx -y deepgram-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrfentmen-deepgram-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "deepgram-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrfentmen-deepgram-mcp --command npx --arg -y --arg deepgram-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-deepgram-mcp:
    command: "npx"
    args: ["-y", "deepgram-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-deepgram-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "deepgram-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-deepgram-mcp -t stdio -c npx -a -y deepgram-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-deepgram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "deepgram-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 61, +15)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-10-17 (score 46)

First indexed and scored.

## MCP tools (3)

### `list_projects` (~16 tokens)

List projects

Deepgram projects with IDs and names.

### `get_balance` (~24 tokens)

Project balance

Credit balances of a project.

Input parameters:

- `project_id` (string, required): Project UUID.

### `list_keys` (~24 tokens)

List API keys

API keys of a project.

Input parameters:

- `project_id` (string, required): Project UUID.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-deepgram-mcp/deepgram-mcp#diagnostics

## Score history

- 2026-10-23: 64
- 2026-10-22: 63
- 2026-10-21: 63
- 2026-10-20: 62
- 2026-10-19: 62
- 2026-10-18: 61
- 2026-10-17: 46

## Common questions

### What is the io.github.mrfentmen/deepgram-mcp server?

io.github.mrfentmen/deepgram-mcp is listed in the public MCP registry as io.github.mrfentmen/deepgram-mcp. Query the Deepgram API: projects, project balances, and API keys. This page covers its npm package (deepgram-mcp).

### Is the io.github.mrfentmen/deepgram-mcp server safe to use?

io.github.mrfentmen/deepgram-mcp scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.mrfentmen/deepgram-mcp server expose?

io.github.mrfentmen/deepgram-mcp exposes 3 tools: list_projects, get_balance, list_keys. Their descriptions and schemas cost roughly 64 tokens of context every time the server is loaded.

### Is the io.github.mrfentmen/deepgram-mcp server still maintained?

io.github.mrfentmen/deepgram-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.mrfentmen/deepgram-mcp server under?

io.github.mrfentmen/deepgram-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/deepgram-mcp
- Socket report: https://socket.dev/npm/package/deepgram-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-deepgram-mcp/deepgram-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-deepgram-mcp/deepgram-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-deepgram-mcp/deepgram-mcp