io.usefulapi/bannerbear
REMOTE · BANNERBEAR.USEFULAPI.IO · SCANNED SEP 21
Generate images, videos, and screenshots from your Bannerbear templates via AI.
Available components
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 Security46
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.usefulapi/bannerbear MCP server?
io.usefulapi/bannerbear is a hosted endpoint at https://bannerbear.usefulapi.io/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 · bannerbear.usefulapi.io
claude mcp add --transport http io-usefulapi-bannerbear 'https://bannerbear.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-bannerbear": {
"url": "https://bannerbear.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-bannerbear": {
"type": "http",
"url": "https://bannerbear.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-bannerbear] url = "https://bannerbear.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-bannerbear": {
"type": "remote",
"url": "https://bannerbear.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-bannerbear --url 'https://bannerbear.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-bannerbear:
url: "https://bannerbear.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-bannerbear": {
"Transport": "http",
"Url": "https://bannerbear.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-bannerbear -t streamable-http -u 'https://bannerbear.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-bannerbear": {
"type": "http",
"url": "https://bannerbear.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Sept 26 −68
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 0
- Transport: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.60 ▲ functional
- 13 Aug 26 0
- Transport: fail → unverified ▼ security
- 12 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
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 21 Sept 2026 · Probed https://bannerbear.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 97837d984d11098c0e477eb27bc455a4 |
| SANs: usefulapi.io, bannerbear.usefulapi.io, *.bannerbear.usefulapi.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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bannerbear.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bannerbear.usefulapi.io/mcp | Auth required | 401 | |
| http (plaintext) | http://bannerbear.usefulapi.io/mcp | Inconclusive | 401 |
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 →
bannerbear_create_collection Create collection ~195
Generate a collection of images from a template set (additive; CONSUMES API quota). Async: returns a `pending` collection whose uid you poll with bannerbear_get_collection (image_urls map populates on completion). API: POST /v2/collections.
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | string | – | Arbitrary metadata string echoed back on the object. |
| modifications | array | – | Layer overrides applied to the template. Array of objects, one per layer, each keyed by `name` (the layer name) plus the props to set, e.g. { name: "title", text: "Hello", color: "#FF0000" } or { nam… |
| template_set | string | yes | Template set uid to render. |
| webhook_url | string | – | URL Bannerbear will POST the finished collection to when done. |
No output schema declared.
No examples provided.
bannerbear_create_image Create image ~260
Generate an image from a template (additive; CONSUMES API quota). Async by default: returns a `pending` image whose uid you poll with bannerbear_get_image. Set synchronous:true to block and receive the finished image (image_url populated) via the sync host. API: POST /v2/images.
| Name | Type | Req | Description |
|---|---|---|---|
| metadata | string | – | Arbitrary metadata string echoed back on the object. |
| modifications | array | – | Layer overrides applied to the template. Array of objects, one per layer, each keyed by `name` (the layer name) plus the props to set, e.g. { name: "title", text: "Hello", color: "#FF0000" } or { nam… |
| render_pdf | boolean | – | Also render a PDF version of the image. |
| synchronous | boolean | – | When true, POST to the sync host and wait for the completed image. Default false (202 pending). |
| template | string | yes | Template uid to render. |
| transparent | boolean | – | Render with a transparent background (PNG). |
| webhook_url | string | – | URL Bannerbear will POST the finished image to when done. |
No output schema declared.
No examples provided.
bannerbear_create_screenshot Create screenshot ~162
Capture a screenshot of a web page (additive; CONSUMES API quota). Async by default: returns a `pending` screenshot to poll. Set synchronous:true to block and receive the finished screenshot via the sync host. API: POST /v2/screenshots.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | – | Viewport height in pixels. |
| mobile | boolean | – | Render with a mobile viewport. |
| synchronous | boolean | – | When true, POST to the sync host and wait for the completed screenshot. Default false (202 pending). |
| url | string | yes | Public URL of the web page to screenshot. |
| webhook_url | string | – | URL Bannerbear will POST the finished screenshot to when done. |
| width | integer | – | Viewport width in pixels. |
No output schema declared.
No examples provided.
bannerbear_create_video Create video ~217
Generate a video from a video template (additive; CONSUMES API quota). Async: returns a `pending` video whose uid you poll with bannerbear_get_video (video_url populates on completion). API: POST /v2/videos.
| Name | Type | Req | Description |
|---|---|---|---|
| input_media_url | string | – | URL of the source media (e.g. an audio/video file) to build from. |
| metadata | string | – | Arbitrary metadata string echoed back on the object. |
| modifications | array | – | Layer overrides applied to the template. Array of objects, one per layer, each keyed by `name` (the layer name) plus the props to set, e.g. { name: "title", text: "Hello", color: "#FF0000" } or { nam… |
| video_template | string | yes | Video template uid to render. |
| webhook_url | string | – | URL Bannerbear will POST the finished video to when done. |
No output schema declared.
No examples provided.
bannerbear_get_account Get account ~36
Get account details and usage: api_usage, api_quota, and paid_plan_name. API: GET /v2/account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bannerbear_get_collection Get collection ~65
Get a single collection — poll this to check an async render (status: pending | completed | failed; image_urls map populates on completion). API: GET /v2/collections/{uid}.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | Collection uid (from a create_collection response). |
No output schema declared.
No examples provided.
bannerbear_get_image Get image ~64
Get a single generated image — poll this to check an async render (status: pending | completed | failed; image_url populates on completion). API: GET /v2/images/{uid}.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | Image uid (from a create_image response). |
No output schema declared.
No examples provided.
bannerbear_get_template Get template ~48
Get a single template incl. its available_modifications (the layers you can override when generating). API: GET /v2/templates/{uid}.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | Template uid. |
No output schema declared.
No examples provided.
bannerbear_get_template_set Get template set ~43
Get a single template set and the templates it contains. API: GET /v2/template_sets/{uid}.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | Template set uid. |
No output schema declared.
No examples provided.
bannerbear_get_video Get video ~64
Get a single generated video — poll this to check an async render (status: pending | completed | failed; video_url populates on completion). API: GET /v2/videos/{uid}.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | Video uid (from a create_video response). |
No output schema declared.
No examples provided.
bannerbear_list_effects List effects ~31
List the image effects available for use in template modifications. API: GET /v2/effects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bannerbear_list_fonts List fonts ~28
List the fonts available for use in template modifications. API: GET /v2/fonts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bannerbear_list_images List images ~39
List generated images in the project (paginated). API: GET /v2/images.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination. |
No output schema declared.
No examples provided.
bannerbear_list_template_sets List template sets ~43
List the template sets in the project (used by collections). API: GET /v2/template_sets.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination. |
No output schema declared.
No examples provided.
bannerbear_list_templates List templates ~87
List the templates in the project. Filter/paginate with page, tag, name, and limit. API: GET /v2/templates.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of templates per page. |
| name | string | – | Filter templates by name (substring match). |
| page | integer | – | Page number for pagination. |
| tag | string | – | Filter templates by tag. |
No output schema declared.
No examples provided.
What is the io.usefulapi/bannerbear MCP server?
io.usefulapi/bannerbear is an MCP server listed in the public MCP registry as io.usefulapi/bannerbear. Generate images, videos, and screenshots from your Bannerbear templates via AI. This page covers its hosted endpoint (https://bannerbear.usefulapi.io/mcp).
Is the io.usefulapi/bannerbear MCP server safe to use?
io.usefulapi/bannerbear scores 18 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 io.usefulapi/bannerbear MCP server expose?
io.usefulapi/bannerbear exposes 15 tools: bannerbear_get_account, bannerbear_list_templates, bannerbear_get_template, bannerbear_list_template_sets, bannerbear_get_template_set, and 10 more. Their descriptions and schemas cost roughly 1,382 tokens of context every time the server is loaded.
Does the io.usefulapi/bannerbear MCP server require authentication?
No. We connected to io.usefulapi/bannerbear without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.usefulapi/bannerbear MCP server still maintained?
io.usefulapi/bannerbear is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.