Atly
REMOTE · AGENTIC-API.ATLY.COM
Find places by what you want (work friendly, gluten free, great coffee), scored from real reviews.
Available components
Last scanned (8 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
- Structured output schemas are declared (86% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +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.
- 14 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 +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.
- 9 Oct 26 +1
- Stability: unverified → 0.10 ▲ functional
- 6 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://agentic-api.atly.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atly.com | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ad17ebc0772373170eb04d0f28a80c48 |
| SANs: atly.com, *.atly.com, os.atly.com, *.os.atly.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentic-api.atly.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| atly.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentic-api.atly.com/mcp | Verified | 200 | |
| http (plaintext) | http://agentic-api.atly.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_api_key Show my key and quota ~44
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).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string|null | – | – |
| doc_notes | string|null | – | – |
| email_verified | boolean|null | – | – |
| key_id | string|null | – | – |
| label | string|null | – | – |
| quota | – | – | – |
| tier | – | – | – |
No examples provided.
get_docs Read the Atly API guide ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_place Get place details ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string|null | – | – |
| doc_notes | string|null | – | – |
| place | – | – | – |
No examples provided.
list_areas Find areas ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| areas | – | – | – |
| call_id | string|null | – | – |
| doc_notes | string|null | – | – |
| total | – | – | – |
No examples provided.
list_categories Find categories ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string|null | – | – |
| categories | – | – | – |
| doc_notes | string|null | – | – |
| total | – | – | – |
No examples provided.
search_places Search places ~264
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area_id | string | – | An id from `list_areas`; the search covers that area's viewport. Give this or lat/lon, not both. |
| categories | array | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
submit_feedback Send feedback ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | – |
| notes | string | – | About the result only — never the conversation or the user. |
| outcome | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string|null | – | – |
| doc_notes | string|null | – | – |
| recorded | boolean|null | – | – |
No examples provided.
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.
remote · agentic-api.atly.com
claude mcp add --transport http com-atly-places 'https://agentic-api.atly.com/mcp'
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.