Myagi - Open Agent Registry

bot.myagiPublished by myagi.botOfficial publisherv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Remote MCP server for the Myagi Open Agent Registry that scores a domain's AI-agent readiness and returns platform info or submits inquiries.

What you can do
  • Look up a domain's agent-readiness score and full profile (signals, score, label, approval path)
  • Query Myagi platform details: current phase, milestones, conceptual model and public roadmap
  • Submit a contact inquiry on the operator's behalf and receive an inquiry ID
When to use it
Useful when an assistant needs to judge whether a website or service is ready for agent access before calling it, or wants the registry's approval-path checklist. Also for checking Myagi platform status or sending a contact inquiry.
Requirements
A remote streamable HTTP endpoint at myagi.bot; no packages, environment variables, headers or authentication are declared. Network access to the endpoint is required.
Before you install
The inquiry tool sends a message to the operator's contact address on the user's behalf, so confirm before submitting. Lookups are proxied to the registry's scan API, so the domains queried are shared with that service. The registry is described as pre-alpha, so scores and data may be incomplete or change.

Installation

In SourceWeft

  1. Open Myagi - Open Agent Registry in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/bot.myagi%2Fopenagent-registry/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "myagi-open-agent-registry": {
      "type": "http",
      "url": "https://myagi.bot/api/mcp"
    }
  }
}

README

OpenAgent Registry

The open registry, scanner, and leaderboard for agent-ready websites and services.

OpenAgent Registry (OAR) does three things in one place:

  1. Scans any URL for the full stack of agent-access signals - llms.txt, agents.txt / agents.json, AGENTS.md, .well-known/agent-card.json, robots.txt + Content Signals, OpenAPI, OAuth discovery, RSL licensing, MCP/A2A registry presence - and aggregates upstream registries instead of re-doing their work.
  2. Scores each site against a transparent, public rubric and ranks it within its industry category.
  3. Tells you what to do about it - a concrete approval-path checklist with deep links to the actual developer applications, OAuth signups, partner programs, and standards-adoption steps. Lead with the checklist; the score is supporting evidence.

Sources of authoritative scoring credit (registries / standards bodies):

Community resources used for domain discovery only (no score credit; we use these to know which sites to scan):

What OAR adds that none of the above does today:

  • Comparative leaderboards by industry category (rentals, shopping, content, social, developer)
  • Approval-path generator - concrete next steps, not just "you have OAuth"
  • Aggregation across the full stack in one report
  • Change monitoring over time
  • A public, free API so agents (including your own) can query it before calling external services

Status

Pre-alpha but live. Public deploy: https://openagent-registry.vercel.app.

After the v0.1 import, the registry tracks 1,400+ services across 6 industry categories, sourced from the original seed plus an import of llms-txt-hub. Every service has a live score, a label, and a generated approval-path checklist. Looking for contributors - especially for approval-path data per service (the moat).

Stack

  • Next.js 15 (App Router) + TypeScript + Tailwind CSS
  • No backend service in v0 - Next.js API routes do the scanning
  • Local JSON cache for MVP; Postgres or Vercel KV for production scale
  • Deploys natively to Vercel

Quickstart

bash
pnpm installpnpm dev

Then open http://localhost:3000.

How scoring works

See docs/rubric.md. Every signal is weighted, every weight is published, every score is reproducible from the JSON profile. No black-box scoring.

The current rubric (summary):

SignalPoints
Official MCP server in MCP Registry+25
A2A Agent Card found+25
agents.json (root or .well-known)+15
OpenAPI spec found+15
Web Bot Auth / signed-agent support+15
Official developer docs+10
Partner / approval path documented+10
OAuth/OIDC discovery+10
agents.txt standard+10
llms.txt+8
AGENTS.md+8
RSL / licensing manifest+8
robots.txt allows docs/API+5
Cloudflare Content Signals present+5
llms-full.txt (extended)+5
Listed in llms-txt-hub+5
Listed in Agent Friendly Directory+5
ai-plugin.json (deprecated signal)+2
Explicit bot/agent prohibition-50
Blocks automation, no API alternative-30
Unknown terms / can't parse-10

Labels:

ScoreLabel
80–100Agent-ready
60–79Agent-friendly
40–59Partially agent-accessible
20–39API-only / limited
0–19Unknown
<0Likely blocked

Categories

  • Rentals & Travel - Airbnb, Booking, Hertz, Avis, Enterprise, Expedia, Vrbo, AutoRentals
  • Shopping & Commerce - Amazon, Shopify, Stripe, Target, Walmart, BestBuy, Etsy
  • Content & News - NYT, WaPo, Bloomberg, Reuters, Substack, Medium
  • Social & Community - Reddit, X, LinkedIn, Bluesky, Mastodon, Discord
  • Developer Platforms - GitHub, Vercel, Cloudflare, npm, AWS, plus 800+ dev tools from the upstream import
  • AI & ML Platforms - Anthropic, OpenAI, and 500+ AI/ML platforms publishing llms.txt

Within each category, services are ranked by their AgentRank score. The category page is the SEO-friendly editorial surface: "Top agent-ready rental sites, [month] [year]".

Contributing

See CONTRIBUTING.md. The three highest-leverage contributions today:

  1. Add services to data/seed.json (a category, a homepage URL, optional notes) - opens a PR; CI runs a scan against it.
  2. Tighten parsers for the well-known files. The MVP parsers are intentionally conservative - better parsers raise the data quality for everyone.
  3. Approval-path data - concrete next-step instructions per service (developer signup URL, OAuth scopes needed, partner-program form). This is the killer feature; quality is the moat.

License

Apache 2.0.

Source: README.md at commit ff34411

Tools

3

query_platform

Returns structured information about the Myagi platform: current phase, milestones, conceptual model, and public roadmap.

Parameterstopic

submit_inquiry

Submit a contact inquiry on behalf of the calling agent's operator. Forwards to [email protected]. Returns an inquiry ID on success.

Parametersnamerequiredemailrequiredmessagerequired

registry_lookup

Look up a domain's agent-readiness score in the Open Agent Registry. Proxies to /open-agent-registry/api/scan. Returns the full Profile (signals, score, label, approval_path).

Parametersdomainrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts