# Reka (remote · mcp.reka.ai)

Understand your videos with Reka AI — search, ask questions, and extract insights.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.reka.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ai-reka-mcp/mcp.md), [page](https://verifymcp.io/servers/ai-reka-mcp/mcp)
- pypi · `reka-mcp`: 5/100, [markdown](https://verifymcp.io/servers/ai-reka-mcp/reka-mcp.md), [page](https://verifymcp.io/servers/ai-reka-mcp/reka-mcp)

## Channel facts

- Endpoint: `https://mcp.reka.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.10`

## 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-08-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_video).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1769 tokens (~93/item across 19 items; 17 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-reka-mcp https://mcp.reka.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-reka-mcp]
url = "https://mcp.reka.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-reka-mcp --url https://mcp.reka.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-reka-mcp:
    url: "https://mcp.reka.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-reka-mcp": {
      "type": "http",
      "url": "https://mcp.reka.ai/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-08-04 (score 66, +1)

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

### 2026-08-02 (score 65, +1)

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

### 2026-07-31 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (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-07-27 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (17)

### `upload_video` (~93 tokens)

Upload a video from a URL. Returns a video_id. Local file paths are not accepted; upload files outside the MCP server and pass a reachable video_url. The upload runs asynchronously — poll get_video until status is 'uploaded', then call index_video to enable search and analysis.

Input parameters:

- `description`
- `group_id`
- `name`
- `rationale`
- `video_url` (string, required)

Output parameters:

- `result` (string)

### `list_videos` (~92 tokens)

List all videos in your account, or filter to a specific group by passing group_id. Shows upload status and which features have been indexed for each video. Each video's 'url' is a short-lived HTTPS presigned URL (expires within hours) — fetch immediately and do not store; call list_videos or get_video again for a fresh URL when needed.

Input parameters:

- `group_id`
- `rationale`

Output parameters:

- `result` (string)

### `get_video` (~93 tokens)

Get detailed information about a video including upload status, metadata (duration, resolution, fps), and per-feature indexing status. Use this to check if upload or indexing is complete. The 'url' field is a short-lived HTTPS presigned URL (expires within hours) — fetch immediately and do not store; call get_video again for a fresh URL when needed.

Input parameters:

- `rationale`
- `video_id` (string, required)

Output parameters:

- `result` (string)

### `update_video` (~90 tokens)

Update a video's display name, title, description, or move it to a different group. At least one field must be provided. To remove a video from its group, pass group_id as null.

Input parameters:

- `description`
- `group_id`
- `move_group` (boolean)
- `name`
- `rationale`
- `title`
- `video_id` (string, required)

Output parameters:

- `result` (string)

### `delete_video` (~46 tokens)

Permanently delete a video and all its indexed data (transcript, captions, embeddings, etc.). This cannot be undone.

Input parameters:

- `rationale`
- `video_id` (string, required)

Output parameters:

- `result` (string)

### `create_group` (~40 tokens)

Create a new video group. Groups organize videos into collections. Returns the new group's ID and name.

Input parameters:

- `name` (string, required)
- `rationale`

Output parameters:

- `result` (string)

### `list_groups` (~34 tokens)

List all video groups. Use list_videos with a group_id to see videos in a specific group.

Input parameters:

- `rationale`

Output parameters:

- `result` (string)

### `delete_group` (~42 tokens)

Delete a video group. Videos in the group are not deleted — they are simply removed from the group.

Input parameters:

- `group_id` (string, required)
- `rationale`

Output parameters:

- `result` (string)

### `index_video` (~184 tokens)

Index a video for search, QA, or full analysis. Processes the video through a pipeline of AI features. Typically takes 3-7 minutes; longer for long videos or the 'full' pipeline. Times out after 10 minutes by default.

Pipelines:
\- search_only: transcription + captions + embeddings (enables search_videos)
\- qa_only: transcription + captions (enables ask_video)
\- full: transcription + captions + embeddings (enables all tools)

Scene detection is enabled by default and produces scene boundaries for get_scenes. Pass scene_detection=False to skip it.

Prerequisites: if using video_id, the video must be in 'uploaded' status. Use get_video to check status before calling this tool.

Input parameters:

- `pipeline` (string)
- `rationale`
- `scene_detection` (boolean)
- `video_id` (string, required)

Output parameters:

- `result` (string)

### `search_videos` (~151 tokens)

Find WHEN and WHERE something happens across your videos. Returns timestamped results ranked by relevance — use these timestamps as start/end in ask_video for focused analysis.

This is the recommended first step for most questions. Instead of asking ask_video about the entire video, search first to narrow down the relevant moments.

Each result's 'video_url' is a short-lived HTTPS presigned URL (expires within hours) — fetch immediately and do not store; call search_videos or get_video again for a fresh URL when needed.

Requires search_only or full pipeline.

Input parameters:

- `group_id`
- `max_results` (integer)
- `query` (string, required)
- `rationale`
- `video_ids`

Output parameters:

- `result` (string)

### `ask_video` (~208 tokens)

Ask a question about one or more videos with visual analysis. Most effective on focused time ranges — use start/end to specify the segment to analyze.

BEFORE calling this tool, read the reka://docs/guide resource for recommended workflows. In most cases, you should first:
\- search_videos to find WHEN something happens, then pass those timestamps here as start/end
\- segment_video to detect and locate specific objects
\- get_transcript to read what was said

For single-video questions, pass video_id with start/end. For cross-video questions, pass videos — a list of video references with start/end each.

For follow-up questions, pass conversation_id from the previous response. You can add start/end to drill into a specific moment while keeping the conversation context.

Requires qa_only or full pipeline.

Input parameters:

- `conversation_id`
- `end`
- `question` (string, required)
- `rationale`
- `start`
- `video_id`
- `videos`

Output parameters:

- `result` (string)

### `segment_video` (~235 tokens)

Detect objects in a video segment using text prompts. Describe what to look for and get per-frame detections with bounding boxes and confidence scores.

Prompt tips:
\- Use broad, visual categories: 'animal', 'vehicle', 'person', 'text on screen'
\- Specific labels ('rabbit', 'Toyota') are less reliable — the detector matches visual patterns, not semantic concepts
\- Best for confirming whether a category of object appears in a time window, not for precise identification

How to pick a time range:
\- Use search_videos to find WHEN something appears, then pass those timestamps here
\- Use get_scenes to scan systematically — call segment_video once per scene (scenes typically fit in the 15s window)
\- Or pass any range you already know

Maximum range is 15 seconds per call; for longer spans, make multiple calls with consecutive windows.

Does NOT require any feature indexing — works on any uploaded video.

Input parameters:

- `end`
- `prompts` (array, required)
- `rationale`
- `start` (number, required)
- `threshold` (number)
- `video_id` (string, required)

Output parameters:

- `result` (string)

### `get_transcript` (~106 tokens)

Get the spoken words in a video. Use this instead of ask_video when you need to read what was said — it returns the actual text, not a summary.

Use start/end to narrow results for long videos.

Requires the transcript feature to be indexed.

Input parameters:

- `end`
- `format` (string)
- `max_chars` (integer)
- `max_results` (integer)
- `rationale`
- `start`
- `video_id` (string, required)

Output parameters:

- `result` (string)

### `get_captions` (~89 tokens)

Get AI-generated visual descriptions of what happens on screen. Use this to understand the visual content without watching — each caption describes a short segment with timestamps.

Use start/end to narrow results.

Requires the captions feature (qa_only or full pipeline).

Input parameters:

- `end`
- `max_results` (integer)
- `rationale`
- `start`
- `video_id` (string, required)

Output parameters:

- `result` (string)

### `get_scenes` (~113 tokens)

Get detected scene boundaries with start/end timestamps. Use this to understand the video's structure, then pass scene timestamps as start/end to:
\- ask_video for per-scene contextual analysis
\- segment_video to detect specific objects per scene (scenes typically fit in segment_video's 15s max range)

Requires transcript indexed with scene detection (on by default; skipped only if index_video was called with scene_detection=False).

Input parameters:

- `max_results` (integer)
- `rationale`
- `video_id` (string, required)

Output parameters:

- `result` (string)

### `get_feature_catalog` (~41 tokens)

List available video analysis features with their dependencies and descriptions. Use this to understand what features exist and what pipelines to use with index_video.

Input parameters:

- `rationale`

Output parameters:

- `result` (string)

### `summarize_video` (~71 tokens)

Start here. Get a compact overview of a video: metadata, which features are indexed, a transcript preview, and scene count. Use this to decide which tools to call next — then use segment_video to detect specific objects in time ranges of interest.

Input parameters:

- `rationale`
- `video_id` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-08-04: 66
- 2026-08-03: 65
- 2026-08-02: 65
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 63
- 2026-07-29: 62
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 60

## Links

- Remote endpoint: https://mcp.reka.ai/mcp
- Authorisation metadata: https://mcp.reka.ai/.well-known/oauth-protected-resource/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-reka-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-reka-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-reka-mcp/mcp