Rev.ai MCP by usefulapi
REMOTE · REV-AI.USEFULAPI.IO
Transcribe audio with Rev.ai: submit jobs by URL, read transcripts, summaries and captions.
Available components
Last scanned (22 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://rev-ai.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rev-ai.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://rev-ai.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://rev-ai.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://rev-ai.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://rev-ai.usefulapi.io/mcp |
| Authorisation server | https://rev-ai.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rev-ai.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/rev-ai/ |
| http (plaintext) | http://rev-ai.usefulapi.io/mcp | Inconclusive | 302 | http://rev-ai.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
revai_delete_job Delete job ~76
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Rev.ai job id (the `id` from revai_submit_job or revai_list_jobs). |
No output schema declared.
No examples provided.
revai_get_account Get account and balance ~43
The Rev.ai account behind the token: email, free, purchased, total and invoiced balance (USD) and whether HIPAA is on. GET /account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revai_get_captions Get captions ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | srt (default) or vtt. |
| job_id | string | yes | 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. |
No output schema declared.
No examples provided.
revai_get_job Get job status ~76
One transcription job by id: status (in_progress, transcribed, failed), timestamps, duration, language, failure reason. Poll this until status is transcribed. GET /jobs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Rev.ai job id (the `id` from revai_submit_job or revai_list_jobs). |
No output schema declared.
No examples provided.
revai_get_summary Get transcript summary ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | 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). |
No output schema declared.
No examples provided.
revai_get_transcript Get transcript ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | text (default) or segments. |
| group_channels_by | string | – | Multichannel jobs only: how to group words into turns. |
| job_id | string | yes | 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). |
No output schema declared.
No examples provided.
revai_list_jobs List transcription jobs ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Jobs per page, 1-100 (default 20). |
| starting_after | string | – | Return jobs older than this job id (exclusive), from next_starting_after. |
No output schema declared.
No examples provided.
revai_submit_job Submit transcription job ~356
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
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.
remote · rev-ai.usefulapi.io
claude mcp add --transport http io-usefulapi-rev-ai 'https://rev-ai.usefulapi.io/mcp'
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.