Developer · Remote MCP server
Loomaly
SEO audit of every page: what to fix first, a fix prompt for your framework, and a re-check.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.loomaly/loomaly- Version
- 1.1.5
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- com.loomaly
- Namespace
- Namespace verified by the MCP Registry via the domain loomaly.com · how
- Website
- loomaly.com/docs/mcp
- Repository
- github.com/loomaly/loomaly
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://loomaly.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Loomaly
Loomaly is a remote MCP server: there is nothing to install. Its endpoint is https://loomaly.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| LongmemPersistent cross-project memory for Cursor and Claude Code using local semantic search. | Local · stdio |
| Looking Glass MCPAI-native browser for agents. 71 tools with self-healing, semantic extraction, vault CLI. | Local · stdio |
| Lookup Disclose IoFind the right security-disclosure contact for any internet asset (domain, IP, package, repo, app). | Remote · HTTPLive check: ✓ handshake |
| LoomLocal-first personal knowledge base. Cited answers from your vault via vector + graph retrieval. | Local · stdio |
| LoopbackFeedback bus for coding agents: pin feedback on the app you're building; a fix turns the pin green. | Local · stdio |
| LoreCross-agent memory over MCP: hybrid recall, knowledge graph, private/shared visibility, redaction. | Local · stdio |
| LoreLightweight MCP for infinite agent memory. Any agent, any session, anytime. | Local · stdio |
| Lore ContextGoverned AI-agent memory, Evidence Ledger traces, evals, and portable context tools. | Local · stdio |