Reka MCP Server

https://mcp.reka.ai/mcp Remote v0.1.10

Published by mcp.reka.ai — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

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

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([list_videos, get_video, search_videos]) co-exist with external-action tools ([upload_video]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [list_videos, get_video, search_videos] → sinks [upload_video]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow list_videos → upload_video

medium Unconstrained URL/host parameter "video_url" on "upload_video"MTC-CAP-007

Tool "upload_video" takes a URL/host parameter "video_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool upload_video · inputSchema.properties.video_url

Tools 17

Each tool and what it can reach — enumerated from the running server.

  • get_videoingests untrusted input
  • list_videosingests untrusted input
  • search_videosingests untrusted input
  • upload_videonetwork egress
  • ask_videono sensitive capability
  • create_groupno sensitive capability
  • delete_groupno sensitive capability
  • delete_videono sensitive capability
  • get_captionsno sensitive capability
  • get_feature_catalogno sensitive capability
Show 7 more tools ↓
  • get_scenesno sensitive capability
  • get_transcriptno sensitive capability
  • index_videono sensitive capability
  • list_groupsno sensitive capability
  • segment_videono sensitive capability
  • summarize_videono sensitive capability
  • update_videono sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.10 latest A 97/100 2 1.10.0 2026-07-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-reka-ai/badge.svg)](https://mcptrustchecker.com/registry/mcp-reka-ai)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-reka-ai"><img src="https://mcptrustchecker.com/registry/mcp-reka-ai/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-reka-ai/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://mcp.reka.ai/mcp --online

Use the free API → How scoring works

More in Web, Search & Scraping