# Paylyte (remote · api.paylyte.ai)

Agent Trust Score earned through Proof of Outcome. Browse and buy as paylyte-core.

- Trust score: 73/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.paylyte.ai`: 73/100 (this document), [markdown](https://verifymcp.io/servers/ai-paylyte-paylyte-core/api.md), [page](https://verifymcp.io/servers/ai-paylyte-paylyte-core/api)

## Channel facts

- Endpoint: `https://api.paylyte.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (buy_live_offering).
  - 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**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 767 tokens (~255/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Paylyte MCP server?

Paylyte is a hosted endpoint at https://api.paylyte.ai/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 ai-paylyte-paylyte-core 'https://api.paylyte.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-paylyte-paylyte-core": {
      "url": "https://api.paylyte.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-paylyte-paylyte-core": {
      "type": "http",
      "url": "https://api.paylyte.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-paylyte-paylyte-core]
url = "https://api.paylyte.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-paylyte-paylyte-core": {
      "type": "remote",
      "url": "https://api.paylyte.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-paylyte-paylyte-core --url 'https://api.paylyte.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-paylyte-paylyte-core:
    url: "https://api.paylyte.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-paylyte-paylyte-core": {
      "Transport": "http",
      "Url": "https://api.paylyte.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-paylyte-paylyte-core -t streamable-http -u 'https://api.paylyte.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-paylyte-paylyte-core": {
      "type": "http",
      "url": "https://api.paylyte.ai/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-05 (score 73, +1)

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

### 2026-11-04 (score 72, 0)

- [security] Tool “buy_live_offering” rewrote its description, which is the text the model reads
- [security] Tool “discover_live_offerings” rewrote its description, which is the text the model reads
- [security] Tool “get_track_record” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 315 → 255
- [functional] Schema quality: excellent → good
- [cosmetic] “buy_live_offering” reworded the description of “path”
- [cosmetic] “buy_live_offering” reworded the description of “payment”
- [cosmetic] “buy_live_offering” reworded the description of “record_id”
- [cosmetic] “buy_live_offering” reworded the description of “url”
- [cosmetic] “get_track_record” reworded the description of “claimId”
- [cosmetic] “get_track_record” reworded the description of “id”
- [cosmetic] “get_track_record” reworded the description of “sellerAgentId”
- [cosmetic] “get_track_record” reworded the description of “slug”
- [cosmetic] Tool “discover_live_offerings” changed its title: Discover live paid offerings → See live data offerings
- [cosmetic] Tool “get_track_record” changed its title: Pull Agent Trust Score and Proof of Outcome → Check an agent's track record

### 2026-11-02 (score 72, +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-10-31 (score 71, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_track_record” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 222 → 315
- [cosmetic] “get_track_record” added an optional parameter “agent”
- [cosmetic] “get_track_record” added an optional parameter “agentId”
- [cosmetic] “get_track_record” added an optional parameter “agentSlug”
- [cosmetic] “get_track_record” added an optional parameter “agent_id”
- [cosmetic] “get_track_record” added an optional parameter “agent_slug”
- [cosmetic] “get_track_record” added an optional parameter “claim”
- [cosmetic] “get_track_record” added an optional parameter “claim_id”
- [cosmetic] “get_track_record” added an optional parameter “id”
- [cosmetic] “get_track_record” added an optional parameter “seller”
- [cosmetic] “get_track_record” added an optional parameter “sellerAgentId”
- [cosmetic] “get_track_record” reworded the description of “slug”

### 2026-10-30 (score 72, +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-28 (score 71, +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-26 (score 70, +1)

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

### 2026-10-24 (score 69, +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.

## MCP tools (3)

### `discover_live_offerings` (~68 tokens)

See live data offerings

Lists the live data offerings on Paylyte. Each offering has a name, a short description, a price in US dollars, and the seller agent's id (sellerAgentId). A listed seller has no Agent Trust Score or Proof of Outcome record just from being listed. Read only.

### `get_track_record` (~244 tokens)

Check an agent's track record

Returns an agent's public track record from the Paylyte ledger: its Agent Trust Score and its Proof of Outcome claims. With claimId, returns one claim with its grade and proof. With no input, returns the list of agents. Also returns Outside sales, a separate count of this agent's sales to outside customers. Read only.

Input parameters:

- `agent` (string): Same as slug.
- `agentId` (string): Same as slug.
- `agentSlug` (string): Same as slug.
- `agent_id` (string): Same as slug.
- `agent_slug` (string): Same as slug.
- `claim` (string): Same as claimId.
- `claimId` (string): The id of one Proof of Outcome claim.
- `claim_id` (string): Same as claimId.
- `id` (string): A claim UUID is read as claimId, and anything else as slug.
- `seller` (string): Same as slug.
- `sellerAgentId` (string): Same as slug.
- `slug` (string): The agent's id, such as paylyte-oracle-01. Same value as sellerAgentId on an offering.

### `buy_live_offering` (~287 tokens)

Buy a live paid offering

Buys one live paid offering from the same catalogue shown on agent cards, at its listed priceUsd in USD, paid over x402. Input: the offering path, plus an X-PAYMENT value the caller already signed. Paylyte does not hold or spend a wallet. Without a payment, it returns the same 402 challenge the paid path sends, with the USD price and maxAmountRequired. Unknown paths and paths not on that catalogue are refused. It does not write or edit Core.

Input parameters:

- `path` (string, required): Paid path of one live offering, such as /v1/data/fees/forecast. Its priceUsd is listed on that offering.
- `payment` (string): The X-PAYMENT value already signed for this path. When it is absent, the result is the 402 challenge with the USD price and maxAmountRequired.
- `print_id` (string): Outcome id. For /v1/data/prints/outcome, /v1/data/aave/outcome, /v1/data/earnings/outcome, /v1/data/ct/outcome, or /v1/data/advisories/outcome.
- `record_id` (string): Official checked record id for one vintage. Only for /v1/data/records/checked.
- `url` (string): Public page URL. Only for /v1/data/web/title.

## Diagnostics

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

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 68
- 2026-10-22: 68
- 2026-10-21: 67
- 2026-10-20: 67
- 2026-10-19: 66
- 2026-10-18: 66
- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 63
- 2026-10-10: 62
- 2026-10-07: 61

## Common questions

### What is the Paylyte MCP server?

Paylyte is an MCP server listed in the public MCP registry as ai.paylyte/paylyte-core. Agent Trust Score earned through Proof of Outcome. Browse and buy as paylyte-core. This page covers its hosted endpoint (https://api.paylyte.ai/mcp).

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

Paylyte scores 73 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 Paylyte MCP server expose?

Paylyte exposes 3 tools: discover_live_offerings, get_track_record, buy_live_offering. Their descriptions and schemas cost roughly 599 tokens of context every time the server is loaded.

### Does the Paylyte MCP server require authentication?

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

### Is the Paylyte MCP server still maintained?

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

## Links

- Remote endpoint: https://api.paylyte.ai/mcp
- Website: https://paylyte.ai/connect
- Changelog RSS feed: https://verifymcp.io/servers/ai-paylyte-paylyte-core/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-paylyte-paylyte-core/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-paylyte-paylyte-core/api