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

Green Screen Memes

REMOTE · API.GREENSCREENMEMES.APP

2,000+ green screen meme clips to search, with an ffmpeg recipe to key each over video.

78 Trust /100

Last scanned (22 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Design and Media

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security92
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 900 tokens (~128/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +4
    • Authorization: fail → pass ▲ security
    • First check of Authorization: pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_usage” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 74

    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 4 Nov 2026 · Probed https://api.greenscreenmemes.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=greenscreenmemes.app CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 d5e7cb2c4d630db913253f931618e8c8
SANs: greenscreenmemes.app, api.greenscreenmemes.app, *.api.greenscreenmemes.app
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.greenscreenmemes.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
greenscreenmemes.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="Green Screen Memes API", resource_metadata="https://api.greenscreenmemes.app/.well-known/oauth-protected-resource/mcp", scope="clips"

Bearer realm="Green Screen Memes API", resource_metadata="https://api.greenscreenmemes.app/.well-known/oauth-protected-resource/mcp", scope="clips"

Protected resource metadata

Document https://api.greenscreenmemes.app/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.greenscreenmemes.app/mcp
Authorisation server https://api.greenscreenmemes.app

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.greenscreenmemes.app/mcp Verified 200
http (plaintext) http://api.greenscreenmemes.app/mcp HTTPS enforced 301 https://api.greenscreenmemes.app/mcp
MCP tools · 7 exposed · ~523 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_collection ~81

The green screens in one collection, in order. Use id "trending" for the current trending clips.

NameTypeReqDescription
cursorstring–nextCursor from a previous result, for the next page.
idstringyesA collection id from list_collections, or "trending".
limitinteger–How many results (default 10).

No output schema declared.

No examples provided.

get_green_screen ~47

One green screen clip by id, with its video link and an ffmpeg recipe for compositing it over an image or video.

NameTypeReqDescription
idstringyesThe id from search results.

No output schema declared.

No examples provided.

get_trending ~79

What people are using right now in the Green Screen Memes app, most popular first. Each clip has its trending rank (1 = most popular), plus the same fields as search results.

NameTypeReqDescription
cursorstring–nextCursor from a previous result, for the next page.
limitinteger–How many results (default 10).

No output schema declared.

No examples provided.

get_usage ~82

This API key's plan (free or paid, with its price), the calls and video downloads it has used and has left (the free plan's 50 downloads are one-time; paid plans' reset monthly), and the plans above it with prices and an upgrade link. Use it when someone asks what this costs, whether it's free, or how to get more.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_collections ~39

Curated collections of green screens, including "trending" (what people are using right now in the app; get_trending returns it directly).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tags ~41

The most used tags with how many green screens have each, to see what the library covers.

NameTypeReqDescription
limitinteger–How many tags (default 100).

No output schema declared.

No examples provided.

search_green_screens ~154

Search green screen meme clips by words (matched against names, tags and descriptions). Leave query empty to get the newest. Returns ids, names, descriptions, thumbnails and video links.

NameTypeReqDescription
colorstring–Only clips with this background color. "none" means the clip has no key color and is used as-is.
cursorstring–nextCursor from a previous result, for the next page.
limitinteger–How many results (default 10).
querystring–A few words for the reaction, action or subject, e.g. "angry cat" or "dancing".
tagstring–Only clips with this exact tag (see list_tags).

No output schema declared.

No examples provided.

Install

How do I install the Green Screen Memes MCP server?

Green Screen Memes is a hosted endpoint at https://api.greenscreenmemes.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.greenscreenmemes.app

# add to Claude Code
claude mcp add --transport http app-greenscreenmemes-api-green-screen-memes 'https://api.greenscreenmemes.app/mcp'
Common questions

What is the Green Screen Memes MCP server?

Green Screen Memes is an MCP server listed in the public MCP registry as app.greenscreenmemes.api/green-screen-memes. 2,000+ green screen meme clips to search, with an ffmpeg recipe to key each over video. This page covers its hosted endpoint (https://api.greenscreenmemes.app/mcp).

Is the Green Screen Memes MCP server safe to use?

Green Screen Memes scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Green Screen Memes MCP server expose?

Green Screen Memes exposes 7 tools: search_green_screens, get_green_screen, get_trending, list_collections, get_collection, and 2 more. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.

Does the Green Screen Memes MCP server require authentication?

Yes. Green Screen Memes asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Green Screen Memes MCP server still maintained?

Green Screen Memes is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.