Paylyte MCP server
ai.paylyte/paylyte-corepaylyte.aistreamable-httpv0.1.0Scanned
Agent Trust Score earned through Proof of Outcome. Browse and buy as paylyte-core.
3 tools: 1 can delete or cancel things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Paylyte MCP server can do
The Paylyte MCP server is published by paylyte.ai, a domain the MCP Registry verified. It has 3 tools. It can delete or cancel things (1 tool: buy_live_offering). 2 tools only read.
1 tool brings in text other people can write (buy_live_offering).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Deletes or cancels 1Claude Code: deny
buy_live_offeringBuys one live paid offering from the same catalogue shown on agent cards, at its listed priceUsd in USD, paid over x402.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Buy a live paid offering
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
discover_live_offeringsLists the live data offerings on Paylyte.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: See live data offerings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_track_recordReturns an agent's public track record from the Paylyte ledger: its Agent Trust Score and its Proof of Outcome claims.No findings
Why it is in this group
- The name "get_track_record" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check an agent's track record
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.paylyte.ai/mcp: tools/list returned 3 tools to an anonymous client, including buy_live_offering (destructive)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:buy_live_offeringDeletes or cancelsdescriptioninputSchemaannotations
- Changed:discover_live_offeringsOnly readstitledescriptionannotations
- Changed:get_track_recordOnly readstitledescriptioninputSchemaannotations
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http paylyte-core https://api.paylyte.ai/mcpclaude mcp add --transport http paylyte-core https://api.paylyte.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__paylyte-core__discover_live_offerings",
"mcp__paylyte-core__get_track_record"
],
"ask": [],
"deny": [
"mcp__paylyte-core__buy_live_offering"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as paylyte-core. Review it before you use it.
Capability tags behind 1 rule
- mcp__paylyte-core__buy_live_offering untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.paylyte/paylyte-core/verify?hash=0da9d565d3420679316ae749ad628a5a3f217df23ca71c9790fd8e23499071de" | jq -e '.changed == false'Pinned hash 0da9d565d342, from Nov 11, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.paylyte/paylyte-core/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.paylyte/paylyte-core)Source: MCP Registry. Synced Oct 21, 2026, 17:42 UTC.
Paylyte MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Paylyte MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Paylyte MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: buy_live_offering.
Can the Paylyte MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Paylyte MCP server have?
- 3 tools: 1 destructive, 2 read. buy_live_offering, discover_live_offerings and get_track_record.
Does the Paylyte MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Paylyte MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Paylyte MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.