# ToolSchema Forge (remote · toolschema-forge.toolschemaforge.workers.dev)

Convert, lint and generate LLM tool schemas for OpenAI, Anthropic, Gemini and MCP

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

## Components

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

## Channel facts

- Endpoint: `https://toolschema-forge.toolschemaforge.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-04.

- **Endpoint Security**: 63/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 722 tokens (~144/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ToolSchema Forge MCP server?

ToolSchema Forge is a hosted endpoint at https://toolschema-forge.toolschemaforge.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-toolschemaforge-toolschema-forge-too 'https://toolschema-forge.toolschemaforge.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-toolschemaforge-toolschema-forge-too": {
      "url": "https://toolschema-forge.toolschemaforge.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-toolschemaforge-toolschema-forge-too": {
      "type": "http",
      "url": "https://toolschema-forge.toolschemaforge.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-toolschemaforge-toolschema-forge-too]
url = "https://toolschema-forge.toolschemaforge.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-toolschemaforge-toolschema-forge-too": {
      "type": "remote",
      "url": "https://toolschema-forge.toolschemaforge.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-toolschemaforge-toolschema-forge-too --url 'https://toolschema-forge.toolschemaforge.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-toolschemaforge-toolschema-forge-too:
    url: "https://toolschema-forge.toolschemaforge.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-toolschemaforge-toolschema-forge-too": {
      "Transport": "http",
      "Url": "https://toolschema-forge.toolschemaforge.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-toolschemaforge-toolschema-forge-too -t streamable-http -u 'https://toolschema-forge.toolschemaforge.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-toolschemaforge-toolschema-forge-too": {
      "type": "http",
      "url": "https://toolschema-forge.toolschemaforge.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-11-04 (score 70, +1)

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

### 2026-11-01 (score 69, +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-30 (score 68, +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-28 (score 67, +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-26 (score 66, +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.

### 2026-10-25 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 65)

First indexed and scored.

## MCP tools (5)

### `convert_tool_schema` (~133 tokens)

Convert tool schema

Convert one LLM tool/function definition between OpenAI, OpenAI strict mode, Anthropic, Gemini, MCP and plain JSON Schema. The input format is auto-detected. Every change is reported as an issue with a JSON pointer. Free: 5 calls/hour per IP with arguments up to 8 KB; then $0.01 USDC per call via x402.

Input parameters:

- `targets` (array): Target formats. Default: all.
- `tool` (object, required): Tool definition in any supported format (OpenAI chat/responses, Anthropic, Gemini, MCP, or {name, description, parameters}).

### `lint_tool_schema` (~97 tokens)

Lint tool schema

Check one LLM tool definition against each provider's schema rules (OpenAI strict, Anthropic, Gemini, MCP) and report errors and warnings with fixes. Free: 5 calls/hour per IP with arguments up to 8 KB; then $0.005 USDC per call via x402.

Input parameters:

- `targets` (array): Providers to check. Default: all.
- `tool` (object, required): Tool definition in any supported format.

### `openapi_to_tools` (~133 tokens)

OpenAPI to tools

Turn an OpenAPI 3.x or Swagger 2.0 spec (JSON object) into LLM tool definitions in the chosen format, one tool per operation. Free: 5 calls/hour per IP with arguments up to 8 KB; then $0.02 USDC per call via x402.

Input parameters:

- `include` (array): Optional operationIds or 'METHOD /path' strings to include.
- `maxTools` (integer)
- `spec` (object, required): OpenAPI 3.x or Swagger 2.0 document as JSON.
- `target` (string): Output format. Default openai.

### `batch_convert_tool_schemas` (~94 tokens)

Batch convert tool schemas

Convert up to 50 tool definitions at once to the chosen formats, with per-tool issues and ready-to-use bundles. Free: 5 calls/hour per IP with arguments up to 8 KB; then $0.05 USDC per call via x402.

Input parameters:

- `targets` (array): Target formats. Default: all.
- `tools` (array, required): 1-50 tool definitions in any supported format.

### `mcp_manifest` (~155 tokens)

MCP manifest + server stub

Generate an MCP server manifest (tools with inputSchema, titles, annotations, HTTP bindings) and a TypeScript stdio server stub from an OpenAPI spec or a list of tools. Free: 5 calls/hour per IP with arguments up to 8 KB; then $0.15 USDC per call via x402.

Input parameters:

- `include` (array): Optional operationIds or 'METHOD /path' strings to include (openapi input).
- `openapi` (object): OpenAPI 3.x or Swagger 2.0 document as JSON. Give this or tools.
- `server` (object): Optional server info overrides.
- `tools` (array): Tool definitions in any supported format. Give this or openapi.

## Diagnostics

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

## Score history

- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 68
- 2026-10-30: 68
- 2026-10-29: 67
- 2026-10-28: 67
- 2026-10-27: 66
- 2026-10-26: 66
- 2026-10-25: 65
- 2026-10-24: 65

## Common questions

### What is the ToolSchema Forge MCP server?

ToolSchema Forge is an MCP server listed in the public MCP registry as dev.workers.toolschemaforge.toolschema-forge/toolschema-for…. Convert, lint and generate LLM tool schemas for OpenAI, Anthropic, Gemini and MCP. This page covers its hosted endpoint (https://toolschema-forge.toolschemaforge.workers.dev/mcp).

### Is the ToolSchema Forge MCP server safe to use?

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

ToolSchema Forge exposes 5 tools: convert_tool_schema, lint_tool_schema, openapi_to_tools, batch_convert_tool_schemas, mcp_manifest. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.

### Does the ToolSchema Forge MCP server require authentication?

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

### Is the ToolSchema Forge MCP server still maintained?

ToolSchema Forge 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.

## Links

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