Relay — agent service discovery

Name: Relay — agent service discovery
Author: site.chatgpt.orellise.relay-agent-services

MCP serverMCP

Discover agent services, compare sourced capabilities and inspect connection evidence. No execution.

by site.chatgpt.orellise.relay-agent-serviceshomepage ↗v0.11.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"relay-agent-service-discovery","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability (some checks stopped at authentication)33/34 checks ok

Some successful checks reached the service and some stopped at an authentication response; figures combine both.

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	170 ms	server relay 0.11.0 · protocol 2025-06-18 · 14 tools
10 h ago	mcp initialize	ok	200	333 ms	server relay 0.11.0 · protocol 2025-06-18 · 14 tools
17 h ago	mcp initialize	ok	200	188 ms	server relay 0.11.0 · protocol 2025-06-18 · 14 tools
24 h ago	mcp initialize	ok	200	110 ms	server relay 0.11.0 · protocol 2025-06-18 · 14 tools
30 h ago	mcp initialize	ok	200	132 ms	server relay 0.11.0 · protocol 2025-06-18 · 14 tools
2 d ago	mcp initialize	ok	200	498 ms	server relay 0.11.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	194 ms	server relay 0.11.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	169 ms	server relay 0.11.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	191 ms	server relay 0.11.0 · protocol 2025-06-18 · 13 tools
3 d ago	mcp initialize	ok	200	1658 ms	server relay 0.11.0 · protocol 2025-06-18 · 13 tools

Tools observed via MCP handshake

run_discovery_workflow — Preferred default for multi-step service discovery. One fixed read-only discovery workflow, inspired by Code Mode. Send requestJson containing mode recommend/ca
search_llm_providers — Read dated official-documentation observations for LLM providers. Optional query uses literal metadata terms; planType distinguishes free-tier, evaluation, recu
search_discovered_services — Read the separate, automatically collected Official MCP Registry index. Send requestJson containing query, limit and offset. Literal substring matching over nam
get_service_evidence — Read the published evidence for one current service. Source review, observed provider response and internal task review are separate. Inspect observation dates,
find_service_alternatives — Read-only alternatives. Send the original complete requestJson used for recommend_services and excludedProviders (1–20 distinct service slugs). Preserves all ta
recommend_services — Full standalone recommendation response. Prefer run_discovery_workflow when a shortlist with evidence, connection details or comparison is needed; use this tool
get_benchmark_suite — Read 20 predefined public-documentation task cases across English, Turkish, German and Spanish, with source URLs and review rubrics. Five task families have fou
plan_benchmark — Plan a predefined benchmark case without running it. Read get_benchmark_suite for a caseId, then send requestJson containing {caseId,constraints?:{maxTaskCostUs
search_services — Find services using deterministic keywords, bounded language aliases and category/protocol/pricing filters. Prefer requestJson (at most 8192 UTF-16 code units):
get_service — Read one full catalogue entry, including documentation links, pricing caveats and source check date. Does not connect to the provider.
compare_services — Retrieve 2–3 selected catalogue entries for comparison. Does not test providers or infer performance from their listing.
get_connection_spec — Read recorded endpoint, declared interfaces, authentication method, setup gaps and source evidence. Transport can come from matching Registry evidence or an exa
get_connection_handoff — Read a reviewed host-managed connection plan for Exa, Jina or Browserless. Only provider is accepted. Returns official endpoints, authentication method, setup s
get_task_options — Plan an optional keyless task without contacting a provider. Send requestJson containing only task (web_search, read_page, pdf_parse or browser_screenshot), inp

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrysite.chatgpt.orellise.relay-agent-services/relay

first seen 10 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

10 d ago · declared · summary → "Discover agent services, compare sourced capabilities and inspect connection evidence. No execution."
10 d ago · declared · description → "Discover agent services, compare sourced capabilities and inspect connection evidence. No execution."
10 d ago · declared · publisherName → "site.chatgpt.orellise.relay-agent-services"
10 d ago · declared · homepageUrl → "https://relay-agent-services.orellise.chatgpt.site/start"
10 d ago · declared · version → "0.11.0"
10 d ago · declared · protocols → ["mcp"]

Relay — agent service discovery

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from