aiaam
MAI-1 registry: search 100+ verified AI tool contracts with live reliability scores in one call.
needs work
No valid MCP answer at last check (HTTP 405).
Rule R2g · what this means · Not tested in Copilot Studio.
| Registry name | io.github.javierfajardo85-rgb/aiaam |
| Endpoint used for verdict | https://aiaam.xyz/mcp |
| Transports | streamable-http |
| Auth (Copilot Studio setting) | Unknown |
| Last endpoint check | 2026-10-23T22:40:31Z · HTTP 405 |
| GitHub | javierfajardo85-rgb/aiaam-xyz |
| Version | 1.0.0 |
| Registry updated | 2026-06-10 |
Standards signals
| Official MCP Registry | Listed (active) MCP Registry |
| server.json schema | 2025-09-29 · older than 2025-12-11server.json schema changelog |
| Transport | Streamable HTTP (remote) Transports: Streamable HTTP |
| Answers MCP | No valid MCP answer at last check Lifecycle: initialization |
| Spec version spoken | Not observed Versioning |
| Supports 2026-07-28 | Not detected server/discover |
Observed from public registry data and a read-only, unauthenticated check on 2026-10-23. Not a certification: AAIF and the MCP project don't certify servers, and these lines are signals, not pass/fail. They don't change the Copilot Studio verdict. Own this server? modelcontextprotocol/conformance: test your own server.
Maintenance signals
- GitHub repo javierfajardo85-rgb/aiaam-xyz is archived (read-only) · checked 2026-10-23 · source
An estimate from public metadata, not a judgment of the project. Signals don't change the Copilot Studio verdict.
Track changes like this weekly. New Copilot-ready MCP servers, breakages and auth changes, in one short email.
Is this wrong or out of date? Email us. Data built 2026-10-24.