# Atly (remote · agentic-api.atly.com)

Find places by what you want (work friendly, gluten free, great coffee), scored from real reviews.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `agentic-api.atly.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-atly-places/agentic-api.md), [page](https://verifymcp.io/servers/com-atly-places/agentic-api)

## Channel facts

- Endpoint: `https://agentic-api.atly.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 869 tokens (~124/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
  - Structured output schemas are declared (86% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Atly MCP server?

Atly is a hosted endpoint at https://agentic-api.atly.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-atly-places 'https://agentic-api.atly.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-atly-places": {
      "url": "https://agentic-api.atly.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-atly-places": {
      "type": "http",
      "url": "https://agentic-api.atly.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-atly-places]
url = "https://agentic-api.atly.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-atly-places": {
      "type": "remote",
      "url": "https://agentic-api.atly.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-atly-places --url 'https://agentic-api.atly.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-atly-places:
    url: "https://agentic-api.atly.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-atly-places": {
      "Transport": "http",
      "Url": "https://agentic-api.atly.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-atly-places -t streamable-http -u 'https://agentic-api.atly.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-atly-places": {
      "type": "http",
      "url": "https://agentic-api.atly.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-09 (score 67, +1)

- [functional improvement] Stability: unverified → 0.10

### 2026-10-06 (score 66)

First indexed and scored.

## MCP tools (7)

### `get_api_key` (~44 tokens)

Show my key and quota

Show my key, tier and remaining quota

Who am I and how much quota is left. Works without a key too (then it describes the anonymous allowance for your IP).

Output parameters:

- `call_id` (string|null)
- `doc_notes` (string|null)
- `email_verified` (boolean|null)
- `key_id` (string|null)
- `label` (string|null)
- `quota`
- `tier`

### `search_places` (~264 tokens)

Search places

Find places for an intent near a location

The core call. Give one or more category ids (from `list_categories`; all must match) and a location — either
an `area_id` from `list_areas` or coordinates with a radius — and get places ranked by Atly's score for those
categories, each with quotable reasons from real reviews, a link to cite, and freshness. Scores are 0–10 and
relative to the area; a place with no score is unmeasured, not bad. If no place matches every category, trailing
categories are dropped until something does (the first is never dropped), and `dropped_categories` says which.
Ranking considers the strongest 100 candidates by Atly's base score. Scores are relative to other places in the same country.

Input parameters:

- `area_id` (string): An id from `list_areas`; the search covers that area's viewport. Give this or lat/lon, not both.
- `categories` (array, required): Category ids, most important first. Every result matches all of them (after any relaxation).
- `lat` (number)
- `limit` (integer)
- `lon` (number)
- `radius_km` (number): Used with lat/lon.

Output parameters:

- `area`: The resolved search geometry — an area (id, name, level, center, bbox) or a circle (center, radius_km).
- `call_id` (string|null)
- `doc_notes` (string|null)
- `dropped_categories`: Category ids dropped to avoid an empty result.
- `places`
- `total_matched`: How many places match in this area, capped ("1000+"). Absent when counting timed out.

### `get_place` (~69 tokens)

Get place details

Everything about one place

Full detail for a place id from `search_places`: profile, hours, all category scores, up to eight quotable
statements, good-to-know facts, gluten-free identity when known, and the canonical Atly URL to cite.

Input parameters:

- `id` (string, required)

Output parameters:

- `call_id` (string|null)
- `doc_notes` (string|null)
- `place`

### `submit_feedback` (~113 tokens)

Send feedback

Tell us how a call went

Reference the `call_id` of any earlier response and say whether it helped, and optionally why, in a sentence
about the result — what was right, missing or wrong. Do not include the user's words, the conversation, or
anything about the person. One row per caller per call; lightly rate-limited.

Input parameters:

- `call_id` (string, required)
- `notes` (string): About the result only — never the conversation or the user.
- `outcome` (string, required)

Output parameters:

- `call_id` (string|null)
- `doc_notes` (string|null)
- `recorded` (boolean|null)

### `get_docs` (~55 tokens)

Read the Atly API guide

Read the documentation

Returns the API guide as Markdown: what each operation is for, how to turn a user's request into
category ids and a location, request and response shapes, how to read scores. Call this once per session.

### `list_categories` (~173 tokens)

Find categories

List intent categories

The intent taxonomy: cuisines, dishes, features ("Wifi", "Outdoor Seating"), vibes ("Cozy", "Lively"),
occasions ("First Date", "Group Dinner"), diets ("Gluten Free", "Keto") and more. Map the user's words to
category ids before searching. Filter with `q`, one concept per call — exact and prefix matches rank first, then substrings and keywords;
plurals, hyphens and small typos are tolerated — or fetch once without `q` and cache the full list.

Input parameters:

- `limit` (integer): Maximum categories to return.
- `q` (string): Words to match against category names and keywords, e.g. "coffee", "dog friendly", "gluten-free". Ranked; tolerant of plurals and small typos.

Output parameters:

- `call_id` (string|null)
- `categories`
- `doc_notes` (string|null)
- `total`

### `list_areas` (~151 tokens)

Find areas

List supported areas

Cities, neighborhoods and states Atly covers — densest in the United States, with pockets in Mexico, Israel and Thailand — each with an `id` you can pass to
search, a center, a bounding box when known, and how many places it holds. Filter with `q` (substring of
the name) and `level` (city, neighborhood, state). Results are ordered by place count.

Input parameters:

- `level` (string): Restrict to one level.
- `limit` (integer)
- `q` (string): Area name or common abbreviation, e.g. "san diego", "midtown", "nyc". Exact and prefix matches rank first.

Output parameters:

- `areas`
- `call_id` (string|null)
- `doc_notes` (string|null)
- `total`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-atly-places/agentic-api#diagnostics

## Score history

- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 69
- 2026-10-12: 69
- 2026-10-10: 68
- 2026-10-09: 67
- 2026-10-06: 66

## Common questions

### What is the Atly MCP server?

Atly is an MCP server listed in the public MCP registry as com.atly/places. Find places by what you want (work friendly, gluten free, great coffee), scored from real reviews. This page covers its hosted endpoint (https://agentic-api.atly.com/mcp).

### Is the Atly MCP server safe to use?

Atly scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Atly MCP server expose?

Atly exposes 7 tools: get_api_key, search_places, get_place, submit_feedback, get_docs, and 2 more. Their descriptions and schemas cost roughly 869 tokens of context every time the server is loaded.

### Does the Atly MCP server require authentication?

No. We connected to Atly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Atly MCP server still maintained?

Atly is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agentic-api.atly.com/mcp
- Repository: https://github.com/atlyai/atly-plugin
- Website: https://agentic-api.atly.com/v0/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-atly-places/agentic-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-atly-places/agentic-api.json
- HTML version of this page: https://verifymcp.io/servers/com-atly-places/agentic-api