AgentPay
REMOTE · AGENTPAY-XHS-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 20
x402 micropayments MCP: Xiaohongshu notes and paid APIs settled in USDC on Base.
Available components
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 Security74
- 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
- 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 Usability83
- 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
- Context-footprint check failed: tool/resource definitions use about 607 tokens (~121/item across 5 items; 4 tools + 1 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 Management43
- Stability observed for 13 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the AgentPay MCP server?
AgentPay is a hosted endpoint at https://agentpay-xhs-production.up.railway.app/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 · agentpay-xhs-production.up.railway.app
claude mcp add --transport http yyxqqq777-agentpay 'https://agentpay-xhs-production.up.railway.app/mcp'
{
"mcpServers": {
"yyxqqq777-agentpay": {
"url": "https://agentpay-xhs-production.up.railway.app/mcp"
}
}
} {
"servers": {
"yyxqqq777-agentpay": {
"type": "http",
"url": "https://agentpay-xhs-production.up.railway.app/mcp"
}
}
} [mcp_servers.yyxqqq777-agentpay] url = "https://agentpay-xhs-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yyxqqq777-agentpay": {
"type": "remote",
"url": "https://agentpay-xhs-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add yyxqqq777-agentpay --url 'https://agentpay-xhs-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
yyxqqq777-agentpay:
url: "https://agentpay-xhs-production.up.railway.app/mcp" {
"McpServers": {
"yyxqqq777-agentpay": {
"Transport": "http",
"Url": "https://agentpay-xhs-production.up.railway.app/mcp"
}
}
} assistant mcp add yyxqqq777-agentpay -t streamable-http -u 'https://agentpay-xhs-production.up.railway.app/mcp'
{
"mcpServers": {
"yyxqqq777-agentpay": {
"type": "http",
"url": "https://agentpay-xhs-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 7 Sept 26 73
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 20 Sept 2026 · Probed https://agentpay-xhs-production.up.railway.app/mcp/ · Declared URL https://agentpay-xhs-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| 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 agentpay-xhs-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | 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 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentpay-xhs-production.up.railway.app/mcp | Redirected | 307 | https://agentpay-xhs-production.up.railway.app/mcp/ |
| streamable-http · followed | https://agentpay-xhs-production.up.railway.app/mcp/ | Verified | 200 | |
| http (plaintext) | http://agentpay-xhs-production.up.railway.app/mcp | HTTPS enforced | 301 | https://agentpay-xhs-production.up.railway.app/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 →
agentpay_payment_status Check AgentPay payment status ~78
Return AgentPay payment configuration without charging: network, price, spending limit, payment mode, gateway URL, and agent wallet address. Call this before paid tools to verify the wallet is configured, or after a payment error.
| Name | Type | Req | Description |
|---|---|---|---|
| include_wallet | boolean | – | If true (default), include the derived agent wallet address from AGENT_PRIVATE_KEY. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
china_wholesale_pricing_query Query China wholesale pricing ~130
Search factory-direct wholesale pricing samples for a product keyword (1688 / Yiwu style catalog). Returns items with MOQ, unit price USD, factory location, and supplier verification flags. Use for China sourcing research. Settles ~0.01 USDC via x402 per query.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | – | – | Optional category filter ID when the user specifies a catalog category. |
| keyword | string | yes | Product search query in English or Chinese, e.g. 'wireless earbuds' or '蓝牙耳机'. |
| max_price | – | – | Optional maximum target unit price in USD to filter results. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
xhs_get_note_detail Get Xiaohongshu note detail ~160
Fetch one Xiaohongshu (小红书) note by share URL or 24-char note_id and return title, description, author, engagement stats, images, and video URL as JSON. Call this when the user pastes an xiaohongshu.com/explore link or a note id. Settles ~0.01 USDC via x402 on each successful call.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | Xiaohongshu note share URL or 24-character hex note_id. Example: https://www.xiaohongshu.com/explore/6a95a1f30000000026019ab7 |
| note_type | – | – | Optional media hint to speed lookup: image, video, 图文, or 视频. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
xhs_get_user_notes List Xiaohongshu user notes ~106
List posted notes for a Xiaohongshu user_id (paginated). Returns note summaries and next_cursor for pagination. Use when the user asks for a creator's recent posts. Settles ~0.01 USDC via x402 per page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | Pagination cursor from the previous response's next_cursor. Omit or null for the first page. |
| user_id | string | yes | Xiaohongshu user ID string from a profile or prior note author. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the AgentPay MCP server?
AgentPay is an MCP server listed in the public MCP registry as io.github.yyxqqq777/agentpay. x402 micropayments MCP: Xiaohongshu notes and paid APIs settled in USDC on Base. This page covers its hosted endpoint (https://agentpay-xhs-production.up.railway.app/mcp).
Is the AgentPay MCP server safe to use?
AgentPay 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 AgentPay MCP server expose?
AgentPay exposes 4 tools: xhs_get_note_detail, xhs_get_user_notes, china_wholesale_pricing_query, agentpay_payment_status. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.
Does the AgentPay MCP server require authentication?
No. We connected to AgentPay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentPay MCP server still maintained?
AgentPay is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.