dev.paypercall.extract/vend-api-merchant
REMOTE · EXTRACT.PAYPERCALL.DEV
Pay-per-call web intel: extract, search, link check, domain, geo, Nano. Settled via Nano x402.
Available components
Last scanned (13 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 16 Oct 2026.
Category Search and Retrieval
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 23 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Oct 26 0
- Schema quality: 739 → 1156 ▼ functional
- New tool “browser_agent” functional
- New tool “browser_agent_batch” functional
- New tool “scrape_page” functional
- New tool “scrape_pages” functional
- 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.
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 23 Oct 2026 · Probed https://extract.paypercall.dev/mcp
TLS unreached
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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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 | Unreachable | ||
| http (plaintext) | http://extract.paypercall.dev/mcp | HTTPS enforced |
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 →
browser_agent ~114
Run a task on a real website with a real browser: it searches, clicks, filters, reads the page and answers. Charges 0.05 XNO per run via x402. Returns a job id at once; poll jobs via the returned links.status (free) until done.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | What the agent should do, in plain language (8-500 characters). |
| website | string | yes | The website to do it on, e.g. arxiv.org or https://www.allrecipes.com |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
browser_agent_batch ~91
Start up to 100 browser-agent runs at once, in parallel on isolated browser contexts. Charges 0.05 XNO per run via x402 (price scales with the number of runs). Returns every job id immediately; poll each via its links.status (free).
| Name | Type | Req | Description |
|---|---|---|---|
| runs | string | yes | JSON list of 1-100 runs: [{"task": "...", "website": "..."}, ...] |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.
scrape_page ~102
Scrape one page with a real stealth browser — no AI. Returns the final URL, title, visible text, structured item cards (products, prices, listings) and interactive elements. Charges 0.002 XNO via x402. Fast (~1s).
| Name | Type | Req | Description |
|---|---|---|---|
| elements | boolean | – | Include the interactive-element list (ids, roles, names). |
| url | string | yes | The page to scrape, e.g. https://arxiv.org or example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
scrape_pages ~110
Scrape up to 100 pages in parallel with real stealth browsers — no AI. Returns one result per URL: final URL, title, visible text, structured item cards and interactive elements. Charges 0.002 XNO per page via x402 (price scales with the number of pages).
| Name | Type | Req | Description |
|---|---|---|---|
| elements | boolean | – | Include the interactive-element list per page. |
| urls | string | yes | JSON list of 1-100 pages to scrape: ["https://a.com", "https://b.com"] |
| 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.
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'
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 0 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 13 tools: extract_url, check_link, domain_info, web_search, geoip_lookup, and 8 more. Their descriptions and schemas cost roughly 1,156 tokens of context every time the server is loaded.
Does the dev.paypercall.extract/vend-api-merchant MCP server require authentication?
Its publisher declares no required credentials for dev.paypercall.extract/vend-api-merchant. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the dev.paypercall.extract/vend-api-merchant MCP server still maintained?
dev.paypercall.extract/vend-api-merchant has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.