mcp-registry/app.askqa/structforge · v1.1.0
As of 2026-10-26 17:07 UTC, the Askqa Structforge MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 14 minutes.
Turn messy text into strict JSON schemas agents can trust (invoice, receipt, contact, resume).
Point your MCP client at this streamable-http endpoint: https://structforge.askqa.app/mcp
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.askqa%2Fstructforge/fixes
{
"name": "get_schema",
"description": "Discover schema shapes. Pass name for one schema, or omit to list all curated schemas.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"name": {
"type": "string",
"description": "Schema name; omit to list all"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "validate_structure",
"description": "Validate JSON against a schema. Enforces field presence and types (string/number/date/array).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"data",
"schema_name"
],
"properties": {
"data": {
"type": "object",
"additionalProperties": {}
},
"schema_name": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.askqa/structforge"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.askqa/structforge"}) over MCP.
structure_text ~140 tokensnormalize_data ~122 tokensvalidate_structure ~107 tokensparse_invoice ~94 tokensget_schema ~90 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.askqa%2Fstructforge?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.askqa%2Fstructforge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.askqa%2Fstructforge.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.askqa%2Fstructforge.svg :target: https://glimind.com/server/mcp-registry%2Fapp.askqa%2Fstructforge?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c2848f08034e69cb…, first seen 2026-10-17, included at leaf 16629 of 74,305. Version history · verify what your client received.
Compare: most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:07 UTC, the Askqa Structforge MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 14 minutes.
Askqa Structforge MCP server advertises 6 tools, including extract_table, get_schema, normalize_data, parse_invoice, structure_text.
Point your MCP client at this streamable-http endpoint: https://structforge.askqa.app/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.