Meme Studio
REMOTE · MEMES.MRHYDE.DEV
Make memes from a big catalog of templates and GIFs or your own photo, and get the finished image
Available components
Last scanned (14 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Design and Media
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1577 tokens (~394/item across 4 items; 4 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 70
First indexed and scored.
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://memes.mrhyde.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mrhyde.dev | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2b2e34707ba254050e50eef11052082f |
| SANs: mrhyde.dev, *.mrhyde.dev | ||||||
| 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 secure
Validation of memes.mrhyde.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| mrhyde.dev. | present | 2371 | 13 | Verified |
| memes.mrhyde.dev. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'none';form-action 'self';frame-ancestors 'none';img-src 'self' blob: data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self';upgrade-insecure-requests;media-src 'self' blob:;connect-src 'self';worker-src 'self';manifest-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | accelerometer=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://memes.mrhyde.dev/mcp | Verified | 200 | |
| http (plaintext) | http://memes.mrhyde.dev/mcp | HTTPS enforced | 301 | https://memes.mrhyde.dev/mcp |
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 →
create_meme ~736
Create a meme on exactly one of: template (a catalog id), image (your own picture in base64 or a data: URL; JPEG, PNG, WebP or GIF, up to 5 MB and 25 megapixels (16 for WebP, 8 for GIF, less for a large progressive JPEG), 100 px or more a side, at most 4:1; a GIF gives its first frame) or image_url (an https address the server downloads). Your own picture is laid out like a template, with slots found in it (see get_template). Captions go in slots, classic top/bottom positions or boxes (fractions of the image, x and y the top-left corner), plus optional author, emojis, stickers, shapes with text and a filter. The server fits and colours every caption, and may write a line break (\n) into a returned caption text, to keep a short word or a number off the end of a line, to keep a quote on one line or to break a long word after an underscore: a returned text sent back as it is comes out the same. With author, the handle goes in the first corner free of other layers, and of faces when it can: bottom right, top right, bottom left, top left. When a top and a bottom caption leave no corner free, the bottom one moves up a little to free one for the handle, given or saved by the person in the studio. Returns the link that opens the meme in Meme Studio (an editor link, never an image source), what each caption got, warnings and a picture: picture "preview" (800 px to check, the default with a template) or "final" (the finished meme at 1200 px with the invisible watermark, like the studio download; the default with your own picture, because the link cannot carry it and only reopens the captions). For a file on disk, with a terminal, do not paste its base64 yourself: pipe the tools/call JSON from the shell into curl --data-binary @-, without a temporary copy of the picture, to the server's /mcp (Content-Type: application/json, Accept: application/json, text/event-stream; no initialize needed), then decode the data of the image item in result.content from base64 into a file for t…
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | The person's handle, with or without @, only if they gave it |
| captions | array | yes | – |
| emojis | array | – | – |
| filter | string | – | – |
| filter_strength | number | – | 0 to 1; the studio default when missing |
| image | string | – | Your own picture instead of a template: JPEG, PNG, WebP or GIF in base64 (a data: URL works too), up to 5 MB and 25 megapixels (16 for WebP, 8 for GIF, less for a large progressive JPEG) |
| image_url | string | – | Your own picture instead of a template: an https address the server downloads |
| language | string | – | Language of the person: es opens the Spanish studio, en the English one |
| picture | string | – | preview: 800 px to check (the default with a template); final: the finished meme at 1200 px (the default with image or image_url) |
| preview | boolean | – | false: return no picture |
| shapes | array | – | – |
| stickers | array | – | – |
| template | string | – | Template id; or give image or image_url instead |
No output schema declared.
No examples provided.
get_template ~250
Details of one template: names, what it is used for, tags, size, whether it is animated and its slots (the boxes where captions go). Each slot has fits_chars, about how many characters fit in it at a good size (0 is a small slot for a word or two): keep its caption under that or the text comes out small. With image: true (or show_slots: true) it also returns the picture with the slots outlined and numbered. Instead of template, give your own picture as image (base64) or image_url, as in create_meme: you get the slots found in that picture, the same ones create_meme uses with it.
| Name | Type | Req | Description |
|---|---|---|---|
| image | – | – | true: also return the picture with the numbered slots. Or your own picture in base64 instead of template, as in create_meme |
| image_url | string | – | Your own picture instead of template: an https address the server downloads |
| show_slots | boolean | – | Also return the picture with the numbered slots, the same as image: true |
| template | string | – | Template id from search_templates, the same you give create_meme; or give image or image_url instead |
No output schema declared.
No examples provided.
popular_templates ~45
Templates people choose most in Meme Studio: trending this week or most used overall.
| Name | Type | Req | Description |
|---|---|---|---|
| animated | boolean | – | – |
| kind | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
search_templates ~89
Search the Meme Studio catalog by name, keywords or what the meme is used for (intent), in Spanish or English. Best matches first, each with what it is used for.
| Name | Type | Req | Description |
|---|---|---|---|
| animated | boolean | – | true: only animated templates; false: only still ones |
| limit | integer | – | – |
| query | string | yes | The joke, the situation or the template name, in any language |
No output schema declared.
No examples provided.
How do I install the Meme Studio MCP server?
Meme Studio is a hosted endpoint at https://memes.mrhyde.dev/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 · memes.mrhyde.dev
claude mcp add --transport http dev-mrhyde-memes 'https://memes.mrhyde.dev/mcp'
What is the Meme Studio MCP server?
Meme Studio is an MCP server listed in the public MCP registry as dev.mrhyde/memes. Make memes from a big catalog of templates and GIFs or your own photo, and get the finished image. This page covers its hosted endpoint (https://memes.mrhyde.dev/mcp).
Is the Meme Studio MCP server safe to use?
Meme Studio scores 70 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 Meme Studio MCP server expose?
Meme Studio exposes 4 tools: search_templates, get_template, popular_templates, create_meme. Their descriptions and schemas cost roughly 1,120 tokens of context every time the server is loaded.
Does the Meme Studio MCP server require authentication?
No. We connected to Meme Studio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Meme Studio MCP server still maintained?
Meme Studio 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.