Agent MCP Directory

Reka: MCP server, CLI and agent surfaces

Yes: Reka runs a public MCP server at mcp.reka.ai that listed 17 tools to a client with no credentials on 4 November 2026. Examples: upload_video, list_videos, get_video. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for reka.ai is 77, grade B, read on 5 November 2026.

Fact sheet

CompanyReka
Domainreka.ai
CategoryAI & ML (Ora leaderboard category)
MCP serverVerified (No authentication)
Ora score77, grade B; Ora scanned the domain on 28 October 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for reka.ai, a vendor-published score)
Company found throughOra's public leaderboard
Last verified4 November 2026

MCP server

Endpointhttps://mcp.reka.ai/mcp
How it was foundlisted in Ora's public leaderboard
Transportstreamable-http
HTTP status200
Protocol version2025-11-25
Serverreka-vision 0.1.10
Capabilitiesexperimental, prompts, resources, tools
Tools17
Resources2
Prompts0
Connected4 November 2026, 20:04 UTC
Handshake time915 ms over 1 attempt

Tools listed

17 tools

  • upload_video
  • list_videos
  • get_video
  • update_video
  • delete_video
  • create_group
  • list_groups
  • delete_group
  • index_video
  • search_videos
  • ask_video
  • segment_video
  • get_transcript
  • get_captions
  • get_scenes
  • get_feature_catalog
  • summarize_video

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:59:09Z https://mcp.reka.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1184 ms
  • 20:04:14Z https://mcp.reka.ai/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 915 ms

Authentication

Auth typeNo authentication

The sign-in route, step by step

  1. Send the handshake to https://mcp.reka.ai/mcp over streamable-http. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
  2. Send tools/list, then resources/list and prompts/list if the capabilities name them.
  3. Send no token. The connector sent none and the server answered, so any MCP client can read this list.
  4. Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Reka. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot detected on the home page by the shared crawl.
MCP discovery fileNot found (the crawl got a non-200 answer).
A2A agent cardNot found (the crawl got a non-200 answer).
A2A agent card (older path)Not found (the crawl got a non-200 answer).
agents.jsonNot found (the crawl got a non-200 answer).
OAuth authorization server metadataNot found (the crawl got a non-200 answer).
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: ai.reka/mcp
GitHub MCP RegistryNo
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.