Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Reka

REMOTE · MCP.REKA.AI · 2 COMPONENTS · SCANNED AUG 3

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

+4 this week 65 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1769 tokens (~93/item across 19 items; 17 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.reka.ai

# add to Claude Code
claude mcp add --transport http ai-reka-mcp https://mcp.reka.ai/mcp
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-reka-mcp --url https://mcp.reka.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-reka-mcp:
    url: "https://mcp.reka.ai/mcp"
// mcp.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 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.

  • 2 Aug 26 +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.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +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.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 60

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://mcp.reka.ai/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.reka.ai CN=Amazon RSA 2048 M04,O=Amazon,C=US 8 May 2026 21 Nov 2026 RSA 2048 SHA256-RSA 27def1263b9824defb1dbb49af8483b
SANs: mcp.reka.ai, *.mcp.reka.ai
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6
DNSSEC insecure

Validation of mcp.reka.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
reka.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.reka.ai/mcp Verified 200
http (plaintext) http://mcp.reka.ai/mcp HTTPS enforced
MCP tools — 17 exposed · ~1,728 tokens

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.

Tool Tokens
ask_video ~208

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.

NameTypeReqDescription
conversation_id
end
questionstringyes
rationale
start
video_id
videos
NameTypeReqDescription
resultstringyes

No examples provided.

create_group ~40

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

NameTypeReqDescription
namestringyes
rationale
NameTypeReqDescription
resultstringyes

No examples provided.

delete_group ~42

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

NameTypeReqDescription
group_idstringyes
rationale
NameTypeReqDescription
resultstringyes

No examples provided.

delete_video ~46

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

NameTypeReqDescription
rationale
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_captions ~89

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).

NameTypeReqDescription
end
max_resultsinteger
rationale
start
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_feature_catalog ~41

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.

NameTypeReqDescription
rationale
NameTypeReqDescription
resultstringyes

No examples provided.

get_scenes ~113

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).

NameTypeReqDescription
max_resultsinteger
rationale
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_transcript ~106

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.

NameTypeReqDescription
end
formatstring
max_charsinteger
max_resultsinteger
rationale
start
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

get_video ~93

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.

NameTypeReqDescription
rationale
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

index_video ~184

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.

NameTypeReqDescription
pipelinestring
rationale
scene_detectionboolean
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

list_groups ~34

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

NameTypeReqDescription
rationale
NameTypeReqDescription
resultstringyes

No examples provided.

list_videos ~92

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.

NameTypeReqDescription
group_id
rationale
NameTypeReqDescription
resultstringyes

No examples provided.

search_videos ~151

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.

NameTypeReqDescription
group_id
max_resultsinteger
querystringyes
rationale
video_ids
NameTypeReqDescription
resultstringyes

No examples provided.

segment_video ~235

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.

NameTypeReqDescription
end
promptsarrayyes
rationale
startnumberyes
thresholdnumber
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

summarize_video ~71

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.

NameTypeReqDescription
rationale
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

update_video ~90

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.

NameTypeReqDescription
description
group_id
move_groupboolean
name
rationale
title
video_idstringyes
NameTypeReqDescription
resultstringyes

No examples provided.

upload_video ~93

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.

NameTypeReqDescription
description
group_id
name
rationale
video_urlstringyes
NameTypeReqDescription
resultstringyes

No examples provided.