RMCP.DEV
← Registry

Security & Testing

alertforge.ai

An MCP server for managing and querying alert configurations and scene types via the AlertForge API.

1 endpoint23 known toolsFirst detected July 29, 2026Last detected July 29, 2026

ENDPOINT 1

https://alertforge.ai/api/mcp

No auth detected

MCP server metadata

Name
alertforge-mcp
Version
1.0.0
Capabilities
tools
Server instructions

AlertForge information + AlertForge for Agents pack tools. get_product_info/get_pricing/get_faq are read-only and unauthenticated. Every other tool requires an AlertForge API key (Authorization: Bearer af_live_...; create one at https://alertforge.ai/dashboard/agents) and can spend the caller's own credit wallet -- call tools/list to see the full set.

Known tools 23

get_product_info

Read-only.

Inferred read-only
get_pricing

Read-only.

Inferred read-only
get_faq

Read-only.

Inferred read-only
list_scene_kinds

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
list_particles

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
get_balance

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
list_overlay_projects

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
plan_design_sheet

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
create_design_sheet

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
approve_design_sheet

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
plan_overlay_pack

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
create_overlay_pack

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
get_pack_status

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
export_pack_zip

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
list_alert_types

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
plan_alert_pack

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
create_alert_pack

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
get_alert_pack_status

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
generate_alert_character

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
get_alert_character_status

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
plan_transparent_video

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
create_transparent_video

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects
get_render_status

Requires an AlertForge API key (create one at https://alertforge.ai/dashboard/agents).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.alertforge-mcp]
url = "https://alertforge.ai/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "alertforge-mcp": {
      "type": "http",
      "url": "https://alertforge.ai/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: alertforge-mcp
Remote MCP URL: https://alertforge.ai/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "alertforge-mcp": {
      "url": "https://alertforge.ai/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "alertforge-mcp": {
      "type": "http",
      "url": "https://alertforge.ai/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "alertforge-mcp",
  "transport": "streamable-http",
  "url": "https://alertforge.ai/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for alertforge.ai was fetched 2026-08-03T19:31:51.622Z and is being refreshed.

Trust status Neutral

alertforge.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.