# MCP Remote Server Endpoint Probe (`junipr/mcp-remote-server-smoke-tester`) Actor

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.

- **URL**: https://apify.com/junipr/mcp-remote-server-smoke-tester.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, Developer tools, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 schema validateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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.

# Actor input Schema

## `serverUrl` (type: `string`):

Remote MCP server URL to probe with the configured safety limits.

## `manifestUrl` (type: `string`):

Optional MCP manifest URL to fetch instead of probing the server endpoint directly.

## `metadataInputs` (type: `array`):

Optional supplied MCP metadata objects to inspect instead of connecting to a remote server.

## `headers` (type: `object`):

Optional request headers for authorized endpoints. Avoid secrets in shared examples and public tasks.

## `safeMode` (type: `boolean`):

Keep probing conservative and avoid optional actions that could mutate remote state.

## `maxTools` (type: `number`):

Maximum tools to process in one run; keep defaults low for safe first runs.

## `callSampleTools` (type: `boolean`):

Controls whether MCP Remote Server Endpoint Probe calls sample tools during the run.

## `timeoutMs` (type: `number`):

Maximum time in milliseconds allowed for the MCP Remote Server Endpoint Probe operation before it is treated as timed out.

## `includeRawMetadata` (type: `boolean`):

Include raw metadata in output rows or reports when available.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE charge allowed for the run before the actor stops gracefully.

## Actor input object example

```json
{
  "serverUrl": "https://mcp.deepwiki.com/mcp",
  "manifestUrl": "",
  "metadataInputs": [],
  "headers": {},
  "safeMode": true,
  "maxTools": 3,
  "callSampleTools": false,
  "timeoutMs": 10000,
  "includeRawMetadata": false,
  "maxChargeUsd": 1
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/mcp-remote-server-smoke-tester").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/mcp-remote-server-smoke-tester").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call junipr/mcp-remote-server-smoke-tester --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/mcp-remote-server-smoke-tester"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/S6n5w79TUsRonIrY9/builds/UFIsPIguhGCAaWL1X/openapi.json