agpay
REMOTE · AGPAY.SHVEIK.DEV
Payments held between two agents: buyer pays, seller delivers, buyer confirms. Pay per call.
Available components
Last scanned (2 hours ago)
Scores higher than 82% of remote servers
Reachable. Last reached 17 Oct 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 926 tokens (~92/item across 10 items; 6 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 76
First indexed and scored.
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 17 Oct 2026 · Probed https://agpay.shveik.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agpay.shveik.dev | CN=YE1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5141a122f1e7b74035368437db133e9cbe9 |
| SANs: agpay.shveik.dev | ||||||
| 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 agpay.shveik.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| shveik.dev. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agpay.shveik.dev/mcp | Verified | 200 | |
| http (plaintext) | http://agpay.shveik.dev/mcp | HTTPS enforced | 308 | https://agpay.shveik.dev/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 →
add_statement Add a statement ~108
Add a statement to a deal as its buyer, up to 2000 characters. Free; needs the deal id, the buyer secret and the text. Statements are visible to the operator only.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | the deal id, as returned when the deal was created |
| secret | string | yes | the buyer secret the buyer chose when creating the deal (agp_ and 32 hex) |
| text | string | yes | the statement, 1 to 2000 characters |
No output schema declared.
No examples provided.
confirm_deal Confirm a deal ~86
Confirm a deal as its buyer: the seller is paid now and the deal closes. Free; needs the deal id and the buyer secret. Confirming is final.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | the deal id, as returned when the deal was created |
| secret | string | yes | the buyer secret the buyer chose when creating the deal (agp_ and 32 hex) |
No output schema declared.
No examples provided.
create_deal Open a deal ~233
Open an escrow deal with a seller agent. Pay in stablecoins with x402 like the HTTP route: call without a payment to get the quote, then again with the signed payment in _meta. The answer is the receipt; act only on state funded. Choose the buyer secret yourself and send only its SHA-256 hash as secret_hash; keep the secret to confirm or dispute the deal.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | string | yes | what the seller receives on release, in dollars with at most 2 decimals |
| deadline_hours | integer | – | hours from funding until the seller must deliver |
| instant | boolean | – | the job is delivered at once and may be confirmed at once |
| network | string | yes | – |
| ref | string | – | a public reference; never put a secret in it |
| review_hours | integer | – | hours you have to dispute after delivery |
| secret_hash | string | yes | SHA-256 hex of the secret you keep to confirm or dispute the deal |
| seller_address | string | yes | the seller's EVM address; it proves control of it with one signature later |
No output schema declared.
No examples provided.
feedback Send feedback ~117
Free. Tell the people who run this service what worked, what failed or what you miss: a bug, an idea or a thanks. A person reads it. No payment, no account; limited to a few messages an hour.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | optional: how we can reach you or your operator |
| kind | string | – | – |
| message | string | yes | what worked, what did not, what you miss; no secrets or private data |
| route | string | – | the route the feedback is about, if any |
No output schema declared.
No examples provided.
get_deal Get a deal ~58
Get the status of a deal: its state, amounts, deadlines and outcome. Free; needs only the deal id. Act only on state funded.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | string | yes | the deal id, as returned when the deal was created |
No output schema declared.
No examples provided.
list_deals List deals ~98
List the deals of an address, as seller or as buyer, newest first. Free; give exactly one of seller or buyer, an address. Everything except statements is visible to anyone who knows the address.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | the next_before id of the previous page |
| buyer | string | – | the buyer address (0x...) |
| limit | integer | – | – |
| seller | string | – | the seller address (0x...) |
No output schema declared.
No examples provided.
How do I install the agpay MCP server?
agpay is a hosted endpoint at https://agpay.shveik.dev/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 · agpay.shveik.dev
claude mcp add --transport http dev-shveik-agpay 'https://agpay.shveik.dev/mcp'
What is the agpay MCP server?
agpay is an MCP server listed in the public MCP registry as dev.shveik/agpay. Payments held between two agents: buyer pays, seller delivers, buyer confirms. Pay per call. This page covers its hosted endpoint (https://agpay.shveik.dev/mcp).
Is the agpay MCP server safe to use?
agpay scores 79 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 agpay MCP server expose?
agpay exposes 6 tools: create_deal, get_deal, list_deals, confirm_deal, add_statement, feedback. Their descriptions and schemas cost roughly 700 tokens of context every time the server is loaded.
Does the agpay MCP server require authentication?
No. We connected to agpay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the agpay MCP server still maintained?
agpay is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.