io.github.javierfajardo85-rgb/aiaam

Official registry Archived Search and web

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http aiaam 'https://aiaam.xyz/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "aiaam": {
            "type": "http",
            "url": "https://aiaam.xyz/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. aiaam.xyz — MAI-1 Tool Registry
  2. The problem
  3. The MAI-1 contract
  4. Quick start — MCP (recommended)
  5. Quick start — REST
  6. Telemetry (optional, anonymous)
  7. Philosophy
  8. Status

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.


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:

{
  "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

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

Claude Code:

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

Cursor / generic MCP config:

{
  "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

# Search the catalog
curl "https://aiaam.xyz/api/v1/tools?q=web+scraping"

# Get a full contract
curl "https://aiaam.xyz/api/v1/tools/scrapy-v1"

# Trending tools
curl "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.

Frequently asked questions

What is io.github.javierfajardo85-rgb/aiaam?

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

How do I install io.github.javierfajardo85-rgb/aiaam?

It runs as a remote server. In Claude Code: claude mcp add --transport http aiaam 'https://aiaam.xyz/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.javierfajardo85-rgb/aiaam need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.javierfajardo85-rgb/aiaam open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.javierfajardo85-rgb/aiaam?

It is published by javierfajardo85-rgb. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.