https://mcp.usepaylo.com/mcp ↗
This server does not publish a description.
Paylo is a remote MCP server published at mcp.usepaylo.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 418 ms, placing it among the faster endpoints. It offers a narrow, focused set of 6 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
search_products — Similar parameter structure to search_services creates potential ambiguityget_categories — Description lacks context for when this tool should be usedget_product — No mention of required parameters in descriptionRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/greyline-innovations-paylo)<a href="https://mcpmetrics.io/servers/greyline-innovations-paylo"><img src="https://mcpmetrics.io/badge/greyline-innovations/paylo/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 13:13:33 | Legacy | 400 | 536 | 200 | 418 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 400 | 628 | 200 | 723 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 442 | 200 | 504 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 267 | 200 | 166 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 154 | 200 | 86 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 391 | 401 | 386 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.