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.

AlertForge

REMOTE · ALERTFORGE.AI

Create stream overlays, AI alerts, and transparent videos through AlertForge.

Available components

+4 this week 70 Trust /100

Last scanned (1 hour ago)

Scores higher than 55% of remote servers

Reachable. Last reached 5 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 Security66
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5016 tokens (~209/item across 24 items; 24 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% 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 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 25 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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 26 66

    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 5 Nov 2026 · Probed https://alertforge.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=alertforge.ai CN=YE2,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA384 697c13d41776061733a707f1261c0ef9ce7
SANs: *.alertforge.ai, alertforge.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of alertforge.ai. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
alertforge.ai. present 2371 13 Verified
alertforge.ai. 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=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://static.cloudflareinsights.com https://www.googletagmanager.com https://www.googleadservices.com https://*.doubleclick.net https://connect.facebook.net; script-src-elem 'self' 'unsafe-inline' https://static.cloudflareinsights.com https://www.googletagmanager.com https://www.googleadservices.com https://*.doubleclick.net https://connect.facebook.net; script-src-attr 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.supabase.co https://*.fal.media https://*.r2.cloudflarestorage.com https://cloudflareinsights.com https://www.google-analytics.com https://www.googletagmanager.com https://api.producthunt.com https://www.googleadservices.com https://*.doubleclick.net https://www.google.com https://google.com https://www.google.com.au https://www.facebook.com; media-src 'self' blob: https://*.supabase.co https://*.fal.run https://*.fal.media https://*.r2.cloudflarestorage.com; connect-src 'self' https://*.supabase.co ws
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://alertforge.ai/api/mcp Verified 200
http (plaintext) http://alertforge.ai/api/mcp HTTPS enforced 301 https://alertforge.ai/api/mcp
MCP tools · 24 exposed · ~4,890 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
approve_design_sheet ~181

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Records the user's approval of a rendered Style Sheet -- call this ONLY after the user has actually seen the image from get_pack_status's designPackage.imageUrl and said they like it. This is the server-side gate: plan_overlay_pack refuses to plan any scene on this project until approve_design_sheet has been called successfully. Fails if the Style Sheet hasn't finished rendering yet -- poll get_pack_status until designPackage.status is "ready" first. Safe to call again on an already-approved project (returns the same approval, does not re-approve or error).

NameTypeReqDescription
projectIdstringyesprojectId returned by create_design_sheet.

No output schema declared.

No examples provided.

create_alert_pack ~199

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Spends credits. Consumes a plan from plan_alert_pack and creates its alert(s). Requires an active AlertForge subscription (checked at this step, not at planning) -- fails with 'subscription_required' otherwise. Calling this again with the same planId after it already succeeded is safe -- it returns the same pack rather than creating a second one or charging twice. A single failed alert does not fail the whole call -- check each entry's `error` field in the result. Returns immediately, before any alert has rendered -- call get_alert_pack_status afterward to check progress. Timing varies by model, queue, processing route, and provider demand.

NameTypeReqDescription
planIdstringyesplanId returned by plan_alert_pack.

No output schema declared.

No examples provided.

create_design_sheet ~176

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Consumes a plan from plan_design_sheet, spending its quoted credits and creating the project. Calling this again with the same planId after it already succeeded is safe -- it returns the same project rather than creating a second one or charging twice. Returns immediately, before the Style Sheet image has rendered -- call get_pack_status to advance rendering and get designPackage.imageUrl, show it to the user, then call approve_design_sheet once they approve it. plan_overlay_pack refuses to plan any scene on this project until that approval is recorded.

NameTypeReqDescription
planIdstringyesplanId returned by plan_design_sheet.

No output schema declared.

No examples provided.

create_overlay_pack ~163

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Consumes a plan from plan_overlay_pack, spending its quoted credits and ATTACHING those scenes to the existing design-approved project (it never creates a new project -- that happened at create_design_sheet time). Calling this again with the same planId after it already succeeded is safe -- it returns the same project rather than attaching the scenes a second time or charging twice. Returns immediately, before any scene has rendered -- call get_pack_status afterward to advance and check progress.

NameTypeReqDescription
planIdstringyesplanId returned by plan_overlay_pack.

No output schema declared.

No examples provided.

create_style_sheet_character_edit ~152

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Spends the quoted credits and queues the character-region change from plan_style_sheet_character_edit. It keeps the same project and patches only the character slot into the current Style Sheet. Safe to retry with the same planId. The previous approval is cleared; poll get_style_sheet_character_edit_status, show the revised image to the user, then approve_design_sheet only after the user explicitly approves it.

NameTypeReqDescription
planIdstringyesplanId returned by plan_style_sheet_character_edit.

No output schema declared.

No examples provided.

create_transparent_video ~193

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Spends credits. Consumes a plan from plan_transparent_video and starts the render. No subscription is required to CREATE it (only credits) -- but downloading/exporting the finished file later depends on the account's existing entitlement; plan_transparent_video's `downloadWarning` field tells you up front if the account can't download yet. Calling this again with the same planId after it already succeeded is safe -- it returns the same render rather than creating a second one. Returns immediately -- call get_render_status to check progress. Timing varies by model, duration, queue, processing route, and provider demand.

NameTypeReqDescription
planIdstringyesplanId returned by plan_transparent_video.

No output schema declared.

No examples provided.

export_pack_zip ~158

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Bundles the pack's finished scenes into a flat ZIP (WebMs + PNGs + manifest.json) uploaded to R2, returning a time-limited signed download URL. This is the flat agent pack, not the full themed folder-tree artifact (scenes/stinger/alerts/sheet-tile ladders with composited branding) -- that comes from the 'Download pack' button in the web editor at this result's editorUrl.

NameTypeReqDescription
projectIdstringyesprojectId returned by create_overlay_pack.

No output schema declared.

No examples provided.

generate_alert_character ~159

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Spends credits (the exact price is in list_alert_types' characterGenerateCredits). Generates a brand-new standalone character portrait from a text description via AI -- this is a still image, not a video. Returns a renderId immediately; generation is asynchronous and provider timing varies. Poll get_alert_character_status with it until status is 'completed', then use the returned `path` as characterImageUrl in plan_alert_pack.

NameTypeReqDescription
promptstringyesA description of the character to generate, up to 600 characters.

No output schema declared.

No examples provided.

get_alert_character_status ~126

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call. Read-only poll for a character generation started by generate_alert_character -- call it every few seconds until status is 'completed' (with a usable `path`/`url`) or 'failed' (reserved credits are returned to the wallet automatically on failure).

NameTypeReqDescription
renderIdstringyesrenderId returned by generate_alert_character.

No output schema declared.

No examples provided.

get_alert_pack_status ~153

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call. Read-only -- unlike get_pack_status, this does NOT advance anything (the render worker progresses these on its own schedule, outside this call). Reports each alert's current status (queued/running/succeeded/failed), its result WebM URL once done, its OBS overlay URL, and its credit cost. Poll at a reasonable interval until every alert reaches a terminal state; provider timing varies.

NameTypeReqDescription
packIdstringyespackId returned by create_alert_pack.

No output schema declared.

No examples provided.

get_balance ~64

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Get the caller's current AlertForge credit balance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_pack_status ~344

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Advances the pack by running up to about 15 seconds of rendering work, then reports current status -- including the Style Sheet's own status and image URL (`designPackage`) and whether it has been approved (`designApproved`), plus per-scene status. A sheet-pack scene (panel-pack/label-pack/sub-badge-pack/ emote-pack) passes through an extra "tiles" stage after its sheet image renders (cropping + uploading each tile) and, once done, reports a `tiles` array (index, label, enabled, a signed download `url`, and an export-ladder `sizes` array for sub-badge-pack/emote-pack). This call has side effects -- call it repeatedly (e.g. every few seconds) until `complete` is true; each call both progresses the pack and returns its latest state. Works on a design-sheet-only project too (from create_design_sheet, before any scene exists) -- poll it until designPackage.status is "ready", then call approve_design_sheet. Every image/video link this returns (designPackage.imageUrl, previewImageUrl, resultUrl, tile urls) is a direct, absolute, signed download URL that opens with no AlertForge login -- never a dashboard link. Links expire after a while, so re-poll to get fresh ones rather than caching one long-term.

NameTypeReqDescription
projectIdstringyesprojectId returned by create_design_sheet or create_overlay_pack.

No output schema declared.

No examples provided.

get_product_info ~32

Read-only. What AlertForge is, its key features, supported streaming platforms, and OBS-ecosystem compatibility.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_render_status ~113

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call. Read-only poll for any single render you own -- a transparent video created via create_transparent_video, or any other render id. Reports status and the result video URL(s) once done.

NameTypeReqDescription
renderIdstringyesrenderId returned by create_transparent_video.

No output schema declared.

No examples provided.

get_style_sheet_character_edit_status ~115

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Advances the queued character edit, performs the server-side region patch, and returns the revised full Style Sheet image when complete. Call repeatedly until completed or failed. Credits reserved for a failed patch are restored.

NameTypeReqDescription
editIdstringyeseditId returned by create_style_sheet_character_edit.

No output schema declared.

No examples provided.

list_alert_types ~140

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call. Lists the 7 AI Alert types (follow, sub, donation, bits, giftsub, host, raid), the two render tiers (Standard=Veo, Pro=Kling) with their real current credit prices (silent and with audio), and the character-generation price -- all derived live from AlertForge's billing config, never hardcoded. Call this before plan_alert_pack or generate_alert_character.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_overlay_projects ~73

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. List the caller's animated-overlay projects, most recently updated first (up to 20).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_particles ~77

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. List the particle overlay effects that can be Color-Dodge-blended onto a scene (max 4 per scene).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_scene_kinds ~189

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. List every animated-overlay scene kind with metadata (label, whether it animates, whether it's a cam-frame, and whether it's creatable via this agent surface -- with a one-line reason when it isn't). The four sheet-pack kinds (panel-pack, label-pack, sub-badge-pack, emote-pack) also carry `tileInputs` -- their fixed slot count, whether tile labels are locked to fixed vocabulary (sub-badge-pack only), and how the sheet is billed -- pass per-tile overrides for them as `tileTexts` in plan_overlay_pack. This is the single source of truth for scene kinds; never assume or hardcode a kind name.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_alert_pack ~403

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call -- prices a proposed AI Alert pack WITHOUT spending any credits or creating anything. Supports a single alert, a handful, or the full set of 7: pass `alerts` with only the keys you want (e.g. one entry to create just one alert), or omit `alerts` entirely for the full 7-alert pack. Requires `characterImageUrl` -- your own uploaded/generated character (see generate_alert_character). Returns a planId (valid 24 hours, single-use) plus the exact credit cost -- show that to the user and get confirmation before calling create_alert_pack with this planId.

NameTypeReqDescription
alertsarray–Which alerts to include. Omit this field entirely for the full 7-alert pack. If provided, ONLY the keys listed here are created -- e.g. a single {key:"follow"} entry creates exactly one alert. Call l…
captionColorstring–#RRGGBB fill for every alert's on-screen caption text (applies to the whole pack, not per-alert). Falls back automatically if too close to the character's chroma-key colour.
characterImageUrlstringyesYour own character image: the path/url returned by generate_alert_character (once complete) or your own upload, or a safe https:// URL. Required.
generateAudioboolean–Whole-pack audio toggle. Defaults true.
packNamestring–Defaults to 'AI Alert Pack'.
paletteHexesarray–Up to 8 #RRGGBB colours to steer the pack's look.
themestring–Overall visual theme/direction for every alert, up to 400 characters.

No output schema declared.

No examples provided.

plan_design_sheet ~671

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. The FIRST step for any new overlay pack -- prices the pack's shared Style Sheet (design sheet) WITHOUT spending any credits or creating anything. AlertForge's own web builder always asks the streamer these SAME 3 questions, in this order, before generating anything -- ask the USER these exact questions and pass their answers; never invent a theme yourself: (1) "What is your channel name? We use it where your logo or wordmark needs text. Letters, numbers, spaces, - and _ (max 20)." -> channelName. (2) "What should represent your channel? Describe the logo, mascot, character, or symbol you want." -> logoOrCharacterBrief. (3) "What should the overall style feel like? Describe the world, mood, visual style, and any preferred colours." -> themeAndColorsBrief. Returns a planId (valid 24 hours, single-use) plus the exact credit cost -- show that to the user, then call create_design_sheet with this planId. Scenes cannot be planned until the resulting Style Sheet has rendered (get_pack_status) AND been approved (approve_design_sheet).

NameTypeReqDescription
channelNamestringyesThe user's answer to "What is your channel name? We use it where your logo or wordmark needs text. Letters, numbers, spaces, - and _ (max 20).". Required.
detailLevelstring–Art style, a choice of look rather than of quality (the web builder's Flat, Illustrated and 3D). "clean" (Flat): bold, simple flat vector with a hand-made poster look. "detailed" (Illustrated): polis…
logoOrCharacterBriefstringyesThe user's answer to "What should represent your channel? Describe the logo, mascot, character, or symbol you want.". Required.
projectNamestring–Defaults to 'Agent Pack'.
referenceImageUrlstring–An http(s) URL to a reference image (the user's own photo or logo) for the pack. Data URLs are not accepted here.
referenceRolestring–Only meaningful when referenceImageUrl is set. "character" turns the photo into the pack's character, fully redrawn in its art style; "use-as-is" reproduces a logo or character faithfully. Defaults t…
subjectModestring–Whether the described subject becomes a generated character, a generated logo, or is inferred automatically from the brief. Defaults to auto -- mirrors the web builder's Auto/Character/Logo chips.
themeAndColorsBriefstringyesThe user's answer to "What should the overall style feel like? Describe the world, mood, visual style, and any preferred colours.". Required.

No output schema declared.

No examples provided.

plan_overlay_pack ~440

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Normalizes and prices scenes to add to a DESIGN-APPROVED project WITHOUT spending any credits or creating anything. Requires `projectId` from a project whose Style Sheet has been approved via approve_design_sheet -- every scene inherits that project's approved look (visual identity comes entirely from the Style Sheet; there is no theme/reference input here anymore). Calling this without a valid approved projectId returns a structured `design_sheet_required` error (with the product's 3 onboarding questions and the exact tool sequence to follow) instead of guessing a theme -- see plan_design_sheet. Returns a planId (valid 24 hours, single-use) plus the exact credit cost and a human-readable summary -- SHOW that summary and cost to the user and get their confirmation before calling create_overlay_pack with this planId. Call list_scene_kinds first to see which scene kinds are creatable -- including alert-pack, which crops the identity from this project's Style Sheet and creates the selected production overlay alerts, plus the four sheet-pack kinds (panel-pack, label-pack, sub-badge-pack, emote-pack): each sheet kind renders ONE themed sheet and crops it into individual tile PNGs (a Twitch panel set, activity-feed labels, subscriber badges, or channel emotes) -- pass per-tile overrides via `tileTexts` on that scene entry; list_scene_kinds' `tileInputs` reports each kind's exact slot count and whether labels are locked to fixed vocabulary.

NameTypeReqDescription
durationSecnumber–Default animation length in seconds for scenes that don't set their own.
imageQualitystring–Default quality for scenes that don't set their own.
projectIdstringyesA design-approved project id -- from create_design_sheet, after approve_design_sheet has succeeded on it. Required.
scenesarrayyesThe scenes to include. Call list_scene_kinds first -- this tool rejects any kind that isn't creatable.

No output schema declared.

No examples provided.

plan_style_sheet_character_edit ~201

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call. Prices a character-region change on an existing Style Sheet WITHOUT spending credits. Use mode=edit for a small change to the same character; use mode=redesign when replacing it with a new character while preserving the rest of the Style Sheet pixel-for-pixel. Returns a single-use 24-hour plan and exact cost; show the quote and obtain confirmation before create_style_sheet_character_edit.

NameTypeReqDescription
instructionstringyesThe user's exact character-change instruction, up to 1000 characters.
modestring–edit keeps the same identity and changes details; redesign replaces the character. Defaults to redesign.
projectIdstringyesThe existing overlay project whose rendered Style Sheet will be changed.

No output schema declared.

No examples provided.

plan_transparent_video ~368

Requires an approved AlertForge account connection. OAuth-aware clients should start AlertForge's secure authorization flow and ask the user only to sign in and approve. Setup: https://alertforge.ai/ai-agents#agent-setup. Free to call -- prices a single transparent WebM video (a plain animated clip, NOT an AI Alert -- no character chroma-plate, no OBS alert wiring) WITHOUT spending credits or creating anything. Returns a planId (valid 24 hours, single-use) plus the exact credit cost for the chosen model tier -- show that to the user and get confirmation before calling create_transparent_video with this planId.

NameTypeReqDescription
generateAudioboolean–Defaults false. Forced false when modelTier is 'exact'.
includeCenteredSubjectboolean–Defaults true.
includePaletteboolean–Defaults false.
modelTierstring–standard=Kling 3 Standard (default), premium=Veo 3.1 Fast, kling=Kling 3 Pro, exact=animates an uploaded image as-is (requires referenceImageUrl or referenceImagePath, and is always silent).
paletteobject–Optional brand colours. Defaults to AlertForge's standard purple/cyan pair.
promptExtrastringyesThe creative prompt for the video. Required; up to 3400 characters for Standard/Kling (GLM-written shots), 2400 for Premium/Exact.
referenceImagePathstring–Your own reference-images/<you>/... path, or the generated character path returned by get_alert_character_status.
referenceImageUrlstring–A safe https:// reference image URL.
skipBurnTextboolean––
templateNamestring–Defaults to 'Agent Video'.

No output schema declared.

No examples provided.

Install

How do I install the AlertForge MCP server?

AlertForge is a hosted endpoint at https://alertforge.ai/api/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 · alertforge.ai

# add to Claude Code
claude mcp add --transport http lasan713-alertforge 'https://alertforge.ai/api/mcp'
Common questions

What is the AlertForge MCP server?

AlertForge is an MCP server listed in the public MCP registry as io.github.lasan713/alertforge. Create stream overlays, AI alerts, and transparent videos through AlertForge. This page covers its hosted endpoint (https://alertforge.ai/api/mcp).

Is the AlertForge MCP server safe to use?

AlertForge 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 AlertForge MCP server expose?

AlertForge exposes 24 tools: get_product_info, list_scene_kinds, list_particles, get_balance, list_overlay_projects, and 19 more. Their descriptions and schemas cost roughly 4,890 tokens of context every time the server is loaded.

Does the AlertForge MCP server require authentication?

No. We connected to AlertForge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AlertForge MCP server still maintained?

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