ToolSchema Forge
REMOTE · TOOLSCHEMA-FORGE.TOOLSCHEMAFORGE.WORKERS.DEV
Convert, lint and generate LLM tool schemas for OpenAI, Anthropic, Gemini and MCP
Available components
Last scanned (18 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 4 Nov 26 +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.
- 1 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.
- 30 Oct 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.
- 28 Oct 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.
- 26 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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 65
First indexed and scored.
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 4 Nov 2026 · Probed https://toolschema-forge.toolschemaforge.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=toolschemaforge.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 61d0e51a7d322320b46eb7aea0be33e56e4 |
| SANs: *.toolschemaforge.workers.dev, toolschemaforge.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 insecure
Validation of toolschema-forge.toolschemaforge.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://toolschema-forge.toolschemaforge.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://toolschema-forge.toolschemaforge.workers.dev/mcp | Inconclusive | 405 |
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 →
batch_convert_tool_schemas Batch convert tool schemas ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targets | array | – | Target formats. Default: all. |
| tools | array | yes | 1-50 tool definitions in any supported format. |
No output schema declared.
No examples provided.
convert_tool_schema Convert tool schema ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targets | array | – | Target formats. Default: all. |
| tool | object | yes | Tool definition in any supported format (OpenAI chat/responses, Anthropic, Gemini, MCP, or {name, description, parameters}). |
No output schema declared.
No examples provided.
lint_tool_schema Lint tool schema ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| targets | array | – | Providers to check. Default: all. |
| tool | object | yes | Tool definition in any supported format. |
No output schema declared.
No examples provided.
mcp_manifest MCP manifest + server stub ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
openapi_to_tools OpenAPI to tools ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | Optional operationIds or 'METHOD /path' strings to include. |
| maxTools | integer | – | – |
| spec | object | yes | OpenAPI 3.x or Swagger 2.0 document as JSON. |
| target | string | – | Output format. Default openai. |
No output schema declared.
No examples provided.
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.
remote · toolschema-forge.toolschemaforge.workers.dev
claude mcp add --transport http dev-workers-toolschemaforge-toolschema-forge-too 'https://toolschema-forge.toolschemaforge.workers.dev/mcp'
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.