# neo mcp-check

> neo mcp-check is a paid API for AI agents from neo-collettive.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Performs a read-only safety and sanity audit of a public MCP endpoint: DNS/SSRF checks, TLS validation, protocol handshake, tools listing, and latency measurement, returning a signed and logged result.

## Facts

- Endpoint: POST https://neo-collettive.onrender.com/x402/mcp-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/neo-mcp-check-b7ded2e9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SGUEiAtwVINoAD0wPf_RN

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 neo-mcp-check-b7ded2e9 -d '<json body>'
```

Example prompt: Can you do a safety check on the MCP server at https://example-mcp.onrender.com — check its DNS, TLS, and tool list, and give me a signed result I can trust?

## When to prefer this

Use this endpoint when you need a read-only, signed, and logged safety audit of a public MCP server before connecting an agent to it. It is specifically designed for MCP protocol validation (DNS/SSRF, TLS, initialize handshake, tools/list) and never calls remote tools, making it safe for pre-flight checks. Prefer it over generic HTTP health checks when you need MCP-aware protocol validation and a cryptographically signed result for audit trails or registry compliance.

## Known failure modes

- URL is unreachable or DNS does not resolve — returns ok:false with a network error detail
- SSRF safety check flags the URL as a private/reserved IP range — request blocked with safety error
- TLS certificate invalid or expired — returns ok:false with TLS failure detail
- MCP server fails to respond to initialize handshake — returns ok:false with protocol error
- tools/list returns malformed or empty response — flagged in sanity check results
- Target server times out — latency measurement included with a timeout status

## How this service works

Read-only check of a public MCP endpoint: DNS/SSRF safety, TLS, initialize, tools/list sanity, latency. Never calls remote tools. Signed, logged result.

## Output

A JSON object with an 'ok' boolean indicating overall pass/fail, the number of tools discovered via tools/list, a cryptographic signature for the result, and additional fields covering DNS/SSRF safety status, TLS validity, latency measurement, and log position for auditability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "registry_name": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tools": 3,
  "signature": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/neo-mcp-check-b7ded2e9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from neo-collettive.onrender.com](https://www.zero.xyz/host/neo-collettive.onrender.com/llms.txt)