GingerLive

REMOTE · MCP.GINGERLIVE.IO · SCANNED AUG 20

GingerLive livestream ad formats, network reach stats, campaign case studies, and streamer program.

Available components

61 61 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 Security60

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability57

40% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 265 tokens (~29/item across 9 items; 6 tools + 3 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.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.gingerlive.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-gingerlive-mcp https://mcp.gingerlive.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-gingerlive-mcp]
url = "https://mcp.gingerlive.io/mcp"

// opencode.json

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

# add to OpenClaw

openclaw mcp add io-gingerlive-mcp --url https://mcp.gingerlive.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-gingerlive-mcp:
    url: "https://mcp.gingerlive.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-gingerlive-mcp": {
      "type": "http",
      "url": "https://mcp.gingerlive.io/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.

20 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
19 Aug 26 60

First indexed and scored.

Show 1 earlier entry Hide earlier entries

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 20 Aug 2026 · Probed https://mcp.gingerlive.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=gingerlive.io	CN=WE1,O=Google Trust Services,C=US	18 Aug 2026	16 Nov 2026	ECDSA 256	ECDSA-SHA256	b6e854fc7a72a3430ea7745042093d7e
SANs: gingerlive.io, mcp.gingerlive.io, *.mcp.gingerlive.io
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC secure

Validation of mcp.gingerlive.io. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
gingerlive.io.	present	2371	13	Verified
mcp.gingerlive.io.				Verified address RRset verified with the apex keys

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

Header	Value
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN
referrer-policy	same-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.gingerlive.io/mcp	Verified	200
http (plaintext)	http://mcp.gingerlive.io/mcp	HTTPS enforced	301	https://mcp.gingerlive.io/mcp

MCP tools · 6 exposed · ~250 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

get_case_study Get a case study ~63

Full write-up for one case study. Pass a slug returned by list_case_studies.

Input Output Examples

Name	Type	Req	Description
slug	string	yes	Case-study slug, e.g. 'turknet-x-gingerlive-case-study-gen-z-livestream-advertising-campaign'

No output schema declared.

No examples provided.

get_company_overview Company overview ~33

What GingerLive is: positioning summary, streaming platforms, network stats, third-party measurement partners, and contact links.

Input Output Examples