Turn messy text into strict JSON schemas agents can trust (invoice, receipt, contact, resume).
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://structforge.askqa.app/mcp6 tools · 413msstructure_textConvert messy text to strict JSON schema. Use for emails, chat logs, unstructured input. Schemas: invoice, receipt, contact, resume.Convert messy text to strict JSON schema. Use for emails, chat logs, unstructured input. Schemas: invoice, receipt, contact, resume.
| Parameter | Type | Description |
|---|---|---|
| text* | string | Raw text to structure |
| schema_name | string | Target schema: invoice, receipt, contact, resume |
parse_invoiceParse invoice text into vendor, amount, due_date, line_items (with math_check).Parse invoice text into vendor, amount, due_date, line_items (with math_check).
| Parameter | Type | Description |
|---|---|---|
| text* | string | Invoice text or PDF extract |
extract_tableExtract HTML or markdown tables into JSON rows.Extract HTML or markdown tables into JSON rows.
| Parameter | Type | Description |
|---|---|---|
| html* | string | HTML or table content |
normalize_dataNormalize data object to a named schema (invoice, receipt, contact, resume).Normalize data object to a named schema (invoice, receipt, contact, resume).
| Parameter | Type | Description |
|---|---|---|
| data* | object | Input data object |
| target_schema* | string | Target schema name |
validate_structureValidate JSON against a schema. Enforces field presence and types (string/number/date/array).Validate JSON against a schema. Enforces field presence and types (string/number/date/array).
| Parameter | Type | Description |
|---|---|---|
| data* | object | — |
| schema_name* | string | — |
get_schemaDiscover schema shapes. Pass name for one schema, or omit to list all curated schemas.Discover schema shapes. Pass name for one schema, or omit to list all curated schemas.
| Parameter | Type | Description |
|---|---|---|
| name | string | Schema name; omit to list all |
6 of 6 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Turn messy text into strict JSON schemas agents can trust (invoice, receipt, contact, resume).
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.