MCP Response Normalizer

Store Positioning

Store title: MCP Response Normalizer

Short description: Normalize MCP tool responses into consistent structured records by parsing content blocks, JSON payloads, text responses, attachments, errors, metadata, and schema-mapped output fields.

SEO title: MCP Response Normalizer — API, schema, and developer QA

SEO description: Normalize MCP tool responses into consistent structured records by parsing content blocks, JSON payloads, text responses, attachments, errors, metadata, and schema-mapped output fields. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

Categories: SEO_TOOLS, DEVELOPER_TOOLS

Keywords: mcp, response, normalizer, structured data, schema, data qa, api/developer qa

Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: A1 — API/developer QA
• Primary event: schema-validated at $0.00650 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. MCP Response Normalizer: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• schema-validated: base $0.00650, GOLD $0.00520. MCP Response Normalizer: charged when schema validated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• contract-rule-checked: base $0.00390, GOLD $0.00312. MCP Response Normalizer: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• report-generated: base $0.05000, GOLD $0.04000. MCP Response Normalizer: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Extract MCP Response rows from supplied public inputs
• Inventory MCP Response fields across a capped sample
• Normalize MCP Response evidence for delivery
• Flag missing MCP Response data before delivery
• Export MCP Response records with source URLs

Normalize heterogeneous MCP tool responses into consistent dataset rows. The actor accepts JSON responses, response logs, text responses, expected schemas, and mapping rules, then extracts content blocks, parsed JSON, normalized records, schema validity, error blocks, resource URIs, and attachment metadata.

Inputs

Provide responseJsonInputs, responseLogInputs, textResponses, expectedSchemas, schemaMappings, normalizationMode, extractJsonFromText, includeRawResponse, includeErrorBlocks, maxResponses, maxResponseBytes, and timeoutMs. The defaults are capped so accidental huge logs do not create expensive runs.

Output

Rows include sourceId, toolName, responseIndex, responseType, contentType, contentBlockType, parsedJson, normalizedRecord, schemaValid, fieldPath, errorCode, errorMessage, resourceUri, attachmentName, normalizationWarning, and confidence. KVS reports summarize normalized records, schema failures, and parse warnings.

Billing safety

The actor charges actor-start before analysis, charges the primary PPE event before each dataset row, and charges the report event before writing report artifacts. maxChargeUsd stops work or output gracefully before the configured cap is exceeded.