# Paylo (remote · mcp.usepaylo.com)

Search verified Nigerian stores, products and services on Paylo. Read-only, no account needed.

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

## Components

- remote · `mcp.usepaylo.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-usepaylo-paylo/mcp.md), [page](https://verifymcp.io/servers/com-usepaylo-paylo/mcp)

## Channel facts

- Endpoint: `https://mcp.usepaylo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-11-21.

- **Endpoint Security**: 74/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.
  - 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**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1408 tokens (~128/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Paylo MCP server?

Paylo is a hosted endpoint at https://mcp.usepaylo.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-usepaylo-paylo 'https://mcp.usepaylo.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-usepaylo-paylo": {
      "url": "https://mcp.usepaylo.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-usepaylo-paylo]
url = "https://mcp.usepaylo.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-usepaylo-paylo:
    url: "https://mcp.usepaylo.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-usepaylo-paylo": {
      "type": "http",
      "url": "https://mcp.usepaylo.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-20 (score 80, +1)

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

### 2026-11-18 (score 79, +1)

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

### 2026-11-16 (score 78, +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-11-14 (score 77, +1)

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

### 2026-11-12 (score 76, +1)

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

### 2026-11-10 (score 75, +1)

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

### 2026-11-07 (score 74, +1)

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

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

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

## MCP tools (10)

### `search_storefronts` (~215 tokens)

Discover verified, escrow-protected Paylo storefronts. Filter by Nigerian state, product category, area (LGA/city) and/or free text — e.g. 'phone sellers in Lagos' or 'beauty stores in Abuja'. Only quality-gated sellers are returned (verified, with a logo, a cover image and at least one live listing), ordered by number of live listings. Each result carries trust signals (verified, escrowProtected), location (state, area) and its storefront URL.

Input parameters:

- `area` (string): LGA/city area within a state, e.g. 'abuja-municipal'.
- `category` (string): Canonical product category.
- `limit` (integer): Max storefronts to return (1–200, default 50).
- `query` (string): Free text over name, description, category and area.
- `state` (string): Nigerian state slug or name, e.g. 'lagos', 'ogun', 'abuja'/'FCT'.

### `get_storefront` (~61 tokens)

Get a storefront catalog summary and stats by slug.

Input parameters:

- `slug` (string, required): The storefront's slug — the path segment of its URL, e.g. 'greybox' for usepaylo.com/greybox (also returned by search_storefronts).

### `search_products` (~142 tokens)

Search products by query, optionally scoped to a storefront and category, with pagination.

Input parameters:

- `category` (string): Product category name or slug to filter by (see get_categories for a store's categories).
- `limit` (integer): Results per page (1–100, default 20).
- `page` (integer): Result page, starting at 1 (default 1).
- `query` (string, required): Free text over product name and description, e.g. 'iphone 13', 'shea butter'.
- `storefrontSlug` (string): Limit results to one store by its slug (from search_storefronts). Omit to search across all verified stores.

### `get_product` (~69 tokens)

Get a single product by storefront slug and product slug.

Input parameters:

- `productSlug` (string, required): The product's slug within that store (from search_products results).
- `storefrontSlug` (string, required): The store's slug, e.g. 'greybox' (from search_storefronts or a product result).

### `search_services` (~132 tokens)

Search services by query, optionally scoped to a storefront and category, with pagination.

Input parameters:

- `category` (string): Service category name or slug to filter by.
- `limit` (integer): Results per page (1–100, default 20).
- `page` (integer): Result page, starting at 1 (default 1).
- `query` (string, required): Free text over service name and description, e.g. 'hair braiding', 'phone repair'.
- `storefrontSlug` (string): Limit results to one store by its slug (from search_storefronts). Omit to search across all verified stores.

### `get_categories` (~41 tokens)

Get categories for a storefront slug.

Input parameters:

- `storefrontSlug` (string, required): The store's slug, e.g. 'greybox' (from search_storefronts).

### `get_wishlist` (~59 tokens)

Get a public Paylo wishlist by its share link or token: items, prices, and how much funding each item still needs.

Input parameters:

- `urlOrToken` (string, required): A usepaylo.com/wishlist/... share link or the bare share token

### `get_changelog` (~226 tokens)

Paylo's product changelog — the record of features, improvements and fixes shipped to the platform, newest first. Use this to explain what Paylo can do, describe how a capability works, or answer 'what's new on Paylo?'. Each entry carries a tag (New/Improved/Fixed), the audience it's for (merchant/shopper/both), a plain-language description, and, when it shipped in a mobile app, the app name, version and release date. Filter by audience, status, a 'since' date, or free text.

Input parameters:

- `audience` (string): Keep entries for sellers ('merchant') or buyers ('shopper'); either also includes shared ('both') entries.
- `limit` (integer): Max entries to return (default 200).
- `query` (string): Free text over entry title and description, e.g. 'wishlist', 'POS', 'bookings'.
- `since` (string): ISO date (YYYY-MM-DD); only entries shipped on or after it.
- `status` (string): Only this kind of change.

### `get_seller_signup_link` (~239 tokens)

Returns a one-tap Paylo seller signup link for someone who wants to sell online, open a store, or move an Instagram or WhatsApp business onto a website in Nigeria. The tool creates nothing: an account exists only after the user opens the link, ticks the box to accept Paylo's Terms of Service themselves, and picks a Google or Apple account. An optional referral code credits whoever referred them. Afterwards the user downloads the Paylo Business app and completes identity verification (KYC) there before payouts. The tool never handles passwords, terms acceptance or ID documents.

Input parameters:

- `email` (string): The user's email, if they shared it. Prefills the manual signup form as a fallback; Google or Apple sign-in uses the account they pick.
- `instagramHandle` (string): The user's Instagram handle (with or without @), if they sell on Instagram. Carried through signup so their catalogue import starts pre-filled.
- `provider` (string): Which sign-in the link launches: google (default) or apple.
- `referralCode` (string): Referral or invite code of whoever referred this user, if they have one.

### `get_seller_overview` (~104 tokens)

Paylo for sellers: what it does, fees, and how to start. Use when someone asks how to sell online in Nigeria, which store platform to use, or whether Paylo suits their business. Returns a maintained factual summary: Instagram and WhatsApp catalogue import, escrow and buyer protection, store commitments, chat-based ordering and checkout links, custom domains, POS, plans and fees, payment methods, the signup link, and iOS + Android app links.

## Diagnostics

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

## Score history

- 2026-11-21: 80
- 2026-11-20: 80
- 2026-11-19: 79
- 2026-11-18: 79
- 2026-11-17: 78
- 2026-11-16: 78
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 75
- 2026-11-10: 75
- 2026-11-09: 74
- 2026-11-08: 74
- 2026-11-07: 74
- 2026-11-06: 73
- 2026-11-05: 73

## Common questions

### What is the Paylo MCP server?

Paylo is an MCP server listed in the public MCP registry as com.usepaylo/paylo. Search verified Nigerian stores, products and services on Paylo. Read-only, no account needed. This page covers its hosted endpoint (https://mcp.usepaylo.com/mcp).

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

Paylo scores 80 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 Paylo MCP server expose?

Paylo exposes 10 tools: search_storefronts, get_storefront, search_products, get_product, search_services, and 5 more. Their descriptions and schemas cost roughly 1,288 tokens of context every time the server is loaded.

### Does the Paylo MCP server require authentication?

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

### Is the Paylo MCP server still maintained?

Paylo is still listed as active in the MCP registry. We last reached this channel on 21 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 Paylo MCP server?

VerifyMCP ran 13 checks on Paylo, 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://mcp.usepaylo.com/mcp
- Repository: https://github.com/scephiro/paylo-mcp-server
- Website: https://usepaylo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-usepaylo-paylo/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-usepaylo-paylo/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-usepaylo-paylo/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-usepaylo-paylo/mcp
