# Ayebot buyer index (remote · ayebot.com)

Counts of acquirers by sector and Southeast Asian market, from ayebot.com. Aggregate only, no names.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-07

## Components

- remote · `ayebot.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/gweeyichen-ayebot/ayebot.md), [page](https://verifymcp.io/servers/gweeyichen-ayebot/ayebot)

## Channel facts

- Endpoint: `https://ayebot.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 702 tokens (~175/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Ayebot buyer index MCP server?

Ayebot buyer index is a hosted endpoint at https://ayebot.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 gweeyichen-ayebot 'https://ayebot.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "gweeyichen-ayebot": {
      "url": "https://ayebot.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gweeyichen-ayebot": {
      "type": "http",
      "url": "https://ayebot.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.gweeyichen-ayebot]
url = "https://ayebot.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gweeyichen-ayebot": {
      "type": "remote",
      "url": "https://ayebot.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gweeyichen-ayebot --url 'https://ayebot.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  gweeyichen-ayebot:
    url: "https://ayebot.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "gweeyichen-ayebot": {
      "Transport": "http",
      "Url": "https://ayebot.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add gweeyichen-ayebot -t streamable-http -u 'https://ayebot.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "gweeyichen-ayebot": {
      "type": "http",
      "url": "https://ayebot.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-11-07 (score 86, +1)

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

### 2026-11-06 (score 85, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 85, +1)

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

### 2026-11-02 (score 84, +1)

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

### 2026-10-31 (score 83, +1)

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

### 2026-10-29 (score 82, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “how_to_sell_next_steps” rewrote its description, which is the text the model reads

### 2026-10-27 (score 81, +1)

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

### 2026-10-24 (score 80, +3)

- [security improvement] HSTS header: fail → pass

## MCP tools (4)

### `count_buyers` (~229 tokens)

Count acquirers by sector and market

Count how many acquirers on Ayebot's buyer register state an appetite for a sector in a Southeast Asian market. Use it for questions like "how many buyers are there for a healthcare business in Malaysia?" or "how many private equity buyers look at logistics in Singapore?". Give sector and market for one cell; sector only for that sector across all six markets; market only for every sector in that market; neither for register totals. Accepts keys (e.g. "fnb", "sg") or plain names (e.g. "food and beverage", "Singapore"). Returns aggregate counts split into strategic, private equity, family office and other. Never returns names. Call list_sectors_and_markets for valid values.

Input parameters:

- `market` (string): Market key or name: sg, my, id, th, vn, ph (Singapore, Malaysia, Indonesia, Thailand, Vietnam, Philippines). Omit for all markets.
- `sector` (string): Sector key or name, e.g. "healthcare", "F&B", "logistics". Omit for all sectors.

### `list_sectors_and_markets` (~55 tokens)

List sectors and markets

List the 12 sectors and 6 Southeast Asian markets covered by the Ayebot buyer index, with the key to pass to count_buyers and buyer_appetite_summary, and the public page for each sector.

### `buyer_appetite_summary` (~127 tokens)

Buyer appetite for a sector across Southeast Asia

Summarise acquirer appetite for one sector across Singapore, Malaysia, Indonesia, Thailand, Vietnam and the Philippines: per-market counts (ranked), the strategic / private equity / family office mix, and how many name the market directly versus cover it through a regional or global mandate. Use it for "where in Southeast Asia is buyer appetite strongest for my education business?". Aggregate counts only, never names. Links to the sector page on ayebot.com.

Input parameters:

- `sector` (string, required): Sector key or name, e.g. "education", "beauty", "industrial engineering".

### `how_to_sell_next_steps` (~118 tokens)

Next steps for a founder thinking of selling

Return links to Ayebot's free tools and to a human adviser, for a founder in Singapore or Southeast Asia who is considering selling a company: the buyer finder, buyers by sector, the valuation check, how valuation ranges work, what is free, the FAQ, and talking to an adviser at Growth Alliance Capital. Use it when the user asks what to do next, how to value or prepare a company for sale, or how to get advice. This server does not value companies; it points to the tools and to people.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gweeyichen-ayebot/ayebot#diagnostics

## Score history

- 2026-11-07: 86
- 2026-11-06: 85
- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 81
- 2026-10-27: 81
- 2026-10-26: 80
- 2026-10-25: 80
- 2026-10-24: 80
- 2026-10-23: 77
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 75
- 2026-10-19: 75
- 2026-10-18: 74
- 2026-10-17: 74
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 72
- 2026-10-10: 71

## Common questions

### What is the Ayebot buyer index MCP server?

Ayebot buyer index is an MCP server listed in the public MCP registry as io.github.gweeyichen/ayebot. Counts of acquirers by sector and Southeast Asian market, from ayebot.com. Aggregate only, no names. This page covers its hosted endpoint (https://ayebot.com/mcp).

### Is the Ayebot buyer index MCP server safe to use?

Ayebot buyer index scores 86 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 Ayebot buyer index MCP server expose?

Ayebot buyer index exposes 4 tools: count_buyers, list_sectors_and_markets, buyer_appetite_summary, how_to_sell_next_steps. Their descriptions and schemas cost roughly 529 tokens of context every time the server is loaded.

### Does the Ayebot buyer index MCP server require authentication?

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

### Is the Ayebot buyer index MCP server still maintained?

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

### What did VerifyMCP test on the Ayebot buyer index MCP server?

VerifyMCP ran 13 checks on Ayebot buyer index, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ayebot.com/mcp
- Website: https://ayebot.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/gweeyichen-ayebot/ayebot.xml
- Changelog JSON feed: https://verifymcp.io/servers/gweeyichen-ayebot/ayebot/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/gweeyichen-ayebot/ayebot.json
- HTML version of this page: https://verifymcp.io/servers/gweeyichen-ayebot/ayebot