Other · Remote MCP server
Atlas
Agent-design pattern guidance via 5 hosted read-only tools; Streamable HTTP, no auth, one Release.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.agentic-atlas/atlas- Version
- 1.0.6
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Publisher
- dev.agentic-atlas
- Namespace
- Namespace verified by the MCP Registry via the domain agentic-atlas.dev · how
- Website
- agentic-atlas.dev/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agentic-atlas.dev/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 200)
- Handshake
- Agentic Atlas 1.0.11 · protocol 2025-06-18
- Tools discovered
- 5:
atlas_orient,atlas_cards,atlas_read,atlas_links,atlas_navigate - Checked on
- 2026-10-05
How to connect Atlas
Atlas is a remote MCP server: there is nothing to install. Its endpoint is https://agentic-atlas.dev/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 other servers
| Server | Runs |
|---|---|
| AtakoRemote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels. | Remote · HTTPLive check: ✓ handshake |
| Atera MCPEvery Atera RMM + PSA endpoint, plus a local SQLite mirror that answers fleet-health, SLA, and. | Local · stdio |
| Atimelogger MCPMCP server exposing the ATimeLogger REST API (activities, reports, types) | Local · stdio |
| Atinamos EvidenceRead-only verification evidence for paid machine services and buyer policy checks. | Remote · HTTPLive check: ✗ no handshake |
| Atlas Scientific EZO SensorsMCP server for Atlas Scientific EZO sensor circuits (pH, ORP, DO, EC, RTD, HUM, CO2, PRS) over UART. | Local · stdio |
| AtlaSent MCP ServerAtlasent for AI agents: with an API key, actions wait for approval with signed proof. No key: demo. | Local · stdio |
| atlaso.aiAI memory layer - one shared, persistent memory across every AI tool you connect. | Remote · HTTPLive check: sign-in required |
| AtmitaMessage your Atmita agent - one connection reaches all its accounts and tools, WhatsApp included. | Remote · HTTPLive check: sign-in required |