PayAPI Market
REMOTE · PAYAPI.MARKET · SCANNED SEP 20
Search settlement-verified x402 APIs. Discovery is free. Agents pay the provider 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 553 tokens (~184/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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% 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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the PayAPI Market MCP server?
PayAPI Market is a hosted endpoint at https://payapi.market/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 · payapi.market
claude mcp add --transport http market-payapi-marketplace 'https://payapi.market/mcp'
{
"mcpServers": {
"market-payapi-marketplace": {
"url": "https://payapi.market/mcp"
}
}
} {
"servers": {
"market-payapi-marketplace": {
"type": "http",
"url": "https://payapi.market/mcp"
}
}
} [mcp_servers.market-payapi-marketplace] url = "https://payapi.market/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"market-payapi-marketplace": {
"type": "remote",
"url": "https://payapi.market/mcp",
"enabled": true
}
}
} openclaw mcp add market-payapi-marketplace --url 'https://payapi.market/mcp' --transport streamable-http
mcp_servers:
market-payapi-marketplace:
url: "https://payapi.market/mcp" {
"McpServers": {
"market-payapi-marketplace": {
"Transport": "http",
"Url": "https://payapi.market/mcp"
}
}
} assistant mcp add market-payapi-marketplace -t streamable-http -u 'https://payapi.market/mcp'
{
"mcpServers": {
"market-payapi-marketplace": {
"type": "http",
"url": "https://payapi.market/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 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.
- 18 Sept 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.
- 16 Sept 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.
- 14 Sept 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.
- 12 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.
- 10 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.
- 7 Sept 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.
- 5 Sept 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.
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://payapi.market/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=payapi.market | CN=YR2,O=Let's Encrypt,C=US | 12 Aug 2026 | 10 Nov 2026 | RSA 2048 | SHA256-RSA | 53a8af071e8aeab61d390dc34ed91a31462 |
| SANs: payapi.market | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of payapi.market. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| market. | present | 40531 | 8 | Verified |
| payapi.market. | 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=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://cloud.umami.is https://js.stripe.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://cloud.umami.is https://gateway.umami.is https://web-production-18a32.up.railway.app https://api.airtable.com; frame-src https://js.stripe.com https://hooks.stripe.com https://checkout.stripe.com; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self "https://js.stripe.com"), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://payapi.market/mcp | Verified | 200 | |
| http (plaintext) | http://payapi.market/mcp | HTTPS enforced | 308 | https://payapi.market/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 →
get_api Get one PayAPI Market listing ~165
Fetch a single live listing by its id or slug, including base_url, price range, network and verification state. Also returns a reliability object: score (0 to 100 or null), band (strong, established, thin, caution or unscored) and computed_at. Reliability is a running score from paid verifications, health history and payTo integrity, not a star rating and not a guarantee; unscored means it has not been computed for that listing yet. Method: https://payapi.market/how-an-agent-finds-payapi. Returns the listing whether or not it is verified, and reports payment_verified honestly. Free and read-only; spends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Listing uuid or slug, as returned by search_apis or list_apis. |
No output schema declared.
No examples provided.
list_apis List the PayAPI Market catalogue ~82
Browse the live catalogue, optionally filtered to one category. Omit category for everything. Returns settlement-verified listings only unless verified_only is false. Free and read-only; spends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Exact category name. Call with no category first to see the valid values. |
| limit | integer | – | – |
| verified_only | boolean | – | – |
No output schema declared.
No examples provided.
search_apis Search the PayAPI Market catalogue ~98
Free-text search across the live catalogue. Matches listing name, description, category and provider name. Returns settlement-verified listings only unless verified_only is false. Free and read-only; spends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | What you are looking for, e.g. "uk property" or "sanctions screening". |
| verified_only | boolean | – | Restrict to settlement-verified listings. Default true. |
No output schema declared.
No examples provided.
What is the PayAPI Market MCP server?
PayAPI Market is an MCP server listed in the public MCP registry as market.payapi/marketplace. Search settlement-verified x402 APIs. Discovery is free. Agents pay the provider in USDC on Base. This page covers its hosted endpoint (https://payapi.market/mcp).
Is the PayAPI Market MCP server safe to use?
PayAPI Market scores 73 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 PayAPI Market MCP server expose?
PayAPI Market exposes 3 tools: search_apis, list_apis, get_api. Their descriptions and schemas cost roughly 345 tokens of context every time the server is loaded.
Does the PayAPI Market MCP server require authentication?
No. We connected to PayAPI Market without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PayAPI Market MCP server still maintained?
PayAPI Market 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.