Redbee MCP Server

redbee-mcp PyPI v1.4.2

Published by tamsibesson — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP Server for Red Bee Media OTT Platform - MCP Interface for Exposure APIs

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
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 = 99/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 − 1 = 99. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 37

Each tool and what it can reach — statically extracted from the published source.

  • add_payment_methodno sensitive capability
  • add_user_profileno sensitive capability
  • cancel_purchase_subscriptionno sensitive capability
  • change_user_passwordno sensitive capability
  • create_anonymous_sessionno sensitive capability
  • delete_user_deviceno sensitive capability
  • get_account_purchasesno sensitive capability
  • get_account_transactionsno sensitive capability
  • get_active_channelsno sensitive capability
  • get_asset_collection_entriesno sensitive capability
Show 27 more tools ↓
  • get_asset_detailsno sensitive capability
  • get_asset_thumbnailno sensitive capability
  • get_assets_by_tagno sensitive capability
  • get_epg_for_channelno sensitive capability
  • get_episodes_for_seasonno sensitive capability
  • get_offeringsno sensitive capability
  • get_playback_infono sensitive capability
  • get_public_asset_detailsno sensitive capability
  • get_seasons_for_seriesno sensitive capability
  • get_stored_payment_methodsno sensitive capability
  • get_system_configno sensitive capability
  • get_system_timeno sensitive capability
  • get_user_devicesno sensitive capability
  • get_user_locationno sensitive capability
  • get_user_preferencesno sensitive capability
  • get_user_profilesno sensitive capability
  • list_assetsno sensitive capability
  • login_userno sensitive capability
  • logout_userno sensitive capability
  • purchase_product_offeringno sensitive capability
  • search_assets_autocompleteno sensitive capability
  • search_content_v2no sensitive capability
  • search_multi_v3no sensitive capability
  • select_user_profileno sensitive capability
  • set_user_preferencesno sensitive capability
  • signup_userno sensitive capability
  • validate_session_tokenno sensitive capability

What this scan could not see

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
v1.4.2 latest A 99/100 0 1.13.0 2026-08-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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/redbee-mcp/badge.svg)](https://mcptrustchecker.com/registry/redbee-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/redbee-mcp"><img src="https://mcptrustchecker.com/registry/redbee-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/redbee-mcp/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 redbee-mcp --online --registry pypi

Use the free API → How scoring works

More in Design & Media