MCP Remote Server Endpoint Probe

Store Positioning

Store title: MCP Remote Server Endpoint Probe

Short description: Run a safe bounded endpoint readiness check against an MCP server endpoint or manifest and report whether the server responds, exposes usable tools, and returns sane metadata.

SEO title: MCP Remote Server Endpoint Probe — API, schema, and developer QA

SEO description: Run a safe bounded endpoint readiness check against an MCP server endpoint or manifest and report whether the server responds, exposes usable tools, and returns sane metadata. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

Categories: SEO_TOOLS, DEVELOPER_TOOLS, ECOMMERCE

Keywords: mcp, remote, server, smoke, tester, 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 Remote Server Smoke Tester: 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 Remote Server Smoke Tester: 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 Remote Server Smoke Tester: 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 Remote Server Smoke Tester: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

The actor accepts actor-start before work, accepts the primary event before each dataset row, and accepts report-generated before writing report files. If maxChargeUsd or the live PPE limit blocks a charge, the corresponding row or report is not written.

Public Task Concepts

• Audit MCP Remote Server Endpoint Probe controls on a capped public sample
• Find high-priority MCP Remote Server Endpoint Probe issues before release
• Validate MCP Remote Server Endpoint Probe evidence from supplied pages
• Prioritize MCP Remote Server Endpoint Probe fixes with severity and proof
• Export MCP Remote Server Endpoint Probe QA rows for client review Run safe bounded MCP server metadata smoke checks.

What It Does

Uses supplied metadata or a bounded endpoint fetch to inspect connection status, protocol shape, listed tools, descriptions, input/output schemas, and safe sample-call status.

Inputs

This actor exposes these input fields in .actor/input_schema.json:

• serverUrl
• manifestUrl
• headers
• safeMode
• maxTools
• callSampleTools
• timeoutMs
• includeRawMetadata
• maxChargeUsd

The exact default sends a read-only MCP tools/list request to DeepWiki's public Streamable HTTP endpoint, parses its SSE response, and caps output to three tools; the endpoint was verified at 2026-07-12T05:30:00Z.

Outputs

Dataset rows contain:

• serverUrl
• connectionStatus
• protocolStatus
• toolName
• toolListed
• descriptionPresent
• inputSchemaPresent
• outputSchemaPresent
• safeCallStatus
• error
• recommendation

Sample outputs in examples/output.sample.json and output.sample.json were generated from examples/input.tiny.json through actor logic.

Reports

After the report-generated charge is accepted, the actor writes its Markdown, JSON, or CSV reports to the key-value store. A rejected report charge leaves those files unwritten.

Public Task Concepts

• Validate MCP Remote Server Endpoint Probe before release
• Run a bounded MCP Remote Server Endpoint Probe QA check
• Generate developer QA evidence for MCP Remote Server Endpoint Probe

Safe use

Use small capped runs first. Network paths are bounded; review output quality and costs before increasing limits.