Aiaam

io.github.javierfajardo85-rgbPublished by GitHub account javierfajardo85-rgbv1.0.0Updated Oct 24, 2026

MAI-1 registry: search 100+ verified AI tool contracts with live reliability scores in one call.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Remote MCP registry that lets an assistant search 100+ verified AI tool contracts with install commands, I/O schemas and reliability scores.

What you can do
  • Search the tool catalog by keyword and browse trending tools
  • Retrieve a full contract for one tool, including install and execute commands, input/output schemas and source link
  • Fetch the API manifest and compile an API description from the catalog
  • Optionally report anonymous execution feedback that feeds reliability scores
When to use it
Useful when an assistant has to choose a library or tool for a task and you want structured contracts instead of parsing READMEs or web search results. Also handy for checking a tool's maintenance-based reliability score before adopting it.
Requirements
A remote MCP endpoint at over HTTP transport; no authentication, API keys or environment variables are declared. Network access is required.
Before you install
The catalog is in active development and its reliability scores are derived from public repository metadata, so treat them as indicative rather than authoritative. Optional telemetry posts execution feedback (HTTP status, latency) without authentication; it is described as anonymous and optional, but it does send data to a third party.

Installation

In SourceWeft

  1. Open Aiaam 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/io.github.javierfajardo85-rgb%2Faiaam/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": {
    "aiaam": {
      "type": "http",
      "url": "https://aiaam.xyz/mcp"
    }
  }
}

README

aiaam.xyz — MAI-1 Tool Registry

A machine-readable tool catalog for AI agents. Search 100+ verified tool contracts — install command, I/O schema, live reliability score — in a single call instead of parsing READMEs.

[MCP Registry] [API]

The problem

When an AI agent needs to pick a tool ("which library do I use for web scraping?"), today it searches the web and parses README files — thousands of tokens per candidate, with no reliability data and plenty of room to hallucinate APIs.

The MAI-1 contract

MAI-1 compresses what an agent actually needs into four sections:

json
{  "identity": { "aid": "scrapy-v1", "version": null },  "logic": {    "input_schema":  { "type": "url",  "description": "URL(s) to scrape" },    "output_schema": { "type": "json", "description": "Structured extracted data" }  },  "trust": {    "reliability_score": 0.95,    "latency_ms": 100,    "status": "active"  },  "action": {    "install_cmd": "pip install scrapy",    "execute_cmd": "scrapy crawl <spider_name>",    "source_url": "https://github.com/scrapy/scrapy"  }}
  • logic — what goes in, what comes out
  • trust — reliability scores computed from public repository metadata (stars, maintenance recency), recalculated regularly. No invented numbers.
  • action — how to install and invoke it

Quick start — MCP (recommended)

aiaam is listed in the official MCP registry. Connect from any MCP client:

Claude Code:

bash
claude mcp add --transport http aiaam https://aiaam.xyz/mcp

Cursor / generic MCP config:

json
{  "mcpServers": {    "aiaam": {      "url": "https://aiaam.xyz/mcp",      "transport": "http"    }  }}

Available MCP tools: search_tools, get_tool, get_trending, get_api_manifest, compile_api.

Quick start — REST

bash
# Search the catalogcurl "https://aiaam.xyz/api/v1/tools?q=web+scraping"
# Get a full contractcurl "https://aiaam.xyz/api/v1/tools/scrapy-v1"
# Trending toolscurl "https://aiaam.xyz/api/v1/tools/trending"

Machine-readable discovery endpoints:

PathPurpose
/llms.txtFull catalog in llmstxt.org format
/agent.jsonAgent discovery manifest
/.well-known/mcp.jsonMCP server metadata
/openapi.jsonOpenAPI schema

Telemetry (optional, anonymous)

Contracts include a telemetry_protocol block: after using a tool, agents may POST execution feedback (HTTP status, latency). This feedback feeds the reliability scores — agents that report make the catalog more accurate for every other agent. No authentication, no tracking, entirely optional.

Philosophy

  1. The format spreads, not the product. MAI-1 contracts are self-contained JSON. Anyone can host them; aiaam.xyz is one registry, not a gatekeeper.
  2. No invented data. Reliability scores come from verifiable public metadata. Tools without verification are marked as such.
  3. Additive, never redirective. Integrations never replace existing documentation or workflows.

Status

Active development. Catalog: 100+ verified contracts across PyPI, GitHub, npm and Hugging Face. See /llms.txt for the live list.

Source: README.md at commit 80d1b0a

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.