aiaam
Server Details
MAI-1 registry: search 100+ verified AI tool contracts with live reliability scores in one call.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
6 toolscompile_apiInspect
Compiles a public OpenAPI/Swagger spec URL into a compact MAI-API manifest. Requires a valid API key (X-Api-Key). Without a key, only specs from apis.guru or raw.githubusercontent.com are accepted. Returns immediately with a status_url to poll for the result (~15 seconds). Use get_api_manifest to fetch the result once ready.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Optional API key for unrestricted URL access. Without key, only apis.guru and github raw URLs are allowed. | |
| category | No | Category hint: payments, communication, devtools, ai, productivity, security, data, other | other |
| openapi_url | Yes | Public URL of an OpenAPI 3.x or Swagger 2.x JSON/YAML spec. |
contribute_toolInspect
Add a missing tool to the aiaam.xyz catalog. Provide its PyPI project or GitHub repo URL; the registry builds an unverified MAI-1 contract from public metadata only (no invented data). Idempotent — if the tool already exists, its current contract is returned. Use this when search_tools returns no results for a library you know exists.
| Name | Required | Description | Default |
|---|---|---|---|
| source_url | Yes | https://pypi.org/project/<pkg> or https://github.com/<owner>/<repo> |
get_api_manifestInspect
Returns a compact MAI-API manifest for a web API service (Stripe, Slack, GitHub, etc.). Each manifest is ~850 tokens and contains the base URL, auth method, and up to 20 key endpoints. Use this instead of fetching and parsing a full OpenAPI spec. Available services include: stripe_api, slack_web_api, github, openai_api, notion_api, jira_cloud_rest_api, gmail_api, google_calendar_api, twilio_api, sendgrid_email_activity_api, spotify_web_api, twitter_api_v2, and 30+ more. Returns {error: not_found} if the service has not been compiled yet.
| Name | Required | Description | Default |
|---|---|---|---|
| service_name | Yes | The service identifier, e.g. 'stripe_api', 'slack_web_api', 'openai_api'. Use underscores, lowercase. Check /llmo-apis for the full list. |
get_toolInspect
Returns the complete MAI-1 contract for a specific tool by its AID string (e.g. 'langchain-v1', 'crewai-v1'). Includes reliability_score, latency_ms, install_cmd, execute_cmd, input/output schemas.
| Name | Required | Description | Default |
|---|---|---|---|
| aid | Yes | The tool's unique AID string identifier (e.g. 'langchain-v1') |
get_trendingInspect
Returns top tools sorted by reliability_score descending. Use to discover the most reliable and actively maintained tools in the catalog.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of results to return (default 10, max 20) |
search_toolsInspect
Search the aiaam.xyz catalog of 100+ verified MAI-1 tool contracts by capability or name. Returns up to 10 results saving ~85% context tokens vs reading raw GitHub READMEs.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Tool capability or name to search (e.g. 'web scraping', 'langchain') | |
| category | No | Optional: filter by source platform — github | pypi | huggingface | npm |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!