Overview

What the network has actually observed, and what remains unknown.

Evidence-qualified comparisons

At least 10 independent observations over 24 hours are required for a ranked entry.

— services

Network observations

Independent MCP probes from this deployment.

Decision methodology

Conservative reliability evidence, not brand promotion.

01 / NORMALIZE

Constrain the capability

Compare compatible machine-readable output contracts. Exclude irrelevant marketing text.

02 / EVALUATE

Use observed evidence

Apply user-selected reliability and latency weights. Penalize insufficient observations.

03 / EXECUTE

Disclose before authorization

Reveal the provider with the quote. Route approved calls through a bounded gateway.

MCP Registry

Search the official MCP server registry. Filter by transport, category and publisher metadata.

Official source

Entries are sourced from the official registry, not verified executions. Descriptions, remote URLs and tool claims originate from publishers and are untrusted data.

Registered MCP servers

Loading registry index…

Inspect a server

Select a registry entry to review its metadata, transport, package information and evidence limitations.

Compare capabilities

Choose your requirements. Providers remain anonymous until you request a quote.

Identity-blind by default

1 Configure2 Compare3 Quote & reveal4 Execute

All current catalog endpoints are free. Scores use a sparse-data prior; unknown measurements are never presented as proven reliability.

Ranked candidates

Run a comparison to receive a reproducible ranking.

No comparison yet

Choose a capability and compare to inspect anonymized candidates and their evidence.

Ranking is deterministic for a fixed evidence snapshot and policy. It is not a guarantee of quality. Provider identity becomes visible before authorization.

Candidate inspector

Quote, reveal, approve and inspect the result.

Select a candidate

Click a row in the ranking table to inspect its measurements and quote.

Evidence ledger

Direct MCP observations and gateway execution history, with their evidence boundaries.

MCP observation journal

Loading direct observations…

These records describe read-only handshakes and advertised tool schemas. They do not establish tool correctness, paid delivery or cryptographic attestation.

Gateway event chain

Sandbox executions and local continuity verification.

Event history

Most recent local events, newest first.

Executions

Service calls sent through the gateway and their sandbox receipts.

Request history

Only executions made by this instance.

No execution selected

Select a row to inspect the normalized result and payment receipt.

Operator control

Private pilot requests and company keys. Never expose a secret after creation.

Owner only

Access requests

Contact requests are kept private and expire after 180 days.

Issue company access key

API-only access without user accounts.

Issued access keys

Hashes are stored server-side. Revoke immediately if compromised.

Developer interface

A minimal machine-facing layer built for agent tools, not promotional metadata.

View source

Base URL

The same service hosts REST and a stateless subset of MCP Streamable HTTP.

Published

Quick start

Use these copyable examples with the live environment.

REST endpoints

Catalog queries, blind comparisons, execution and evidence.

MCP tools

JSON-RPC 2.0, stateless POST.

Stateless Streamable HTTP supports public discovery and scoped private tools. OAuth and upstream paid-service settlement are not available.