MCP servers › io.github.xzntexe › yruz-x402

MCP server · registry snapshot 2026-10-28 · last tested 2026-10-28

io.github.xzntexe/yruz-x402

YRUZ x402 tools — the publisher's title

by xzntexe · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Pay-per-call x402 tools: package advisories, EU tenders, Wikidata facts, promo board, web, crypto — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-28version 1.3.1streamable HTTP56 tools

Summary

io.github.xzntexe/yruz-x402 is a remote MCP server listed in the official MCP registry at version 1.3.1, under the namespace of the GitHub account xzntexe. Its linked repository, github.com/xzntexe/yruz-x402, belongs to the same GitHub account. On 2026-10-28 ProtocolProbe connected to it in read-only mode and read its inventory: 56 tools, 0 resources and 0 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Repository: public
Tools: 56
Last tested: 2026-10-28

Tool list size

22,546 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (56 tools). Counted with Anthropic's token counter on 2026-10-28, from the tool list we read on 2026-10-28. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-28 (yruz.one), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.3.1).

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (promo_create_listing). That is our reading of the names; we did not call it. Source: our connection, 2026-10-28.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-28

Mode

read-only (no tool calls)

Latest version

1.3.1, published 2026-10-27 (registry, as of the 2026-10-28 snapshot)

First listed version

2026-10-25 (earliest version still in the registry; older removed versions would be earlier)

Version history

4 versions listed, 2026-10-25 to 2026-10-27; 4 in the 90 days before the 2026-10-28 snapshot.

Most recent 4 versions

1.3.1 · 2026-10-27
1.3.0 · 2026-10-27
1.2.0 · 2026-10-25
1.1.0 · 2026-10-25

(versions still listed in the registry only)

Registry data

snapshot 2026-10-28

Package and repository

checked 2026-10-28

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.3.0 (published 2026-10-27) → 1.3.1 (published 2026-10-27), between the registry lists of 2026-10-27 and 2026-10-28.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-10-27 and on 2026-10-28; release notes from the GitHub Releases API, checked 2026-10-28.

What it is

What does this server offer?

Observed inventory

56tools

0resources

0prompts

None of its 56 tools are described as changing anything. For 56 the reading was uncertain, so no mark is shown.

