Veyline by Payload
MCPB · VEYLINE.MCPB
Veyline by Payload: agent entitlement and usage reads, signed payment preflights. No funds move.
Available components
Last scanned (8 hours ago)
Scores higher than 78% of MCPB servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security13
- 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.Unverified
- 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).Unverified
- No install/post-install scripts declared.Pass
- 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).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 297 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability check failed: the tool surface changed between 1.0.0 and 1.1.0: 0 tool removals, 1 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.
- 27 Oct 26 +1
- Package version: 1.0.0 → 1.1.0 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.
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 5 Nov 2026 · Analysed mcpb/https://github.com/Payloadhq/veyline-mcp/releases/download/v1.1.0/veyline.mcpb@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
veyline_preflight ~223
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.)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The hosted action from the authoritative quote. |
| amount_cents | integer | yes | Amount from the authoritative quote, in cents. |
| approval_id | string | – | Optional existing operator approval identifier. |
| asset | string | yes | – |
| network | string | yes | CAIP-2 Base mainnet. |
| protocol | string | yes | – |
| provider | string | yes | – |
| quote | object | yes | Full original x402 quote; required. |
| quote_id | string | yes | Authoritative hosted quote ID. |
| recipient | string | yes | Recipient from the authoritative quote. |
| request_hash | string | yes | Original request integrity hash. |
| wallet_address | string | – | Optional enrolled wallet address. |
No output schema declared.
No examples provided.
veyline_status ~39
Read the current authenticated organization Veyline entitlement and tier. Does not authorize a payment. (Rail A2A skill veyline_status.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
veyline_usage ~35
Read the current authenticated organization quota and usage. Does not change policy. (Rail A2A skill veyline_usage.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
mcpb · veyline.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
3eb383af8e3da7377bce221f5b1e05ddae2607a30cc528a923485eebe50cb7c5
macOS / Linux
echo "3eb383af8e3da7377bce221f5b1e05ddae2607a30cc528a923485eebe50cb7c5 veyline.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\veyline.mcpb).Hash -eq "3eb383af8e3da7377bce221f5b1e05ddae2607a30cc528a923485eebe50cb7c5"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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.