# Geoacpfilho Paygate MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.geoacpfilho%2Fpaygate-mcp
Registry id: `mcp-registry/io.github.geoacpfilho/paygate-mcp`
Status: live (checked 2026-10-27T09:01:45.461Z)

## Verdict

Geoacpfilho Paygate MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 357 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 6 tools, costing an agent about 1,171 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 357 ms | 57% of MCP servers |
| p95 handshake latency | 2675 ms | — |
| Checks in 30 days | 5,034 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 6 | — |
| Tool-list size for an agent | ~1,171 tokens | 70% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "geoacpfilho-paygate-mcp-server": {
      "type": "http",
      "url": "https://paygate-mcp.rendercriativo.workers.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http geoacpfilho-paygate-mcp-server https://paygate-mcp.rendercriativo.workers.dev/mcp
```

## Tools (10)

- `get_earnings`: Report how much the user has earned selling their tools. Use when they ask about sales, revenue, income, how much they made, how many calls were paid, or which 
- `get_health`: Checks the health and readiness of the payment rail.
- `get_my_listing`: Review what the user currently has for sale. Use when they ask what they are selling, what their prices are, where their money goes, or want to check their list
- `get_server_info`: Retrieves information about a specific registered server.
- `get_tool_pricing`: Retrieves the pricing for a specific tool on a registered server.
- `list_registered_servers`: Find a paid tool that does something you cannot do yourself. Use when the user needs a capability you lack and is willing to pay per use, or asks what paid tool
- `register_server`: Start charging for an MCP server the user owns. Use when they want to monetize, sell, charge for, get paid for, put a price on, or make money from a server, API
- `set_tool_price`: Reprice or unlist something the user already sells. Use when they want to raise, lower or change a price, make a tool free, pause selling it, or take it off the
- `update_tool_pricing`: Updates the pricing for a tool on a registered server.
- `verify_ownership`: Prove the user owns the server they listed, earning a trusted badge in the marketplace. Use after they have published their verification token at /.well-known/p

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.