Paylo
REMOTE · MCP.USEPAYLO.COM
Search verified Nigerian stores, products and services on Paylo. Read-only, no account needed.
Available components
Last scanned (15 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 Security74
- 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. 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 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 Nov 26 +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.
- 12 Nov 26 +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.
- 10 Nov 26 +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.
- 7 Nov 26 +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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://mcp.usepaylo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.usepaylo.com | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | deaeed7f62917a6813a026daeca715c7 |
| SANs: mcp.usepaylo.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 mcp.usepaylo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| usepaylo.com. | No DS | 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://mcp.usepaylo.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.usepaylo.com/mcp | HTTPS enforced | 301 | https://mcp.usepaylo.com/mcp |
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_categories ~41
Get categories for a storefront slug.
| Name | Type | Req | Description |
|---|---|---|---|
| storefrontSlug | string | yes | The store's slug, e.g. 'greybox' (from search_storefronts). |
No output schema declared.
No examples provided.
get_changelog ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_product ~69
Get a single product by storefront slug and product slug.
| Name | Type | Req | Description |
|---|---|---|---|
| productSlug | string | yes | The product's slug within that store (from search_products results). |
| storefrontSlug | string | yes | The store's slug, e.g. 'greybox' (from search_storefronts or a product result). |
No output schema declared.
No examples provided.
get_seller_overview ~104
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_seller_signup_link ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_storefront ~61
Get a storefront catalog summary and stats by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The storefront's slug — the path segment of its URL, e.g. 'greybox' for usepaylo.com/greybox (also returned by search_storefronts). |
No output schema declared.
No examples provided.
get_wishlist ~59
Get a public Paylo wishlist by its share link or token: items, prices, and how much funding each item still needs.
| Name | Type | Req | Description |
|---|---|---|---|
| urlOrToken | string | yes | A usepaylo.com/wishlist/... share link or the bare share token |
No output schema declared.
No examples provided.
search_products ~142
Search products by query, optionally scoped to a storefront and category, with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
search_services ~132
Search services by query, optionally scoped to a storefront and category, with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
search_storefronts ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'. |
No output schema declared.
No examples provided.
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.
remote · mcp.usepaylo.com
claude mcp add --transport http com-usepaylo-paylo 'https://mcp.usepaylo.com/mcp'
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.