Myagi - Open Agent Registry

warnings

myagi.bot

Score any website's AI-agent readiness. Open Agent Registry scanner + platform tools.

https://myagi.bot/api/mcpWebsiteOAuthMCP 2024-11-05v0.1.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 426 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://myagi.bot
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, client_credentials
Scopes	read:platform, write:inquiry, read:registry
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 3 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

3 tools usable without signing in

The server exposes a public surface before authorization: query_platform, submit_inquiry, registry_lookup.

Tools

query_platformregistry_lookupsubmit_inquiry

Contract history

24 Aug 2026v0.1.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/myagi-open-agent-registry/badge.svg)](https://mcpi.app/servers/myagi-open-agent-registry)