Agent Paywire library
REMOTE · MCP.AGENTPAYWIRE.COM
Library (L402, x402, Lightning, stablecoins): 18 read-only tools plus 3 writers.
Available components
Last scanned (23 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability50
- 22% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6293 tokens (~209/item across 30 items; 21 tools + 9 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 Management0
- Stability check failed: schema churn in the 15 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 16 additions. See how to fix → Fail
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 0
- Tool “get_protocol_facts” rewrote its description, which is the text the model reads security
- Tool “get_sdk_security” rewrote its description, which is the text the model reads security
- 1 Nov 26 0
- Tool “get_sdk_security” rewrote its description, which is the text the model reads security
- 29 Oct 26 0
- Tool “get_protocol_facts” rewrote its description, which is the text the model reads security
- 26 Oct 26 0
- Tool “get_support_info” rewrote its description, which is the text the model reads security
- Tool “get_trust_checklist” rewrote its description, which is the text the model reads security
- 24 Oct 26 0
- Schema quality: 5502 → 6183 ▼ functional
- Server version: 1.0.2 → 1.1.0 functional
- Server version: 1.0.1 → 1.0.2 functional
- New tool “check_payment_endpoint” functional
- New tool “create_alert” functional
- New tool “get_verification_status” functional
- New tool “list_alert_topics” functional
- New tool “get_sdk_security” functional
- 23 Oct 26 +8
- HTTPS: unverified → pass ▲ security
- DNSSEC: fail → pass ▲ security
- HSTS header: fail → pass ▲ security
- Tool “list_changes” rewrote its description, which is the text the model reads security
- Tool “get_bot” rewrote its description, which is the text the model reads security
- Tool “get_source” rewrote its description, which is the text the model reads security
- Tool “list_bots” rewrote its description, which is the text the model reads security
- Tool “search_sources” rewrote its description, which is the text the model reads security
- Schema quality: 4377 → 5502 ▼ functional
- Schema quality: 4377 → 5440 ▼ functional
- Schema quality: 13% → 22% ▲ functional
- Destructive annotations: pass → 100 functional
- New resource “reviews” functional
- Server version: 1.0.0 → 1.0.1 functional
- New tool “get_reviews” functional
- New tool “request_missing_data” functional
- New tool “submit_review” functional
- “search_sources” added an optional parameter “status” cosmetic
- 22 Oct 26 −1
- Tool “get_article” rewrote its description, which is the text the model reads security
- Tool “get_bot” rewrote its description, which is the text the model reads security
- Tool “get_dataset” rewrote its description, which is the text the model reads security
- Tool “get_protocol_facts” rewrote its description, which is the text the model reads security
- Tool “get_source” rewrote its description, which is the text the model reads security
- Tool “get_support_info” rewrote its description, which is the text the model reads security
- Tool “get_trust_checklist” rewrote its description, which is the text the model reads security
- Tool “list_articles” rewrote its description, which is the text the model reads security
- Tool “list_bots” rewrote its description, which is the text the model reads security
- Tool “list_categories” rewrote its description, which is the text the model reads security
- Tool “list_changes” rewrote its description, which is the text the model reads security
- Tool “list_datasets” rewrote its description, which is the text the model reads security
- Tool “search_sources” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “get_article” reworded the description of “slug” cosmetic
- “get_bot” reworded the description of “id” cosmetic
- “get_dataset” reworded the description of “id” cosmetic
- “get_source” reworded the description of “id” cosmetic
- “list_changes” reworded the description of “cursor” cosmetic
- “list_changes” made “cursor” optional cosmetic
- 21 Oct 26 +1
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “changes_since” was removed ▼ security
- Tool “latest_sources” was removed ▼ security
- Tool “protocol_facts” was removed ▼ security
- Tool “search” was removed ▼ security
- Tool “search_library” was removed ▼ security
- Tool “get_article” rewrote its description, which is the text the model reads security
- Tool “get_source” rewrote its description, which is the text the model reads security
- Tool “get_support_info” rewrote its description, which is the text the model reads security
- Tool “list_articles” rewrote its description, which is the text the model reads security
- Tool “list_categories” rewrote its description, which is the text the model reads security
- Schema quality: 37 → 100 ▼ functional
- Tool “get_article” now declares an output schema ▲ functional
- Tool “get_source” now declares an output schema ▲ functional
- Tool “get_support_info” now declares an output schema ▲ functional
- Tool “list_articles” now declares an output schema ▲ functional
- Tool “list_categories” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- New tool “get_bot” functional
- New tool “get_dataset” functional
- New tool “get_protocol_facts” functional
- New tool “get_trust_checklist” functional
- New tool “list_bots” functional
- New tool “list_changes” functional
- New tool “list_datasets” functional
- New tool “search_sources” functional
- “get_article” reworded the description of “slug” cosmetic
- “get_source” reworded the description of “id” cosmetic
- Tool “get_article” changed its title: Read one article cosmetic
- Tool “get_source” changed its title: Get one library source cosmetic
- Tool “get_support_info” changed its title: Read support and paid-API details cosmetic
- Tool “list_articles” changed its title: List published articles cosmetic
- Tool “list_categories” changed its title: List library categories cosmetic
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 4 Nov 2026 · Probed https://mcp.agentpaywire.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentpaywire.com | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ca93302e8e9ca7230e3ddcbde4146faf |
| SANs: agentpaywire.com, mcp.agentpaywire.com, *.mcp.agentpaywire.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.agentpaywire.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agentpaywire.com. | present | 2371 | 13 | Verified |
| mcp.agentpaywire.com. | Verified address RRset verified with the apex keys |
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=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agentpaywire.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.agentpaywire.com/mcp | HTTPS enforced | 301 | https://mcp.agentpaywire.com/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_payment_endpoint Check a payment endpoint ~144
Check a public http(s) URL for an L402, x402, or MPP challenge and for agent discovery files. Two free reports per client per 24 hours, using the same client identification as GET /v1/changes. After that, the tool returns payment info for GET https://api.agentpaywire.com/v1/check and does not run the probe. Private, localhost, and metadata URLs are rejected. url is required. report.protocol is the passing challenge ids in the order l402, x402, mpp, joined with +, or null when none pass.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Required public http or https URL of the payment endpoint. |
| Name | Type | Req | Description |
|---|---|---|---|
| payment_required | boolean | – | – |
| report | object | – | – |
No examples provided.
create_alert Create a change alert ~111
Return payment info for a 30-day signed webhook. 2000 sats or 2.00 USD. This tool does not create the subscription. Pay POST https://api.agentpaywire.com/v1/alerts. webhook_url and topics are echoed so the client can retry that call. topics are sdk-security, lightning-releases, lightning-wallets, and protocol-specs.
| Name | Type | Req | Description |
|---|---|---|---|
| topics | array | yes | Required topic ids. |
| webhook_url | string | yes | Required public https URL that will receive POST deliveries. |
| Name | Type | Req | Description |
|---|---|---|---|
| payment_required | boolean | yes | – |
| price_sats | number | yes | – |
| price_usd | string | yes | – |
No examples provided.
get_article Read one article ~250
Return one of this site's own articles. Output is { slug, markdown }. markdown is the article file with YAML front matter, and the same text is the tool content. Parameter slug is required and must match articles[].slug from list_articles. Example: machine-native-economy. Do not include the article: prefix that list_changes uses. A missing slug is rejected as invalid input. An unknown slug returns isError with text No article with slug <slug>. A failed read returns isError whose text is the Error message (Fetch failed <status> <url> when the HTTP status is not OK), or Article fetch failed. when the failure is not an Error. Use list_articles instead when you do not have a slug. Use get_source instead for a third-party library source. Use search_sources instead to find papers and docs. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Required. Article slug exactly as in list_articles articles[].slug, e.g. machine-native-economy. Lowercase words separated by hyphens. Do not include the article: prefix that list_changes uses. A mis… |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | – |
| slug | string | yes | – |
No examples provided.
get_bot Get one verified bot ~370
Return one entry from the bot catalog by exact id. Output is that entry alone, not wrapped in entries or count: id, name, maker, description, protocols (strings), url, license (string or null), license_verified, license_url (string or null), verified_at (YYYY-MM-DD), http_status (integer or null), archive_url (string or null), funds_or_keys, and notes. funds_or_keys is true when the software can access a wallet or keys. Parameter id is required. It must equal list_bots entries[].id. Catalog ids are lowercase letters, digits, and hyphens. Example: lnget. Do not include the bot: prefix that list_changes uses; strip it first. A missing id is rejected as invalid input. An unknown id returns isError with text No bot with id <id>. A failed read of /bots.json returns isError. The text is the Error message (Fetch failed <status> <url> when the HTTP status is not OK), or Bot lookup failed. when the failure is not an Error. Use get_bot instead of list_bots when you already have one id. Use list_bots instead when you need the catalog, the count, the disclaimer, or the inclusion rule, or when you do not know the id. Use search_sources instead for papers and docs about agents. Listed, not endorsed. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Required. Exact entries[].id from list_bots. Catalog ids are lowercase letters, digits, and hyphens. Example: lnget. Do not include the bot: prefix that list_changes uses; strip it first. A missing i… |
| Name | Type | Req | Description |
|---|---|---|---|
| archive_url | string|null | yes | – |
| description | string | yes | – |
| funds_or_keys | boolean | yes | – |
| http_status | – | yes | – |
| id | string | yes | – |
| license | string|null | yes | – |
| license_url | string|null | yes | – |
| license_verified | boolean | yes | – |
| maker | string | yes | – |
| name | string | yes | – |
| notes | string | yes | – |
| protocols | array | yes | – |
| url | string | yes | – |
| verified_at | string | yes | – |
No examples provided.
get_dataset Get one dataset card ~318
Return one dataset card from /datasets/<id>/card.json. Output is one object: id, name, publisher, url, license (string or null), license_verified, license_url (string or null), approx_size, size_bytes (integer or null), format, access (open, login, or terms-acceptance), relevance, mirror_allowed, verified_at, http_status (integer or null), archive_url (string or null), data_period (string or null), sample_url (string or null), and notes. A card is metadata only and does not download dataset files; follow url for the data. Parameter id is required and must match list_datasets entries[].id. Example: agentpaywire-library. Do not include the dataset: prefix that list_changes uses. A missing id is rejected as invalid input. An unknown id returns isError with text Fetch failed 404 <card url>. A failed read for another status uses that same Fetch failed <status> <url> text. Use list_datasets instead when you need the catalog or do not know the id. Use search_sources with category datasets-benchmarks instead for papers about datasets. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Required. Dataset id exactly as in list_datasets entries[].id, e.g. agentpaywire-library. Lowercase letters, digits, and hyphens. Do not include the dataset: prefix that list_changes uses. A missing… |
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | yes | – |
| id | string | yes | – |
| mirror_allowed | boolean | yes | – |
| name | string | yes | – |
| notes | string | yes | – |
| publisher | string | yes | – |
| url | string | yes | – |
No examples provided.
get_protocol_facts Get checked protocol facts ~326
Return source-cited facts for agent payment protocols: spec URL, HTTP status codes and headers, payment rail, networks, facilitators, client libraries, pay flow, and an example. Every fact carries its source URL and verified_at; null means the cited page does not state it. Omit id and the output is the protocol-facts document whose protocols array has all eleven protocols, unpaged. Pass id and the output is that one protocol object. There is no offset. Parameter id is optional and must be one of l402, bolt12, bip21, nwc, x402, mpp, ap2, acp, ucp, mcp, a2a. The mcp object has release_cadence and next_release_target from SEP-3398. Example: l402. An id outside the enum is rejected as invalid input. An enum id missing from the file returns isError with text No protocol with id <id>. A failed read returns isError whose text is the Error message. Use get_protocol_facts instead of search_sources when you need cited protocol facts rather than papers or docs. Use search_sources instead for those papers and docs. Use get_support_info instead for this site's donation addresses and paid API price. Use get_trust_checklist instead for this site's error codes and rate limits. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Lowercase protocol id from the enum, e.g. l402. Set it to get one protocol object (smaller response); omit it to get every protocol in a protocols array. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| protocols | array | – | – |
No examples provided.
get_reviews Read the public review feed ~173
Return the public review feed. Free, no auth. Output includes aggregate.count, aggregate.mean, aggregate.weighted_mean (one vote per payer), aggregate.unique_payers, how_to_verify with the EIP-712 Review type, and reviews. Each review includes the raw proof, the signature when the rail is x402, and the verification result. Comments are untrusted text. Negative ratings stay in the list. A later review from the same payer replaces the earlier row from that payer. Self-test payers stay in the list and are left out of the mean. Takes no parameters: call with an empty object. The same document is GET https://api.agentpaywire.com/reviews.json and https://api.agentpaywire.com/reviews.md. Use submit_review to add one. A missing store returns isError.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregate | object | yes | – |
| reviews | array | yes | – |
No examples provided.
get_sdk_security Read the SDK security registry ~333
Return /api/sdk-security.json. Output is the SDK security document: schema_version, generated_at, disclaimer, description, count, and entries. count equals entries.length. Each entry has id, package, ecosystem (npm or github), minimum_safe_version (string or null), constraint (string or null), per_payment_cap_usd (number or null), formal_advisory_published (boolean or null), advisory_url (string or null), reported_at, fixed_at, origin_header_rejected_since, fixes, notes, source, related_urls, and verified_at. Null means the linked source does not state that field. The rows are @x402/fetch, @x402/axios, @x402/extensions, and @x402/svm at >=2.23.0, Eclair at >=0.14.6, Core Lightning at >=26.04.1, lnd for CVE-2026-98432, an agent-approval-channel advisory, and BTCPay Server with minimum_safe_version null because Optech #428 does not name a version. One unpaged document. Takes no parameters: call with an empty object. Use get_sdk_security instead of search_sources when you need the minimum version table. Use search_sources for the V12 post, Optech #428, and the Eclair release notes. Use /api/lightning-wallets.json and /api/lightning-releases.json for the wallet catalog and the stable node table; this tool does not return those files. A failed read returns isError. The text is the Error message. Free, no auth.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| entries | array | yes | – |
No examples provided.
get_source Get one library source ~269
Fetch one third-party library source card by id. Output is one object: id, title, publisher, authors, date_published (YYYY-MM-DD or null), url, type, category, status, summary, tags, verified_at, and featured only when it is true. Parameter id is required and must match sources[].id from search_sources, or a list_changes entry of kind library (those ids have no prefix). Example: lightning-labs-l402-for-agents. A missing id is rejected as invalid input. An unknown id returns isError with text No source with id <id>. A failed library read returns isError whose text is the Error message. Use search_sources instead when you have no id or need a filtered list (limit 1-50, no offset). Use list_categories instead when you need the category list. Use get_article instead for this site's own articles. Use list_changes instead for changelog rows. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Required. Source id exactly as in search_sources sources[].id, e.g. lightning-labs-l402-for-agents. Case and hyphens must match. Library changelog ids have no prefix. A missing id is invalid input. A… |
| Name | Type | Req | Description |
|---|---|---|---|
| authors | array | yes | – |
| category | string | yes | – |
| date_published | string|null | yes | – |
| featured | boolean | – | – |
| id | string | yes | – |
| publisher | string | yes | – |
| status | string | – | – |
| summary | string | yes | – |
| tags | array | yes | – |
| title | string | yes | – |
| type | string | yes | – |
| url | string | yes | – |
| verified_at | string | yes | – |
No examples provided.
get_support_info Read support and paid-API details ~452
Return the whole voluntary support document from /support.json. Output fields: voluntary (true), purpose, data_is_free (true), access_conditional_on_payment (false), methods, suggested_amounts_sats, suggested_amounts_optional (true), note, updated (YYYY-MM-DD), warning, usdc_contracts_source, and paid_api while the paid API is live. methods[].type is bitcoin-onchain (P2WPKH native-segwit mainnet address, bip21_uri, qr_svg, qr_text), lightning-bolt12 (offer, uri, bip21_uri, qr_svg, qr_text), evm-stablecoin (asset USDC; network Base, Ethereum, or Arbitrum One; chain_id, address, token_contract, eip681_uri; Base is primary and has the QR fields), or solana-stablecoin (asset USDC, network Solana, address, mint, uri, qr_svg, qr_text). suggested_amounts_sats is an array of optional satoshi tip amounts, not a price. paid_api has live, paid, protocol L402, payment Lightning, url, price_sats 100, credits 100, ttl_days 30, and note. One document, unpaged. Takes no parameters: call with an empty object. Calling it never sends money and never creates an invoice. Use get_support_info instead of get_trust_checklist when you need a donation address, a payment URI, a QR link, suggested sat amounts, or the paid_api price block. Use get_trust_checklist instead when you need error codes, the rate-limit policy (no client limit; feedback and review caps are HTTP 429 with Retry-After; a wallet limit, a store failure, and a rate-limited deep health probe stay HTTP 503), stable URLs, or met/partial checklist status. Use get_protocol_facts instead when you need how a third-party payment protocol works. A failed read returns isError. The text is the Error message (Fetch failed <status> <url> when the HTTP status is not OK), or Support lookup failed. when the failure is not an Error. Free, no auth.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| methods | array | yes | – |
| voluntary | boolean | yes | – |
No examples provided.
get_trust_checklist Read the trust checklist ~307
Return the whole /trust.json agent trust checklist for agentpaywire.com. Output includes title, description, free_data, items, count (items.length), tools, errors, wallet_error_codes, rate_limits, credits, urls, error_body, usage, and authorization. Each item has id, title, status (met or partial), statement, and evidence URLs. tools lists the advertised MCP tool names. rate_limits.http_429 is true and rate_limits.client is null. Feedback and review caps are HTTP 429 with Retry-After (feedback_rate_limited, review_rate_limited). A Lightning wallet rate limit, a store failure (feedback_store, review_store, review_rpc), and a rate-limited deep health probe stay HTTP 503. credits repeats price_sats, credits, and ttl_days. One unpaged document. Takes no parameters: call with an empty object. Use get_trust_checklist instead of get_support_info when you need error codes, the rate-limit policy, stable URLs, credit terms, or met/partial status. Use get_support_info instead when you need donation addresses, payment URIs, QR links, or the paid_api price block. Use get_protocol_facts instead for third-party protocol facts. A failed read returns isError. The text is the Error message (Fetch failed <status> <url> when the HTTP status is not OK), or Trust checklist failed. when the failure is not an Error. Free, no auth.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| title | string | yes | – |
| tools | array | yes | – |
No examples provided.
get_verification_status Read a verification status ~75
Read one paid provider verification by id. Free, no auth. The id comes from POST https://api.agentpaywire.com/v1/verify. An unknown id returns isError. Output includes status, checked_at, report_url, and paid_verification.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Required verification id, a UUID. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| paid_verification | boolean | yes | – |
| status | string | yes | – |
No examples provided.
list_alert_topics List alert topics ~47
List webhook topics and the source URL each one watches. Free, no auth. Takes no parameters. Topics are sdk-security, lightning-releases, lightning-wallets, and protocol-specs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| topics | array | yes | – |
No examples provided.
list_articles List published articles ~156
List all of this site's own published articles in one unpaged response. Output is { articles: [{ slug, title, summary, date, status, tags, url, md_url }] }. There is no limit or offset. Takes no parameters: call with an empty object. Use get_article instead when you have a slug and need the Markdown. Use search_sources instead for third-party papers, specs, and reports. Use list_changes instead for recent edits (article rows prefix the id with article:). A failed read returns isError. The text is the Error message (Fetch failed <status> <url> when the HTTP status is not OK), or Article list failed. when the failure is not an Error. Free, no auth.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| articles | array | yes | – |
No examples provided.
list_bots List verified agents and bots ~374
Return the whole /bots.json catalog of public agents and bots that pay, get paid, or connect a wallet. Output is { schema_version, generated_at, language, title, description, disclaimer, inclusion, schema, html_url, markdown_url, count, entries }. count equals entries.length. disclaimer is "Listed, not endorsed." The inclusion field states the rule: a public repository or demo, a known maker, a push in the 12 months before verification, and a license taken from a LICENSE file or marked unconfirmed. Each entries[] item is the same object get_bot returns: id, name, maker, description, protocols, url, license (string or null), license_verified, license_url (string or null), verified_at (YYYY-MM-DD), http_status (integer or null), archive_url (string or null), funds_or_keys, and notes. funds_or_keys is true when the software can access a wallet or keys. One unpaged response: no limit, no offset, and no text filter. Takes no parameters: call with an empty object. Use list_bots instead of get_bot when you need every entry, the count, the disclaimer, or the inclusion rule. Use get_bot instead when you already have one id and want that single object; an unknown id is an error on get_bot, not an empty list here. Use search_sources instead for papers and docs about agents. Use get_protocol_facts instead for how a payment protocol works. list_changes rows of kind bot prefix the id with bot:; strip that prefix before get_bot. A failed read returns isError. The text is the Error message (Fetch failed <status> <url> when the HTTP status is not OK), or Bot list failed. when the failure is not an Error. Free, no auth.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| disclaimer | string | yes | – |
| entries | array | yes | – |
No examples provided.
list_categories List library categories ~261
Return the closed list of eight library categories and nothing else. Output is { categories: [{ id, label, featured, count, json_url, markdown_url, html_url }] }. id is the category id, for example bitcoin-lightning. label is the display name. featured is true only for Bitcoin and Lightning, which is first. count is how many library sources are in that category. json_url, markdown_url, and html_url are absolute links to that category JSON, Markdown, and HTML. There is no source array and no top-level count. Takes no parameters: call with an empty object. The list is unpaged and always the full set; there is no limit or offset. Use list_categories instead of search_sources when you need category ids, labels, or counts. Use search_sources instead when you need the source cards in a category (pass category, for example bitcoin-lightning; limit 1-50, no offset). Use get_source instead when you already have a source id. A failed read of the library file returns isError. The text is the Error message (Fetch failed <status> <url> when the HTTP status is not OK), or Category list failed. when the failure is not an Error. Free, no auth.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
No examples provided.
list_changes List changes after a date ~532
Sync records whose verified_at is later than cursor (exclusive) across library sources, articles, datasets, bots, and support notes. Output is { cursor, count, entries }. cursor is the YYYY-MM-DD that was applied. count is the number of rows in that window. Each entry has kind (article, library, support, dataset, or bot), id, title, url, and verified_at. Some rows also include md_url, category, date_published, or note. Omit cursor to apply an exclusive cursor of UTC today minus 30 days; the response cursor is that date. Pass a YYYY-MM-DD cursor to sync from a stored date. There is no text filter, no limit, and no offset, so an old cursor can return the whole catalog (over 100 entries, about 43 KB). A cursor that is not YYYY-MM-DD returns isError with text cursor must be YYYY-MM-DD. A failed read returns isError whose text is the Error message. This free list is the raw changelog: it is not grouped by protocol and it is not Markdown, and it does not return source cards. Use search_sources instead when you want to browse or filter the library, including newest-first and updated_since (limit 1-50, no offset). Use list_categories, list_articles, list_datasets, list_bots, or get_support_info instead when you want the current full document rather than changelog rows. Use get_trust_checklist instead for the trust checklist. For one record, strip article: before get_article, dataset: before get_dataset, and bot: before get_bot. Library ids have no prefix; use get_source. Support rows have no per-id getter; use get_support_info or get_trust_checklist. Paid GET https://api.agentpaywire.com/v1/changes returns library source cards only, for an inclusive verified_at window, with protocol, category, and new-or-updated filters, as JSON or Markdown. Each client gets 5 unpaid calls per rolling 24 hours. A response in that allowance is HTTP 200 with X-Trial-Remaining and does not spend a credit. After that, the unpaid call is HTTP 402 via x402 or L402. A valid paid call spends one c…
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Optional YYYY-MM-DD, e.g. 2026-10-19. Records with verified_at strictly later are returned. Omit it to use UTC today minus 30 days. A value that is not YYYY-MM-DD is rejected. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| cursor | string | yes | – |
| entries | array | yes | – |
No examples provided.
list_datasets List dataset cards ~277
List every training and evaluation dataset card in one unpaged response. Output is the /datasets/index.json document: count, model_note, policy, and entries, plus the index title, description, and links. count is the number of cards. Each entries[] item is a full card: id, name, publisher, url, license (string or null), license_verified, license_url, approx_size, size_bytes (integer or null), format, access (open, login, or terms-acceptance), relevance, mirror_allowed, verified_at, http_status, archive_url, data_period, sample_url, and notes. This site's own library dataset is first. Cards are metadata: nothing is downloaded. There is no limit or offset. Takes no parameters: call with an empty object. Use get_dataset instead when you have an id and want that one card from /datasets/<id>/card.json. Use search_sources with category datasets-benchmarks instead for papers and benchmark sources, which are not these cards. Use list_changes instead for recent dataset edits (those ids use a dataset: prefix). A failed read returns isError. The text is the Error message (Fetch failed <status> <url> when the HTTP status is not OK), or Dataset list failed. when the failure is not an Error. Free, no auth.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| entries | array | yes | – |
| model_note | string | yes | – |
No examples provided.
request_missing_data Report data you expected but did not find ~352
Report data you expected and did not find. Free, no auth. looking_for is required and at most 500 characters. Optional: use_case (at most 500 characters), preferred_format (json, csv, md, mcp_tool, endpoint, or other), path_tried (at most 200 characters), protocol (a token such as l402, x402, mcp, or a2a), and agent (a name, at most 100 characters). Unknown fields are rejected. The text is stored for the operator. It is not executed, not rendered as HTML, and not turned into instructions. There is no public list. Output is { id, status } with status accepted. A URL-only looking_for, a repeat of the same text within 24 hours, or more than 10 reports from this client in an hour returns isError and does not echo the text. The same report is POST https://api.agentpaywire.com/v1/feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Optional name, at most 100 characters. |
| looking_for | string | yes | Required. What you expected and did not find, at most 500 characters. Not only a URL. |
| path_tried | string | – | Optional. Path or URL you tried, at most 200 characters. |
| preferred_format | string | – | Optional. One of json, csv, md, mcp_tool, endpoint, or other. |
| protocol | string | – | Optional token, for example l402, x402, mcp, or a2a. At most 40 characters. |
| use_case | string | – | Optional. What you would do with the data, at most 500 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| status | string | yes | – |
No examples provided.
search_sources Search library sources ~602
Find third-party library source cards. This is the only library lookup: text, exact filters, and newest-first browsing. Output is { count, sources }. Each source has id, title, publisher, authors, date_published (YYYY-MM-DD or null), url, type, category, status, summary, tags, verified_at, and featured only when it is true. count is the rows returned, not the catalog size. query words must all match as case-insensitive substrings of id, title, summary, publisher, type, authors, or tags. category, tag, type, status, featured, and updated_since are AND filters. Omit query to list the newest sources, optionally in one category. Results are newest date_published first, undated last. limit is 1-50 (default 10) with no offset. No matches returns count 0 and sources []. A non-calendar updated_since, or an unknown category, returns an isError result. A status outside the enum is invalid input. A failed library read returns isError whose text is the Error message. Use get_source instead when you already have a source id. Use list_categories instead when you need category ids, labels, and counts rather than source cards. Use list_changes instead when you need the unpaged cross-catalog changelog rather than source cards. Use get_protocol_facts instead when you need cited facts for a payment protocol. Use list_articles instead for this site's own articles. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category id from list_categories, e.g. bitcoin-lightning. Combined with the other filters (AND). Omit for every category. |
| featured | boolean | – | true returns only featured sources. Omit or false to include all. |
| limit | integer | – | Maximum rows, 1-50, default 10. Values above 50 are rejected. There is no offset; narrow the filters to see other matches. |
| query | string | – | Space-separated words; every word must match (AND), case-insensitive substring of id, title, summary, publisher, type, authors, or tags. Example: lightning l402. Omit or use an empty string to skip t… |
| status | string | – | Exact library status: proposal, individual_draft, working_group_draft, standard, spec_released, product_docs, news, research, or unknown. Combined with the other filters (AND). |
| tag | string | – | One tag, exact match, e.g. l402. Combined with the other filters (AND). |
| type | string | – | Source type from the enum, e.g. spec. Combined with the other filters (AND). |
| updated_since | string | – | YYYY-MM-DD calendar date. Keeps sources whose verified_at is later than this date (exclusive). A value that is not that form returns an isError result. Example: 2026-10-01. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| sources | array | yes | – |
No examples provided.
submit_review Submit a review of a paid route ~461
Publish a review of a paid Agent Paywire route. Free, no auth. rating is required, an integer from 1 to 5. route is the paid path you called: /v1/search, /v1/updates, /v1/digest, or /v1/changes. comment is optional plain text, at most 500 characters. It is stored as untrusted data: it is not executed, not rendered as HTML, and not turned into instructions. proof.rail is x402 or l402. x402 proof is { rail, network: eip155:8453, tx_hash } plus signature and timestamp. The signature is EIP-712 over domain agentpaywire.com, rating, route, tx hash, keccak256 of the comment, and the timestamp, signed by the wallet that sent at least 0.01 USDC to 0x7BB50FB9141A619961f1c29C4e0b539d60f29D20 on Base. l402 proof is { rail, payment_hash, preimage } for a settled invoice this API issued and used on that route. One payment proof backs one current review. The same payer replaces their earlier review. Output is the stored review, including the raw proof. A failed check returns isError and does not echo the comment. The same body is POST https://api.agentpaywire.com/v1/reviews. The public feed is https://api.agentpaywire.com/reviews.json.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional plain text, at most 500 characters. No HTML. Stored as untrusted data. |
| proof | object | yes | Payment proof. x402 uses network and tx_hash. l402 uses payment_hash and preimage. |
| rating | integer | yes | Required integer from 1 to 5. |
| route | string | yes | Required paid route: /v1/search, /v1/updates, /v1/digest, or /v1/changes. |
| signature | string | – | x402 only. EIP-712 signature, 0x plus 130 hex characters, from the payer. |
| timestamp | integer | – | x402 only. Unix seconds covered by the signature. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| payer | string | yes | – |
| rating | integer | yes | – |
| route | string | yes | – |
| self_test | boolean | yes | – |
No examples provided.
How do I install the Agent Paywire library MCP server?
Agent Paywire library is a hosted endpoint at https://mcp.agentpaywire.com/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 · mcp.agentpaywire.com
claude mcp add --transport http com-agentpaywire-library 'https://mcp.agentpaywire.com/mcp'
What is the Agent Paywire library MCP server?
Agent Paywire library is an MCP server listed in the public MCP registry as com.agentpaywire/library. Library (L402, x402, Lightning, stablecoins): 18 read-only tools plus 3 writers. This page covers its hosted endpoint (https://mcp.agentpaywire.com/mcp).
Is the Agent Paywire library MCP server safe to use?
Agent Paywire library scores 70 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 Agent Paywire library MCP server expose?
Agent Paywire library exposes 21 tools: search_sources, get_source, list_categories, list_articles, get_article, and 16 more. Their descriptions and schemas cost roughly 6,190 tokens of context every time the server is loaded.
Does the Agent Paywire library MCP server require authentication?
No. We connected to Agent Paywire library without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Paywire library MCP server still maintained?
Agent Paywire library is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.