dev.paypercall.extract/vend-api-merchant
REMOTE · EXTRACT.PAYPERCALL.DEV · SCANNED OCT 15
Pay-per-call web intel: extract, search, link check, domain, geo, Nano. Settled via Nano x402.
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 Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 739 tokens (~82/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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 dev.paypercall.extract/vend-api-merchant MCP server?
dev.paypercall.extract/vend-api-merchant is a hosted endpoint at https://extract.paypercall.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 · extract.paypercall.dev
claude mcp add --transport http dev-paypercall-extract-vend-api-merchant 'https://extract.paypercall.dev/mcp'
{
"mcpServers": {
"dev-paypercall-extract-vend-api-merchant": {
"url": "https://extract.paypercall.dev/mcp"
}
}
} {
"servers": {
"dev-paypercall-extract-vend-api-merchant": {
"type": "http",
"url": "https://extract.paypercall.dev/mcp"
}
}
} [mcp_servers.dev-paypercall-extract-vend-api-merchant] url = "https://extract.paypercall.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-paypercall-extract-vend-api-merchant": {
"type": "remote",
"url": "https://extract.paypercall.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-paypercall-extract-vend-api-merchant --url 'https://extract.paypercall.dev/mcp' --transport streamable-http
mcp_servers:
dev-paypercall-extract-vend-api-merchant:
url: "https://extract.paypercall.dev/mcp" {
"McpServers": {
"dev-paypercall-extract-vend-api-merchant": {
"Transport": "http",
"Url": "https://extract.paypercall.dev/mcp"
}
}
} assistant mcp add dev-paypercall-extract-vend-api-merchant -t streamable-http -u 'https://extract.paypercall.dev/mcp'
{
"mcpServers": {
"dev-paypercall-extract-vend-api-merchant": {
"type": "http",
"url": "https://extract.paypercall.dev/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.
- 14 Oct 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 80. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 73. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 53 to 63. That category is still filling its 30-day observation window: 16 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.
- 3 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.
- 1 Oct 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.
- 29 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 15 Oct 2026 · Probed https://extract.paypercall.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=extract.paypercall.dev | CN=YE2,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5c34dd3401cdb989390f62dc57eb8a377db |
| SANs: extract.paypercall.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 extract.paypercall.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| paypercall.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://extract.paypercall.dev/mcp | Verified | 200 | |
| http (plaintext) | http://extract.paypercall.dev/mcp | HTTPS enforced | 308 | https://extract.paypercall.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 →
check_link ~58
Check HTTP status, response time and redirect chain for any URL. Charges 0.0001 XNO in Nano via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full http(s) URL whose HTTP status, response time and redirect chain to check. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_url_status ~108
One-call URL status check: final HTTP status, redirect chain, TLS validity and days-to-expiry, response time, and whether the body changed since a previous call (pass previous_hash). Charges 0.0001 XNO in Nano via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| previous_hash | string | – | Optional hash of the body from a previous call, used to detect content drift. |
| url | string | yes | Full http(s) URL whose status, redirect chain, TLS validity and content to check. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
domain_info ~71
Full domain intelligence: DNS records, WHOIS registration, SSL/TLS certificate, HTTP headers. Charges 0.0005 XNO in Nano via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name (e.g. example.com) to look up DNS, WHOIS, SSL/TLS and headers for. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
extract_url ~57
Extract clean text and markdown from a web page URL. Charges 0.0001 XNO in Nano via x402 protocol.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full http(s) URL of the web page to extract clean text/markdown from. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
geoip_lookup ~84
IP geolocation lookup: country, city, coordinates, ISP, ASN, timezone. Use 'myip' for the caller's own IP. Charges 0.0001 XNO in Nano via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4/IPv6 address to geolocate, or the literal 'myip' to use the caller's own IP. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
mcp_find ~144
Search paid MCP and x402 service directories for a task. Returns matching services with their settlement rails, prices, and x402 health. Optional filter_rail='nano' shows only XNO-settling services. Charges 0.0001 XNO in Nano via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| filter_rail | string | – | Optional rail filter — pass 'nano' to show only services that settle in Nano (XNO), 'base' for USDC on Base, etc. |
| limit | integer | – | Max results to return (1-50), default 10. |
| q | string | yes | Natural-language query — what the MCP or x402 service should do. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
nano_account_info ~75
Nano account intelligence: balance, representative, block count, frontier, weight, pending transactions. Charges 0.0005 XNO in Nano via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Nano account address (nano_... or xrb_...) to look up balance, representative, block count, frontier, weight, pending. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
web_search ~57
Web search via DuckDuckGo. Returns structured results with titles, URLs, and snippets. Charges 0.0001 XNO in Nano via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Search query string to run through the web search backend. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
youtube_transcript ~85
Extract captions and transcript from a YouTube video URL. Returns timestamped segments and model-sized chunks with deep-linked citations. Charges 0.0005 XNO in Nano via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language code for the transcript (default 'en'). |
| url | string | yes | YouTube video URL (watch, youtu.be, embed or shorts format). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the dev.paypercall.extract/vend-api-merchant MCP server?
dev.paypercall.extract/vend-api-merchant is an MCP server listed in the public MCP registry as dev.paypercall.extract/vend-api-merchant. Pay-per-call web intel: extract, search, link check, domain, geo, Nano. Settled via Nano x402. This page covers its hosted endpoint (https://extract.paypercall.dev/mcp).
Is the dev.paypercall.extract/vend-api-merchant MCP server safe to use?
dev.paypercall.extract/vend-api-merchant scores 85 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 dev.paypercall.extract/vend-api-merchant MCP server expose?
dev.paypercall.extract/vend-api-merchant exposes 9 tools: extract_url, check_link, domain_info, web_search, geoip_lookup, and 4 more. Their descriptions and schemas cost roughly 739 tokens of context every time the server is loaded.
Does the dev.paypercall.extract/vend-api-merchant MCP server require authentication?
No. We connected to dev.paypercall.extract/vend-api-merchant without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.paypercall.extract/vend-api-merchant MCP server still maintained?
dev.paypercall.extract/vend-api-merchant is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.