# Veyline by Payload (mcpb · veyline.mcpb)

Veyline by Payload: agent entitlement and usage reads, signed payment preflights. No funds move.

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

## Components

- mcpb · `veyline.mcpb`: 48/100 (this document), [markdown](https://verifymcp.io/servers/payload-tools-veyline-mcp/veyline.md), [page](https://verifymcp.io/servers/payload-tools-veyline-mcp/veyline)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Payloadhq/veyline-mcp/releases/download/v1.1.0/veyline.mcpb`
- Version: `1.1.0`
- Transport: `stdio`
- SHA-256: `3eb383af8e3da7377bce221f5b1e05ddae2607a30cc528a923485eebe50cb7c5`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 13/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - No install/post-install scripts declared.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 297 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability check failed: the tool surface changed between 1.0.0 and 1.1.0: 0 tool removals, 1 breaking changes, 0 additions.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% 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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Veyline by Payload MCP server?

Veyline by Payload ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 3eb383af8e3da7377bce221f5b1e05ddae2607a30cc528a923485eebe50cb7c5; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Payloadhq/veyline-mcp/releases/download/v1.1.0/veyline.mcpb`
- SHA-256: `3eb383af8e3da7377bce221f5b1e05ddae2607a30cc528a923485eebe50cb7c5`

### Verify on macOS / Linux

```bash
echo "3eb383af8e3da7377bce221f5b1e05ddae2607a30cc528a923485eebe50cb7c5  veyline.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\veyline.mcpb).Hash -eq "3eb383af8e3da7377bce221f5b1e05ddae2607a30cc528a923485eebe50cb7c5"
```

## 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-04 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53.

### 2026-11-02 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47.

### 2026-10-31 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40.

### 2026-10-29 (score 45, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.

### 2026-10-27 (score 44, +1)

- [functional] Package version: 1.0.0 → 1.1.0

### 2026-10-24 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.

### 2026-10-22 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10.

### 2026-10-20 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.

## MCP tools (3)

### `veyline_status` (~39 tokens)

Read the current authenticated organization Veyline entitlement and tier. Does not authorize a payment. (Rail A2A skill veyline_status.)

### `veyline_usage` (~35 tokens)

Read the current authenticated organization quota and usage. Does not change policy. (Rail A2A skill veyline_usage.)

### `veyline_preflight` (~223 tokens)

Request a signed, short-lived, policy-enforced payment preflight. No funds are transferred. Requires Veyline execution scope and the original authoritative x402 quote. Pass the payment intent (recipient, amount, asset, network) and, when available, the original x402 quote object. (Rail A2A skill veyline_preflight.)

Input parameters:

- `action` (string, required): The hosted action from the authoritative quote.
- `amount_cents` (integer, required): Amount from the authoritative quote, in cents.
- `approval_id` (string): Optional existing operator approval identifier.
- `asset` (string, required)
- `network` (string, required): CAIP-2 Base mainnet.
- `protocol` (string, required)
- `provider` (string, required)
- `quote` (object, required): Full original x402 quote; required.
- `quote_id` (string, required): Authoritative hosted quote ID.
- `recipient` (string, required): Recipient from the authoritative quote.
- `request_hash` (string, required): Original request integrity hash.
- `wallet_address` (string): Optional enrolled wallet address.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/payload-tools-veyline-mcp/veyline#diagnostics

## Score history

- 2026-11-05: 48
- 2026-11-04: 48
- 2026-11-03: 47
- 2026-11-02: 47
- 2026-11-01: 46
- 2026-10-31: 46
- 2026-10-30: 45
- 2026-10-29: 45
- 2026-10-28: 44
- 2026-10-27: 44
- 2026-10-26: 43
- 2026-10-25: 43
- 2026-10-24: 43
- 2026-10-23: 42
- 2026-10-22: 42
- 2026-10-21: 41
- 2026-10-20: 41
- 2026-10-19: 40
- 2026-10-18: 40
- 2026-10-17: 40
- 2026-10-16: 40
- 2026-10-15: 42
- 2026-10-14: 42
- 2026-10-13: 13

## Common questions

### What is the Veyline by Payload MCP server?

Veyline by Payload is an MCP server listed in the public MCP registry as io.github.payload-tools/veyline-mcp. Veyline by Payload: agent entitlement and usage reads, signed payment preflights. No funds move. This page covers its MCPB bundle (https://github.com/Payloadhq/veyline-mcp/releases/download/v1.1.0/veyline.mcpb).

### Is the Veyline by Payload MCP server safe to use?

Veyline by Payload scores 48 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 Veyline by Payload MCP server expose?

Veyline by Payload exposes 3 tools: veyline_status, veyline_usage, veyline_preflight. Their descriptions and schemas cost roughly 297 tokens of context every time the server is loaded.

### What licence is the Veyline by Payload MCP server under?

Veyline by Payload declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/Payloadhq/veyline-mcp
- Website: https://payloadhq.github.io/veyline.html
- Changelog RSS feed: https://verifymcp.io/servers/payload-tools-veyline-mcp/veyline.xml
- Changelog JSON feed: https://verifymcp.io/servers/payload-tools-veyline-mcp/veyline.json
- HTML version of this page: https://verifymcp.io/servers/payload-tools-veyline-mcp/veyline