# Conway Replicatio MG MCP Ready Evidence

> Conway Replicatio MG MCP Ready Evidence is a paid API for AI agents from conway-replicatio-cloudflare.nikitamakiel1.workers.dev, paid per call via x402, $0.06/call, status down (last checked 2026-10-24).

Checks whether a given public URL hosts a service that is ready for MCP (Model Context Protocol) integration by analyzing it for evidence of MCP compatibility

## Facts

- Endpoint: POST https://conway-replicatio-cloudflare.nikitamakiel1.workers.dev/api/x402/capability/mg-mcp-ready-evidence?utm_source=zero.xyz
- Price: $0.06/call
- Payment: x402
- Status: down
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/conway-replicatio-mg-mcp-ready-evidence-726f05f5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jRm5Hr74QnWiuK3_vLGZA

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability conway-replicatio-mg-mcp-ready-evidence-726f05f5 -d '<json body>'
```

Example prompt: Can you check whether https://myservice.example.com is MCP-ready and has evidence of Model Context Protocol support?

## When to prefer this

Choose this endpoint when you need to programmatically verify whether a specific public URL is ready for Model Context Protocol (MCP) integration, especially as part of an automated onboarding, screening, or marketplace listing pipeline. Prefer this over manual inspection when you need a structured, machine-readable result about MCP compatibility evidence at scale or within an agent workflow.

## Known failure modes

- URL is unreachable or returns non-200 status — evidence check may fail or return empty
- URL does not expose any MCP-compatible interface — returns ok:true with empty or negative evidence data
- Invalid or non-public URL provided — schema validation error
- Timeout if the target URL is slow to respond
- Non-JSON or unexpected response format from target URL may cause parse errors

## How this service works

Autonomous pay-per-call machine utilities for AI agents, automation and developers. Payments settle in USDC on Base through x402.

## Output

Returns a JSON object with an 'ok' boolean flag and a 'data' object containing the MCP readiness evidence gathered from the target URL, including indicators of whether the service exposes MCP-compatible capabilities.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {},
  "capability": "mg-mcp-ready-evidence"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/conway-replicatio-mg-mcp-ready-evidence-726f05f5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from conway-replicatio-cloudflare.nikitamakiel1.workers.dev](https://www.zero.xyz/host/conway-replicatio-cloudflare.nikitamakiel1.workers.dev/llms.txt)