# OgForge (remote · ogforge.mike-tusa.workers.dev)

Render 1200x630 Open Graph social preview images from templates; returns a cacheable PNG URL.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `ogforge.mike-tusa.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mike-tusa-ogforge-ogforge/ogforge.md), [page](https://verifymcp.io/servers/dev-workers-mike-tusa-ogforge-ogforge/ogforge)

## Channel facts

- Endpoint: `https://ogforge.mike-tusa.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 629 tokens (~629/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the OgForge MCP server?

OgForge is a hosted endpoint at https://ogforge.mike-tusa.workers.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.

### Claude

```bash
claude mcp add --transport http dev-workers-mike-tusa-ogforge-ogforge 'https://ogforge.mike-tusa.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-ogforge-ogforge": {
      "url": "https://ogforge.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-mike-tusa-ogforge-ogforge": {
      "type": "http",
      "url": "https://ogforge.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mike-tusa-ogforge-ogforge]
url = "https://ogforge.mike-tusa.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-mike-tusa-ogforge-ogforge": {
      "type": "remote",
      "url": "https://ogforge.mike-tusa.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-mike-tusa-ogforge-ogforge --url 'https://ogforge.mike-tusa.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mike-tusa-ogforge-ogforge:
    url: "https://ogforge.mike-tusa.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mike-tusa-ogforge-ogforge": {
      "Transport": "http",
      "Url": "https://ogforge.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mike-tusa-ogforge-ogforge -t streamable-http -u 'https://ogforge.mike-tusa.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-ogforge-ogforge": {
      "type": "http",
      "url": "https://ogforge.mike-tusa.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 70, +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.

### 2026-10-21 (score 69, +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.

### 2026-10-19 (score 68, +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.

### 2026-10-18 (score 67, 0)

- [functional] Server version: 0.2.2 → 0.2.3

### 2026-10-17 (score 67, +1)

- [functional] Server version: 0.2.1 → 0.2.2

### 2026-10-16 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 66)

First indexed and scored.

## MCP tools (1)

### `create_og_image` (~390 tokens)

Create an Open Graph social preview image

Render a 1200x630 PNG Open Graph / social-card image from a template and return its public URL (for og:image and twitter:image tags), size and ready-to-paste meta tags. Templates: blog, launch, docs, minimal, gradient. Optional inline PNG with include_image. Same engine, cache and free-tier limits as GET /api/og. Read-only (renders are cached; nothing is stored about you).

Input parameters:

- `accent` (string): Accent hex color.
- `author` (string): Author or byline. Max 60 characters (longer text is truncated with "…").
- `bg` (string): Background hex color, e.g. 0f172a.
- `emoji` (string): One emoji, e.g. 🚀
- `fg` (string): Text hex color.
- `include_image` (boolean): Also return the PNG inline as MCP image content (default false; usually 30-150 KB).
- `label` (string): Small pill or tag, e.g. "Engineering". Max 40 characters (longer text is truncated with "…").
- `logo` (string): Public https:// URL of a PNG, JPEG or SVG logo (max 512 characters, 300 KB). Fetched by OgForge's server.
- `site` (string): Site or brand name, e.g. "example.dev". Max 60 characters (longer text is truncated with "…").
- `subtitle` (string): Secondary line / description. Max 200 characters (longer text is truncated with "…").
- `template` (string): Layout (default blog).
- `theme` (string): Color scheme (default depends on the template).
- `title` (string, required): Headline, e.g. "How we cut API latency by 60%". Max 120 characters (longer text is truncated with "…").

Output parameters:

- `bytes` (integer)
- `cache` (string): MISS, HIT-MEMORY or HIT-EDGE
- `etag` (string)
- `height` (integer)
- `image_url` (string): Public PNG URL (GET /api/og?...). Use it as og:image / twitter:image.
- `meta_tags` (string): Ready-to-paste og:image / twitter:card meta tags.
- `template` (string)
- `tier` (string)
- `truncated` (array): Fields that were shortened to fit.
- `warning` (string): e.g. logo_fetch_failed: the image rendered without the logo.
- `width` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-mike-tusa-ogforge-ogforge/ogforge#diagnostics

## Score history

- 2026-10-23: 70
- 2026-10-22: 69
- 2026-10-21: 69
- 2026-10-20: 68
- 2026-10-19: 68
- 2026-10-18: 67
- 2026-10-17: 67
- 2026-10-16: 66
- 2026-10-15: 66

## Common questions

### What is the OgForge MCP server?

OgForge is an MCP server listed in the public MCP registry as dev.workers.mike-tusa.ogforge/ogforge. Render 1200x630 Open Graph social preview images from templates; returns a cacheable PNG URL. This page covers its hosted endpoint (https://ogforge.mike-tusa.workers.dev/mcp).

### Is the OgForge MCP server safe to use?

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

OgForge exposes 1 tool: create_og_image. Their descriptions and schemas cost roughly 390 tokens of context every time the server is loaded.

### Does the OgForge MCP server require authentication?

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

### Is the OgForge MCP server still maintained?

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

## Links

- Remote endpoint: https://ogforge.mike-tusa.workers.dev/mcp
- Website: https://ogforge.mike-tusa.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mike-tusa-ogforge-ogforge/ogforge.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mike-tusa-ogforge-ogforge/ogforge.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mike-tusa-ogforge-ogforge/ogforge