site_auditon 9 other servers
“Website audit in one call: TLS certificate, security headers, HTTPS redirect, HTTP/2 and HTTP/3, compression, response time, redirects, SEO tags and AI-agent readiness (llms.txt, robots rules for AI …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- urlstringrequired“website URL or domain (required), e.g.”
web_extracton 20 other servers
“Fetch any public web page and return its main content as clean Markdown (navigation, scripts and boilerplate removed) with title, description, language, canonical URL, author, publish date, headings,…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- urlstringrequired“page URL (required), e.g.”
- linksstring“1 to include every link on the page (default 1)”
- max_charsstring“cap on the Markdown length, 1000-200000 (default 60000)”
company_enrichon 4 other servers
“Company enrichment from a domain or email in one call: company name, description, logo, favicon, social profiles (LinkedIn, X, GitHub, Facebook, Instagram, YouTube ...), contact emails and phones pub…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- domainstringrequired“company domain (required), e.g.”
url_safety_checkon 1 other server
“Should an agent open, sign or pay this link?”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- urlstringrequired“link to check (required), e.g.”
domain_intelon 14 other servers
“Domain intelligence in one call: DNS records (A, AAAA, MX, NS, TXT, CAA, SOA), email security (SPF with lookup count, DMARC policy, MTA-STS, TLS-RPT, BIMI, DKIM on common selectors), registration fro…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- domainstringrequired“domain name (required), e.g.”
weather_forecaston 17 other servers
“Weather for any place on Earth: current conditions (temperature, feels-like, wind, humidity, pressure, cloud, precipitation), the next 48 hours hour by hour and a 7-day forecast with highs, lows and …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs
- qstring“place name (required unless lat/lon), e.g.”
- latstring“latitude, -90 to 90”
- lonstring“longitude, -180 to 180”
link_previewon 4 other servers
“Link preview of any URL in one call: title, description, site name, canonical URL, Open Graph and Twitter card fields, preview image, favicon, theme color, oEmbed endpoint and JSON-LD types.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- urlstringrequired“page URL (required)”
broken_linkson 3 other servers
“Find broken links on a web page: fetches the page, collects its links (internal and external) and checks up to 50 of them in parallel, reporting status code, redirect target and response time for eac…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- urlstringrequired“page URL (required)”
- maxstring“links to check, 1-50 (default 30)”
- scopestring“all (default) | internal | external”
x402_endpoint_checkon 1 other server
“Validate any x402 endpoint the way buyer agents see it: calls it unpaid, decodes the 402 challenge (v2 PAYMENT-REQUIRED header and v1 JSON body), checks every offer (scheme, network, asset, amount, p…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- urlstringrequired“endpoint URL (required)”
- methodstring“GET (default) or POST”
uptime_checkon 2 other servers
“Is it up, right now, from the internet: HTTP status, final URL after redirects, DNS, connect, TLS and time-to-first-byte timings, HTTP version, response size, content type, server, TLS certificate da…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- urlstringrequired“URL or domain (required)”
- keywordstring“optional text that must appear in the response”
wallet_balanceon 27 other servers
“USDC and gas balance of any Solana or Base address, read from the chain: USDC amount, SOL or ETH for fees, whether the USDC account exists, and whether the wallet can pay a given x402 price.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- addressstringrequired“Solana (base58) or Base (0x) address (required)”
- amountstring“optional USDC price to test, e.g.”
crypto_priceon 36 other servers
“Live prices in one fast call for up to 25 assets: any coin by CoinGecko id or ticker symbol (btc, eth, sol, usdc...) and any Solana token by mint address.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- idsstringrequired“comma-separated coins or mints (required), e.g.”
- vsstring“quote currency, default usd (eur, gbp, jpy, btc, eth ...)”

Show 44 more tools

crypto_trendingon 8 other servers
“What the crypto market is doing right now: the most searched coins, the top 24h gainers and losers among the 250 largest coins, global market cap and BTC dominance, and the trending Solana tokens of …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
- limitstring“items per list, 1-20 (default 10)”
solana_token_checkon 3 other servers
“Safety check of any Solana token before an agent buys it: name, symbol, supply, decimals, token program and extensions, mint and freeze authority, mutable metadata, top-10 holder concentration, holde…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- mintstringrequired“Solana token mint address (required)”
solana_portfolio
“Every token a Solana wallet holds, valued in USD: SOL and all fungible SPL and Token-2022 balances with symbol, name, amount, price and value, sorted by value, plus the total portfolio value and the …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- addressstringrequired“Solana wallet address (required)”
- min_usdstring“hide tokens worth less than this, default 0”
solana_tx_explainon 1 other server
“Decode any Solana transaction into plain language: type (swap, transfer, NFT sale, mint ...), the program or DEX used, who sent what to whom with token symbols and amounts, SOL balance changes, fee a…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- signaturestringrequired“transaction signature (required)”
network_fees
“What a transaction costs right now: Solana priority fee levels (low to very high, micro-lamports per compute unit) and the USD cost of a typical transfer and swap, plus Base gas price, base fee and t…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
- accountstring“optional Solana program or account to estimate for (default: Jupiter router)”
deps_get_package
“One package from npm, PyPI or Packagist: latest version, description, declared licence, repository, homepage, deprecation or yanked status, version count, first and last publish date, declared depend…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- namestringrequired“package name (required), e.g.”
- ecosystemstring“npm (default), pypi or composer”
deps_get_version_history
“Release history of a package in ecosystem order (node-semver, PEP 440, Composer): every version with publish time, prerelease flag, deprecation or yank with its reason, which one is latest, release c…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
- namestringrequired“package name (required)”
- ecosystemstring“npm (default), pypi or composer”
- limitstring“versions to return, newest first, 1-200 (default 50)”
- prereleasestring“1 to include prereleases (default 0)”
deps_compare_releases
“What changes between two releases of a package, from registry metadata: dependencies added, removed and re-ranged, licence change, deprecation, publish dates and the releases in between, and which OS…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 2 required
- namestringrequired“package name (required)”
- fromstringrequired“current version (required), e.g.”
- tostring“target version (default: latest)”
- ecosystemstring“npm (default), pypi or composer”
deps_check_advisories
“Is this exact package version affected by a published advisory?”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
- namestringrequired“package name (required)”
- versionstringrequired“exact version (required), e.g.”
- ecosystemstring“npm (default), pypi or composer”
deps_batch_check
“OSV advisory check of 2-100 package versions in one call, mixed ecosystems: status per package version, advisory ids with summary, severity and fixed versions.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- packagesstringrequired“list (required): JSON [{"ecosystem":"npm","name":"lodash","version":"4.17.15"}] or text "npm:lodash@4.17.15, pypi:requests@2.19.0"”
- ecosystemstring“default ecosystem for items without one (default npm)”
deps_get_dependency_tree
“Bounded transitive dependency graph of an npm package version: every node with the declared range, the resolved version (highest published version satisfying the range, as a fresh install without a l…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs, 1 required
- namestringrequired“npm package (required), e.g.”
- versionstring“version or range (default latest)”
- depthstring“levels below the package, 1-4 (default 3)”
- max_nodesstring“graph size cap, 10-250 (default 150)”
- optionalstring“1 to follow optionalDependencies (default 0)”
deps_audit_project
“Audit a project in one call: send package-lock.json (v2/v3), package.json, composer.lock, composer.json or requirements.txt.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- manifeststringrequired“file content (required): package-lock.json, package.json, composer.lock, composer.json or requirements.txt; POST JSON body recommended”
- kindstring“optional file type: package-lock, package, composer-lock, composer, requirements (auto-detected)”
- devstring“1 to include dev dependencies (default 0)”
deps_get_advisory
“One advisory from OSV by its id or alias (GHSA-..., CVE-..., PYSEC-..., RUSTSEC-...): summary, details, severity (CVSS vectors), aliases, published and modified dates, withdrawn flag, every affected …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
- idstringrequired“advisory id (required), e.g.”
deps_get_changes
“Everything that changed for a package since a date: releases published, deprecations and yanks among them, the current latest, advisories published or modified for the package, and attribute changes …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- namestringrequired“package name (required)”
- sincestring“date YYYY-MM-DD (default 90 days ago)”
- ecosystemstring“npm (default), pypi or composer”
deps_monitor_check
“One bounded monitoring check of a package: the current fingerprint of its watched attributes (latest version, licence, deprecation, version count, advisories on the latest release), changed true or f…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- namestringrequired“package name (required)”
- ecosystemstring“npm (default), pypi or composer”
- fingerprintstring“fingerprint returned by your previous check (optional)”
tenders_searchon 1 other server
“Search public tenders and procurement notices published in TED (EU Official Journal S, all EU/EEA countries plus EU-funded procurement such as Serbia): keywords, buyer country, CPV code, contracting …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
15 inputs
- qstring“keywords in the notice text, e.g.”
- countrystring“buyer country, ISO code (DE, DEU, RS, SRB ...)”
- cpvstring“CPV code or prefix, 2-8 digits, e.g.”
- buyerstring“contracting authority name contains”
- supplierstring“awarded supplier name contains (award notices)”
- typestring“competition (calls), result (awards), change (amendments), planning (prior information) or all (default)”
- published_fromstring“date YYYY-MM-DD”
- published_tostring“date YYYY-MM-DD”
- deadline_fromstring“date YYYY-MM-DD”
- deadline_tostring“date YYYY-MM-DD”
- value_minstring“estimated procedure value at least (in its own currency)”
- value_maxstring“estimated procedure value at most”
- limitstring“notices per page, 1-50 (default 20)”
- pagestring“page, 1-100 (default 1)”
- langstring“language of titles, 2 letters (default en)”
tenders_get_notice
“One TED notice by its publication number, normalized: notice and form type, lifecycle stage, title and description, buyer with identifiers, CPV codes, procedure type, place of performance, estimated …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- idstringrequired“TED publication number (required), e.g.”
- langstring“language, 2 letters (default en)”
tenders_get_history
“The lifecycle of a procurement procedure from one of its notices: every TED notice of the same procedure in order (prior information, call, corrigenda, award, contract modification), the change event…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- idstringrequired“TED publication number of any notice of the procedure (required)”
- langstring“language, 2 letters (default en)”
tenders_get_deadlines
“Open calls for tenders whose submission deadline falls in the next 1-90 days, soonest first, with the earliest qualifying lot deadline, buyer, CPV, estimated value and links.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
7 inputs
- qstring“keywords in the notice text, e.g.”
- countrystring“buyer country, ISO code (DE, DEU, RS, SRB ...)”
- cpvstring“CPV code or prefix, 2-8 digits, e.g.”
- buyerstring“contracting authority name contains”
- daysstring“window in days, 1-90 (default 14)”
- limitstring“notices, 1-50 (default 20)”
- langstring“language, 2 letters (default en)”
tenders_get_awards
“Published contract award results matching a supplier, buyer, country, CPV or date range: each award with winners, their country and size, award and tender values with currency, decision and contract …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs
- qstring“keywords in the notice text, e.g.”
- countrystring“buyer country, ISO code (DE, DEU, RS, SRB ...)”
- cpvstring“CPV code or prefix, 2-8 digits, e.g.”
- buyerstring“contracting authority name contains”
- supplierstring“winner name contains”
- fromstring“published from YYYY-MM-DD”
- tostring“published to YYYY-MM-DD”
- limitstring“awards, 1-50 (default 25)”
- langstring“language, 2 letters (default en)”
tenders_get_authority
“Procurement profile of a contracting authority from its TED notices: notice counts by type (calls, awards, amendments, prior information), the most recent notices, CPV divisions and procedure types i…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- namestringrequired“authority name or part of it (required), e.g.”
- countrystring“buyer country, ISO code”
- langstring“language, 2 letters (default en)”
tenders_get_supplier_history
“Award history of a supplier from TED result notices that name it as a winner: total award notices, a dated timeline of the most recent awards with buyer, country, CPV and values as published, buyers …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
- namestringrequired“supplier name or part of it (required), e.g.”
- countrystring“buyer country, ISO code”
- fromstring“published from YYYY-MM-DD”
- langstring“language, 2 letters (default en)”
tenders_get_changes
“What happened since a date (up to 92 days back) for your filters: counts and the newest notices of each kind, new calls for tenders, amendments and corrigenda with their change reasons, award results…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
7 inputs
- qstring“keywords in the notice text, e.g.”
- countrystring“buyer country, ISO code (DE, DEU, RS, SRB ...)”
- cpvstring“CPV code or prefix, 2-8 digits, e.g.”
- buyerstring“contracting authority name contains”
- sincestring“date YYYY-MM-DD (default 7 days ago, at most 92 days back)”
- limitstring“notices per kind, 1-25 (default 10)”
- langstring“language, 2 letters (default en)”
tenders_monitor_check
“One bounded monitoring check of a procurement procedure from any of its TED notices: the current fingerprint of its watched state (notices in the procedure, stage, lot deadlines, estimated value, win…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- idstringrequired“TED publication number of a notice of the procedure (required)”
- fingerprintstring“fingerprint returned by your previous check (optional)”
reality_search
“Find entities on Wikidata by name or alias, with an optional type filter (company, organization, place, software, person): id, label, description, types, the matched name, Wikipedia sitelink count as…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
- qstringrequired“name to search (required), e.g.”
- typestring“any (default), company, organization, place, software or person”
- limitstring“results, 1-20 (default 10)”
- langstring“language of labels, 2-3 letters (default en)”
reality_get_entity
“Normalized profile of one entity: label, description, aliases, types, official identifiers (LEI, ticker, VIAF, OpenCorporates, national registers ...), and the core facts for its kind (inception, cou…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
- idstring“Wikidata id (required unless q), e.g.”
- qstring“name instead of id (the top search hit is used and reported)”
- propertiesstring“extra property ids, comma separated, up to 15, e.g.”
- langstring“language of labels, 2-3 letters (default en)”
reality_get_history
“Time-aware history of an entity: the source's revision log (when, which properties, which kind of edit), when the entity was created, and with as_of the facts the source stated at that past date comp…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs, 1 required
- idstringrequired“Wikidata id (required), e.g.”
- as_ofstring“past date YYYY-MM-DD to compare with now”
- propertystring“only edits of this property, e.g.”
- limitstring“revisions, 1-50 (default 25)”
- langstring“language of labels, 2-3 letters (default en)”
reality_compare
“Two entities side by side: for every core property the current values of each and whether they are the same, overlap, differ or exist on one side only; shared identifiers (a sign of a duplicate recor…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
- astringrequired“first entity: Wikidata id or name (required)”
- bstringrequired“second entity: Wikidata id or name (required)”
- langstring“language of labels, 2-3 letters (default en)”
reality_resolve_entity
“Entity resolution for a company or organization: from a name plus optional website domain, country, LEI or type, the candidate Wikidata entities with a transparent score, a confidence band (determini…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs, 1 required
- namestringrequired“entity name (required), e.g.”
- domainstring“official website domain, e.g.”
- countrystring“country, ISO 2-letter code, e.g.”
- leistring“Legal Entity Identifier, 20 characters”
- typestring“company, organization, place, software or person”
reality_get_evidence
“Evidence bundle for an entity: for each requested property (default: its core facts) every statement with rank, qualifiers and all its references (stated in, reference URL, title, publication and ret…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
- idstringrequired“Wikidata id (required)”
- propertiesstring“property ids, comma separated, up to 10 (default: core facts)”
- langstring“language of labels, 2-3 letters (default en)”
reality_get_conflicts
“Source-conflict report for an entity: properties that should hold one current value but hold several (and whether a preferred rank settles it), time series with different values for the same date, de…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- idstringrequired“Wikidata id (required)”
- langstring“language of labels, 2-3 letters (default en)”
reality_monitor_check
“One bounded monitoring check of an entity: the current fingerprint of its core facts (country, headquarters, website, CEO, employees, revenue, population, version ...”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
- idstringrequired“Wikidata id (required), e.g.”
- fingerprintstring“fingerprint returned by your previous check (optional)”
promo_create_listing
“List a link, API, x402 endpoint, MCP server or dataset on the YRUZ x402 Promo Board for exactly 24 hours (directory, leaderboards, machine-readable catalogue).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 2 required
- titlestringrequired“listing title, 3-120 characters (required), alias name”
- urlstringrequired“public http(s) URL to promote, https:// is added when missing (required), aliases link, website; with an agent Bearer token or a profile x-auth-token it defaul…”
- categorystring“one of api, x402, mcp, data, ai, devtools, crypto, saas, open-source, media, other (default other; synonyms such as tools, dataset, mcp-server are mapped)”
- typestring“one of website, api, x402-endpoint, mcp-server, dataset, developer-tool, agent-service, open-source, other (default: guessed from the URL)”
- descriptionstring“up to 300 characters, optional”
- providerstring“display name, up to 80 characters, optional”
promo_renew_listing
“Add one more 24-hour campaign to your Promo Board listing, starting when the current one ends.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- idstringrequired“listing id returned by /api/promo/create, 16 characters (required), aliases listing, listing_id”
- tokenstringrequired“owner_token returned by /api/promo/create, starts with yzp_ (required), alias owner_token”
promo_takeover_top_spot
“Take over the GLOBAL TOP LINK of the YRUZ Promo Board for 24 hours with your live listing.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 2 required
- idstringrequired“listing id returned by /api/promo/create, 16 characters (required), aliases listing, listing_id”
- tokenstringrequired“owner_token returned by /api/promo/create, starts with yzp_ (required), alias owner_token”
get_exampleon 19 other servers
“Instructions for any paid YRUZ tool: its parameters (required and optional), a valid call, the exact price rule, the payment steps and the response shape (field names and types).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- toolstring“tool name from tools/list, e.g.”
promo_search_listings
“Discovery: search the YRUZ Promo Board listings (live by default) with their 24 h campaign, countdown and top-link status.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs
- qstring“text in title, description or host”
- categorystring“category id”
- typestring“resource type”
- statusstring“active (default), expired or all”
- pagestring“page, 1-100”
promo_get_featured
“Discovery: the current GLOBAL TOP LINK of the YRUZ Promo Board and the next takeover minimum.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
promo_get_leaderboard
“Discovery: every Promo Board ranking (most expensive active link, highest takeover, lifetime spend, most renewed, trending, category leaders) with its definition.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
promo_get_listing
“Discovery: one Promo Board listing with its campaigns and takeovers.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- idstringrequired“listing id (required)”
promo_get_pricing
“Discovery: current Promo Board prices (listing, renewal, takeover minimum), rails and refund policy.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
promo_get_campaign_history
“Discovery: Promo Board takeover and campaign history, newest first.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- pagestring“page, 1-100”
yruz_list_services
“Discovery: the DependencyPulse, TenderGraph and RealityGraph tasks with their task ids, prices and billing units, limits, sources, freshness, MCP tool names and the x402 payment rails (v1 and v2, exa…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- productstring“optional product id”
yruz_get_source_status
“Discovery: every public source behind the data products (npm, PyPI, Packagist, OSV, TED, Wikidata) with licence, attribution, coverage and its measured health: last success, last failure and failure …”
Publisher declares: read-only yes · destructive no · idempotent no · open-world no
Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-28.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 100% of 156
Tools with a description: 100% of 56
Typical description length: 643 characters

The tool set

Counted from the listing

Tools: 56
Size of the list: about 19,013 tokens for an agent to load (characters ÷ 4)
Naming: 56 of 56 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 56 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-28 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://yruz.one/mcp/x402

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "yruz-x402": {
      "url": "https://yruz.one/mcp/x402"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "yruz-x402": {
      "type": "http",
      "url": "https://yruz.one/mcp/x402"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"yruz-x402","type":"http","url":"https://yruz.one/mcp/x402"}'

Claude Code

claude mcp add --transport http yruz-x402 https://yruz.one/mcp/x402

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "yruz-x402": {
      "type": "streamableHttp",
      "url": "https://yruz.one/mcp/x402",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "yruz-x402": {
      "httpUrl": "https://yruz.one/mcp/x402"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.yruz-x402]
url = "https://yruz.one/mcp/x402"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "yruz-x402": {
      "url": "https://yruz.one/mcp/x402"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://yruz.one/mcp/x402 --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint yruz.one/mcp/x402	Session opened	matches	our test · 2026-10-28
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-28
Repository github.com/xzntexe/yruz-x402	Opens publicly	matches	api.github.com · 2026-10-28

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.xzntexe
GitHub owner: a personal account (xzntexe)

Repository: github.com/xzntexe/yruz-x402
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-28.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint yruz.one/mcp/x402

2 of 2 comparisons between consecutive reads showed a change (3 reads, 2026-10-26 to 2026-10-28; versions 1.2.0 to 1.3.1).

Last change seen between our reads on 2026-10-27 (version 1.3.0) and 2026-10-28 (version 1.3.1).

Changed (1):

promo_create_listing: input schema

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-10-28 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-28. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.xzntexe/yruz-x402

Answered from the data above

Who publishes io.github.xzntexe/yruz-x402?

The registry ties the namespace io.github.xzntexe to the GitHub account xzntexe; only its owner can publish under it. Its linked repository, github.com/xzntexe/yruz-x402, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.xzntexe/yruz-x402 safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.xzntexe/yruz-x402 need an API key or sign-in?

It opened a session without any credential on 2026-10-28. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.xzntexe/yruz-x402 been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.github.xzntexe/yruz-x402?

In github.com/xzntexe/yruz-x402, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-28

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-28, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,033 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 56 tools, 0 resources, 0 prompts.
3,575 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-28; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

not stated

GitHub detects no source language in this repository (docs-only or empty)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-28

MCP capability

tools

our test · 2026-10-28

Transport

streamable HTTP

registry · 2026-10-28

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-28

Lifecycle status

active

registry · 2026-10-28

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-28

Maintenance

active

api.github.com · 2026-10-28

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.xzntexe/yruz-x402: MCP server record.” Data checked 2026-10-28. https://protocolprobe.com/mcp/servers/io.github.xzntexe/yruz-x402

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.xzntexe/yruz-x402)](https://protocolprobe.com/mcp/servers/io.github.xzntexe/yruz-x402)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology