_ registry / mcp streamable-http · checked 1h ago

toolschema-forge

https://toolschema-forge.toolschemaforge.workers.dev

Registry code: 794b9f89e442561d

api record

ToolSchema Forge converts and lints LLM tool/function schemas across OpenAI (incl. strict), Anthropic, Gemini and MCP, turns OpenAPI specs into tools, and generates MCP manifests. Deterministic, no LLM inside. Free tier: 5 tool calls per hour per IP, arguments up to 8 KB. Beyond that, pay per call in USDC on Base with x402 (MCP convention: params._meta["x402/payment"]), or call the paid HTTP routes listed at /openapi.json.

endpoint
https://toolschema-forge.toolschemaforge.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is toolschema-forge live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is toolschema-forge free to use?
Yes — the hub reached it with no key and no payment.
What tools does toolschema-forge have?
5 tools: lint_tool_schema, openapi_to_tools, mcp_manifest, batch_convert_tool_schemas, convert_tool_schema.
Is toolschema-forge safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
162ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 6 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
10

last 2026-10-26

received on chain
7.457 USDC

counted from three payers (thin, concentrated)

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • lint_tool_schema unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tool"
  ],
  "properties": {
    "tool": {
      "type": "object",
      "description": "Tool definition in any supported format."
    },
    "targets": {
      "type": "array",
      "items": {
        "enum": [
          "openai",
          "openai_strict",
          "anthropic",
          "gemini",
          "mcp",
          "jsonschema"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Providers to check. Default: all."
    }
  }
}
    arguments 28 lines
  • openapi_to_tools unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "spec"
  ],
  "properties": {
    "spec": {
      "type": "object",
      "description": "OpenAPI 3.x or Swagger 2.0 document as JSON."
    },
    "target": {
      "enum": [
        "openai",
        "openai_strict",
        "anthropic",
        "gemini",
        "mcp",
        "jsonschema"
      ],
      "type": "string",
      "description": "Output format. Default openai."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional operationIds or 'METHOD /path' strings to include."
    },
    "maxTools": {
      "type": "integer",
      "maximum": 128,
      "minimum": 1
    }
  }
}
    arguments 36 lines
  • mcp_manifest unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "tools": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "Tool definitions in any supported format. Give this or openapi."
    },
    "server": {
      "type": "object",
      "properties": {
        "name": {
          "type": "string"
        },
        "version": {
          "type": "string"
        },
        "description": {
          "type": "string"
        }
      },
      "description": "Optional server info overrides."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional operationIds or 'METHOD /path' strings to include (openapi input)."
    },
    "openapi": {
      "type": "object",
      "description": "OpenAPI 3.x or Swagger 2.0 document as JSON. Give this or tools."
    }
  }
}
    arguments 40 lines
  • batch_convert_tool_schemas unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tools"
  ],
  "properties": {
    "tools": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "maxItems": 50,
      "minItems": 1,
      "description": "1-50 tool definitions in any supported format."
    },
    "targets": {
      "type": "array",
      "items": {
        "enum": [
          "openai",
          "openai_strict",
          "anthropic",
          "gemini",
          "mcp",
          "jsonschema"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Target formats. Default: all."
    }
  }
}
    arguments 33 lines
  • convert_tool_schema unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tool"
  ],
  "properties": {
    "tool": {
      "type": "object",
      "description": "Tool definition in any supported format (OpenAI chat/responses, Anthropic, Gemini, MCP, or {name, description, parameters})."
    },
    "targets": {
      "type": "array",
      "items": {
        "enum": [
          "openai",
          "openai_strict",
          "anthropic",
          "gemini",
          "mcp",
          "jsonschema"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Target formats. Default: all."
    }
  }
}
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 794b9f89e442561d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/794b9f89e442561d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/794b9f89e442561d/badge.svg)](https://brick.blue/agent/794b9f89e442561d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.