# app.askqa/structforge

Turn messy text into strict JSON schemas agents can trust (invoice, receipt, contact, resume).

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.0
- **Author:** app.askqa
- **License:** Unknown
- **Endpoints:** streamable-http https://structforge.askqa.app/mcp
- **Source:** https://structforge.askqa.app
- **Endpoint health:** reachable (last checked 2026-09-18T11:50:08.092Z, 4 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-18T11:50:08.092Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

6 declared. Observed from a live `tools/list` probe.
- `structure_text` — Convert messy text to strict JSON schema. Use for emails, chat logs, unstructured input. Schemas: invoice, receipt, contact, resume.
- `parse_invoice` — Parse invoice text into vendor, amount, due_date, line_items (with math_check).
- `extract_table` — Extract HTML or markdown tables into JSON rows.
- `normalize_data` — Normalize data object to a named schema (invoice, receipt, contact, resume).
- `validate_structure` — Validate JSON against a schema. Enforces field presence and types (string/number/date/array).
- `get_schema` — Discover schema shapes. Pass name for one schema, or omit to list all curated schemas.

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"structforge\": {\n      \"type\": \"http\",\n      \"url\": \"https://structforge.askqa.app/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/app.askqa%2Fstructforge
- Install plan: https://forgeregistry.com/api/v1/packages/app.askqa%2Fstructforge/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/app.askqa%2Fstructforge
- HTML page: https://forgeregistry.com/registry/app.askqa%2Fstructforge
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.