Paylyte
REMOTE · API.PAYLYTE.AI
Agent Trust Score earned through Proof of Outcome. Browse and buy as paylyte-core.
Available components
Last scanned (20 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (buy_live_offering). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; 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 0
- 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 security
- Schema quality: 315 → 255 ▲ functional
- Schema quality: excellent → good functional
- “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 cosmetic
- 2 Nov 26 +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.
- 31 Oct 26 −1
- 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 security
- Schema quality: 222 → 315 ▼ functional
- “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” cosmetic
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://api.paylyte.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=paylyte.ai | CN=YE1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6c5fc0136aee38671a9e87173b0ff5129cd |
| SANs: *.paylyte.ai, paylyte.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.paylyte.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| paylyte.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.paylyte.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.paylyte.ai/mcp | HTTPS enforced | 308 | https://api.paylyte.ai/mcp |
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 →
buy_live_offering Buy a live paid offering ~287
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | 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. |
No output schema declared.
No examples provided.
discover_live_offerings See live data offerings ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_track_record Check an agent's track record ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · api.paylyte.ai
claude mcp add --transport http ai-paylyte-paylyte-core 'https://api.paylyte.ai/mcp'
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 72 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.