loops.so publishes an Agentic Resource Discovery manifest at
/.well-known/ai-catalog.json, declaring what an AI agent can call on this domain.
Everything below is read from that file. First seen by our crawler on 31 August 2026.
| Declared resource | Type |
|---|---|
| Loops MCPnot yet checkedv1.0.0 Manage contacts, send events, and send transactional email through the hosted Loops MCP server. endpoint: https://loops.so/.well-known/mcp/server-card.jsonidentifier: urn:air:loops.so:mcp:loopsemail contacts events transactional-email trust identity: https://loops.so | application/mcp-server-card+json |
| Loops Agent Skills and Pluginnot yet checkedv0.1.0 Official installable skills for the Loops API, CLI, LMX email markup, and email-sending best practices. endpoint: https://github.com/Loops-so/skills/archive/refs/heads/main.tar.gzidentifier: urn:air:loops.so:plugin:loopsemail api cli lmx deliverability trust identity: https://loops.so | application/agent-plugins+gzip |
https://loops.so/.well-known/ai-catalog.json, this publisher's own file.
Identifiers are reproduced exactly as published.
Note: this is the pre-v0.91 path. The specification renamed the manifest to /.well-known/ard.json, and most of the ecosystem still serves the older name.
None of these endpoints has been probed for reachability yet, so nothing here says whether they answer.
"Answers" and "no response" describe only whether an endpoint replied when last probed:
services go down and come back, and an entry is demoted rather than removed. None of this
is a trust, quality or safety rating.
https://neuronto.com/search, or connect an agent to https://neuronto.com/mcp.
If this is your domain, the free console shows what a registry
sees when it reads your manifest.