# Rev.ai MCP by usefulapi (remote · rev-ai.usefulapi.io)

Transcribe audio with Rev.ai: submit jobs by URL, read transcripts, summaries and captions.

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

## Components

- remote · `rev-ai.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-rev-ai/rev-ai.md), [page](https://verifymcp.io/servers/io-usefulapi-rev-ai/rev-ai)

## Channel facts

- Endpoint: `https://rev-ai.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-16.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1356 tokens (~169/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Rev.ai MCP by usefulapi server?

Rev.ai MCP by usefulapi is a hosted endpoint at https://rev-ai.usefulapi.io/mcp, so there is nothing to install locally. 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 --transport http io-usefulapi-rev-ai 'https://rev-ai.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-rev-ai": {
      "url": "https://rev-ai.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-rev-ai": {
      "type": "http",
      "url": "https://rev-ai.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-rev-ai]
url = "https://rev-ai.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-rev-ai": {
      "type": "remote",
      "url": "https://rev-ai.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-rev-ai --url 'https://rev-ai.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-rev-ai:
    url: "https://rev-ai.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-rev-ai": {
      "Transport": "http",
      "Url": "https://rev-ai.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-rev-ai -t streamable-http -u 'https://rev-ai.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-rev-ai": {
      "type": "http",
      "url": "https://rev-ai.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-16 (score 64, +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-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (8)

### `revai_get_account` (~43 tokens)

Get account and balance

The Rev.ai account behind the token: email, free, purchased, total and invoiced balance (USD) and whether HIPAA is on. GET /account.

### `revai_list_jobs` (~104 tokens)

List transcription jobs

List transcription jobs from the last 30 days, newest first: id, status (in_progress, transcribed, failed), name, duration, language, failure reason. Page with starting_after = the previous reply's next_starting_after. GET /jobs.

Input parameters:

- `limit` (integer): Jobs per page, 1-100 (default 20).
- `starting_after` (string): Return jobs older than this job id (exclusive), from next_starting_after.

### `revai_get_job` (~76 tokens)

Get job status

One transcription job by id: status (in_progress, transcribed, failed), timestamps, duration, language, failure reason. Poll this until status is transcribed. GET /jobs/{id}.

Input parameters:

- `job_id` (string, required): Rev.ai job id (the `id` from revai_submit_job or revai_list_jobs).

### `revai_submit_job` (~356 tokens)

Submit transcription job

WRITE: start an asynchronous machine transcription job for an audio or video file at a public URL. It uses Rev.ai credit (free credit first). Returns the job with status in_progress; then poll revai_get_job and read the result with revai_get_transcript. Human transcription is not offered. POST /jobs.

Input parameters:

- `delete_after_seconds` (integer): Delete the job and its data this many seconds after it completes.
- `filter_profanity` (boolean): Mask profanity in the transcript.
- `forced_alignment` (boolean): More accurate per-word timestamps (en, fr, it, de, es).
- `language` (string): Spoken language as an ISO 639-1 code (en, en-us, en-gb, es, fr, de, ...). Default en.
- `media_url` (string, required): Direct download URL of the audio or video file. Rev.ai fetches it; it must be reachable without login.
- `metadata` (string): A note stored with the job and returned with it (for example your own reference).
- `remove_disfluencies` (boolean): Drop 'ums' and similar fillers.
- `skip_diarization` (boolean): Do not label speakers.
- `skip_punctuation` (boolean): Return words without punctuation.
- `speaker_channels_count` (integer): Number of audio channels with one speaker each. Billed per channel.
- `speakers_count` (integer): Number of speakers, if known (English, Spanish, French); improves speaker labels.
- `summarization_type` (string): Also create a summary, read later with revai_get_summary.
- `verbatim` (boolean): Keep every false start and disfluency (default true for machine jobs).

### `revai_delete_job` (~76 tokens)

Delete job

WRITE: permanently delete a finished (transcribed or failed) job with its media and transcript. This cannot be undone. A job still in progress cannot be deleted. DELETE /jobs/{id}.

Input parameters:

- `job_id` (string, required): Rev.ai job id (the `id` from revai_submit_job or revai_list_jobs).

### `revai_get_transcript` (~194 tokens)

Get transcript

The transcript of a transcribed job. format=text (default) is plain text with speaker labels and timestamps; format=segments is a list of {speaker, start, end, text} per speaker turn (seconds). Long transcripts are paged: repeat with next_offset until it is null. GET /jobs/{id}/transcript.

Input parameters:

- `format` (string): text (default) or segments.
- `group_channels_by` (string): Multichannel jobs only: how to group words into turns.
- `job_id` (string, required): Rev.ai job id (the `id` from revai_submit_job or revai_list_jobs).
- `max_chars` (integer): Most characters to return in one reply, 1000-20000 (default 15000).
- `offset` (integer): text: character position; segments: segment index. Use the previous reply's next_offset (default 0).

### `revai_get_summary` (~127 tokens)

Get transcript summary

The summary of a transcribed job. It exists only if the job was submitted with summarization_type. Paged by character like revai_get_transcript. GET /jobs/{id}/transcript/summary.

Input parameters:

- `job_id` (string, required): Rev.ai job id (the `id` from revai_submit_job or revai_list_jobs).
- `max_chars` (integer): Most characters to return in one reply, 1000-20000 (default 15000).
- `offset` (integer): Start position from the previous reply's next_offset (default 0).

### `revai_get_captions` (~172 tokens)

Get captions

Captions for a transcribed job as SRT (default) or WebVTT. Long files are paged by character: repeat with next_offset until it is null. For multichannel jobs pass speaker_channel. GET /jobs/{id}/captions.

Input parameters:

- `format` (string): srt (default) or vtt.
- `job_id` (string, required): Rev.ai job id (the `id` from revai_submit_job or revai_list_jobs).
- `max_chars` (integer): Most characters to return in one reply, 1000-20000 (default 15000).
- `offset` (integer): Start position from the previous reply's next_offset (default 0).
- `speaker_channel` (integer): Channel to caption, for jobs submitted with speaker_channels_count.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-rev-ai/rev-ai#diagnostics

## Score history

- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 60

## Common questions

### What is the Rev.ai MCP by usefulapi server?

Rev.ai MCP by usefulapi is listed in the public MCP registry as io.usefulapi/rev-ai. Transcribe audio with Rev.ai: submit jobs by URL, read transcripts, summaries and captions. This page covers its hosted endpoint (https://rev-ai.usefulapi.io/mcp).

### Is the Rev.ai MCP by usefulapi server safe to use?

Rev.ai MCP by usefulapi scores 64 out of 100 on VerifyMCP. 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 Rev.ai MCP by usefulapi server expose?

Rev.ai MCP by usefulapi exposes 8 tools: revai_get_account, revai_list_jobs, revai_get_job, revai_submit_job, revai_delete_job, and 3 more. Their descriptions and schemas cost roughly 1,148 tokens of context every time the server is loaded.

### Does the Rev.ai MCP by usefulapi server require authentication?

Yes. Rev.ai MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Rev.ai MCP by usefulapi server still maintained?

Rev.ai MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://rev-ai.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/rev-ai/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-rev-ai/rev-ai.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-rev-ai/rev-ai.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-rev-ai/rev-ai