Suggested Connectors: exact brand-name query returns zero results for a published directory connector

### What happened?

## Summary

A published directory connector is the **#1 result** in directory search (`claude.ai/directory?q=ads`) but returns **zero results** from in-chat connector suggestions — including when queried by its exact, unique brand name.

This appears to be a retrieval failure rather than a ranking outcome. Ranking determines the *order* of matches; an exact brand-name query returning an empty set suggests the entry is not present in, or not reachable by, the in-chat suggestion index.

## Connector

| Field | Value |
|---|---|
| Name | Adspirer Ads & Performance Marketing Agent |
| Slug | `adspirer-ads-performance-marketing-agent` |
| Server URL | `https://mcp.adspirer.com/mcp` |
| Label | Community |
| Listed | July 2026 |
| Review state | Published |
| Health | Healthy — 3.4% disconnect rate (30d) |
| Tool call users (30d) | 3,378 |
| Tool calls (30d) | 246,936 |
| Directory rank | #352 |

## Steps to reproduce

**1. Confirm the listing is live and top-ranked in directory search**

Navigate to `https://claude.ai/directory?q=ads`

Result: "Adspirer Ads & Performance Marketing Agent" is returned as the **first** result, ahead of ~45 other connectors in the same category.

**2. Query in-chat connector suggestions by exact brand name**

In a Claude conversation, trigger connector suggestions using the exact term `adspirer`.

Result: **zero results returned.**

**3. Query in-chat connector suggestions by category**

Trigger connector suggestions with ads/advertising terms (`ads`, `google ads`, `meta ads`, `manage ad campaigns`, `performance marketing`).

Result: ~10 results returned, consistently including other ads connectors (Supermetrics, Windsor.ai, AdWhispr Ads, Abency, Motion Creative Analytics, Helium 10). Adspirer does not appear in any variation tested.

Six query variations were run across brand-name, category, and use-case phrasings. The connector was returned in none of them.

## Why this reads as a bug rather than ranking

We understand in-chat suggestions are usage-ranked, and that rank #352 will not place us in a competitive category query. That part is working as documented, and **this issue is not a request for promotion.**

The narrower concern is the **zero-result response to an exact, unique brand-name query**. Ranking should affect position among matches, not produce a null set for a direct name lookup. Behaviour consistent with ranking would be the connector appearing low in results for a brand-name query — not being absent entirely.

Per the [directory documentation](https://claude.com/docs/connectors/directory): *"Directory connectors are eligible for Suggested Connectors — in-chat recommendations when relevant to the user's task. Every directory entry is included automatically."* Automatic inclusion does not appear to be reflected in observed behaviour for this entry.

## Questions

1. Is the in-chat suggestion index sourced from the same catalog as directory search, or a separate index with its own inclusion criteria?
2. Should an exact brand-name query be expected to return a matching connector irrespective of usage rank?
3. Is there a lag or eligibility threshold between directory publication and in-chat index inclusion?

## Environment

- Surface: Claude in-chat connector suggestions
- Directory listing: published and live at time of filing
- Connector health: Healthy; no elevated disconnect, 4xx or 5xx rates

### What did you expect to happen?

An exact-match query on a unique, published connector name should return that connector in in-chat connector suggestions, regardless of its usage rank.

Specifically: querying `adspirer` should surface "Adspirer Ads & Performance Marketing Agent", since the term exactly matches a unique published listing name and the connector is live, healthy, and returned as the #1 result for the same category on the directory search surface.

Ranking is expected to affect the connector's *position* among returned matches. It is not expected to produce an empty result set for a direct brand-name lookup.

### Steps to reproduce

1. Navigate to `https://claude.ai/directory?q=ads` and confirm "Adspirer Ads & Performance Marketing Agent" is returned as the #1 result (published, Community label, live listing).

2. In a Claude conversation, trigger in-chat connector suggestions using the exact brand name `adspirer`.
→ Observed: zero results returned.
→ Expected: the connector is returned, since the term exactly matches a unique published listing name.

3. Trigger in-chat connector suggestions with category terms: `ads`, `google ads`, `meta ads`, `manage ad campaigns`, `performance marketing`.
→ Observed: ~10 results returned each time, consistently including other ads connectors (Supermetrics, Windsor.ai, AdWhispr Ads, Abency, Motion Creative Analytics, Helium 10). Adspirer appears in none of them.

4. Repeat across brand-name, category, and use-case phrasings (six variations tested). The connector is returned in zero of them, while remaining the #1 result on the directory search surface throughout.

### Area

MCP Connector (adding/managing servers)

### MCP Server (if applicable)

Adspirer Ads & Performance Marketing Agent — https://mcp.adspirer.com/mcp

### Error messages or logs

```shell

```

### Additional context

_No response_