プロトタイプ · プレビュー版：公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。レビューとアカウント機能は今後のステップで始まります。
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説
初心者モード オフ
配色システムに合わせるライトダーク
言語ไทยEnglish中文日本語한국어EspañolDeutsch
☰ メニュー設定
初心者モード オフ
配色システムに合わせるライトダーク
言語ไทยEnglish中文日本語한국어EspañolDeutsch

AgentResolver — Agent Commerce Health Monitoring

作者：waxswayバージョン 0.2.4i★ –iクラウドで動く
レジストリ名io.github.waxsway/agentresolver

インストール

概要

作者による説明（英語の原文）

Free API/MCP/x402 health checks plus $19 hourly managed monitoring for agent services.

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

  • 接続方法: クラウドで動く
  • トランスポート: Streamable HTTP
  • カテゴリ: クリニック・健康

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

必要なもの

どのアプリを使っていますか？

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

ウェブ、デスクトップ、モバイルのClaudeで使えます：

  1. Settings → Connectors を開く
  2. Add custom connector を押す
  3. 下のアドレスを貼り付けて Add を押す
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Add2https://…3
https://agentresolver.vercel.app/mcp

ターミナルでこれを実行します

claude mcp add --transport http agentresolver https://agentresolver.vercel.app/mcp

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "agentresolver": {
      "url": "https://agentresolver.vercel.app/mcp"
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "agentresolver": {
      "type": "http",
      "url": "https://agentresolver.vercel.app/mcp"
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

ChatGPTがつなげるのは、インターネット上のサーバーだけです：

  1. ウェブ版のChatGPTを開き → Settings → Connectors (Apps)
  2. Create または Add を押す（プランによっては、先に Advanced で Developer mode をオンにする必要があります）
  3. 下のアドレスを貼り付け、名前を付けて保存する
  4. サインインを求められたら、作者のサービスにサインインする
SettingsConnectors1+ Create2https://…3
https://agentresolver.vercel.app/mcp

メニューの名前は、プランや時期によって少し違うことがあります。

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月8日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

  • sponsorship_info

    Free read-only information for tool/API/MCP providers about AgentResolver's explicitly labeled sponsorship pilot. Organic ranking remains independent; applying creates no purchase or financial commitment.

  • resolve

    Free exploratory discovery. Use only when browsing possible tools/APIs/MCP services without needing a trustworthy execution choice yet. For an actual missing capability, prefer procure so required evidence fails closed and unresolved candidates can escalate to verification.

  • provider_bootstrap

    Free zero-state provider onboarding. Reads the fixed AgentResolver well-known manifest on one HTTPS origin, live-verifies selected same-origin x402 payment identities, returns an immediate providerOrigins procurement seed, and prepares caller-owned durable 402 Index registration

  • procure

    CALL THIS when the agent's installed tools do not clearly satisfy the current task. Free open-world procurement across APIs, MCP, x402, L402 and MPP. Required compatibility evidence fails closed: AgentResolver returns no selected provider rather than guessing. When supported unkn

  • abi_encode

    Paid $0.005 USDC on Base or Solana exact Ethereum ABI encoding from Solidity typed JSON values to calldata-ready hex.

  • abi_decode

    Paid $0.005 USDC on Base or Solana exact Ethereum ABI decoding into JSON-safe typed values.

  • eip712_hash

    Paid $0.005 USDC on Base or Solana exact EIP-712 typed-data digest for signing and verification workflows.

  • ens_namehash

    Paid $0.01 USDC on Base or Solana ENSIP-15 normalization, exact ENS namehash and label hashes.

  • evm_address_checksum

    Paid $0.003 USDC on Base or Solana exact EIP-55 address validation and checksum normalization.

  • keccak256

    Paid $0.004 USDC on Base or Solana exact Ethereum keccak256 digest for UTF-8 text or hex bytes.

  • solidity_selector

    Paid $0.01 USDC on Base or Solana exact 4-byte Solidity selector and full keccak256 signature hash.

  • evm_units

    Paid $0.005 USDC on Base or Solana exact decimal/base-unit conversion with arbitrary token decimals.

  • x402_ping

    Paid $0.001 USDC on Base or Solana no-body settlement canary for funded agents. Returns a timestamped pong only after successful x402 payment to verify wallet, facilitator, payment, and delivery end-to-end.

  • sha256

    Paid $0.001 USDC on Base or Solana SHA-256 digest of bounded UTF-8 text.

  • sha512

    Paid $0.001 USDC on Base or Solana SHA-512 digest of bounded UTF-8 text.

  • hmac_sha256

    Paid $0.001 USDC on Base or Solana HMAC-SHA256 hex digest.

  • base64_encode

    Paid $0.001 USDC on Base or Solana UTF-8 to Base64 encoding.

  • base64_decode

    Paid $0.001 USDC on Base or Solana Base64 to UTF-8 decoding.

  • jwt_decode

    Paid $0.001 USDC on Base or Solana non-verifying JWT header/payload decode.

  • json_normalize

    Paid $0.001 USDC on Base or Solana canonical JSON normalization plus SHA-256 digest.

  • json_schema_validate

    Paid $0.001 USDC on Base or Solana deterministic JSON Schema subset validation.

  • url_parse

    Paid $0.001 USDC on Base or Solana absolute URL parser.

  • uuid_v4

    Paid $0.001 USDC on Base or Solana UUID v4 generation, up to 20 IDs.

  • slugify

    Paid $0.001 USDC on Base or Solana deterministic slug generation.

  • hash_encode

    Paid $0.001 USDC on Base or Solana deterministic SHA-256, SHA-512, HMAC-SHA256, Base64 encode/decode, or non-verifying JWT decode. x402-aware MCP clients can authorize and settle inside this tool call.

  • payment_guard

    Paid $0.001 USDC fail-closed payment authorization preflight. Use immediately before an autonomous agent signs a target x402 payment. Returns eligible/blocked, exact observed payment terms, reason codes, evidence receipt and stable fingerprints. The caller retains sole spending a

  • x402_payment_preflight

    Paid $0.001 USDC on Base or Solana transaction-path gate for autonomous buyers. Returns eligible/blocked, exact target payment terms, fail-closed reason codes and verifiable evidence before caller authorization. AgentResolver never requests a private key, signs the target payment

  • http_inspect

    Paid $0.001 USDC on Base or Solana verify-before-pay endpoint safety check: payTo verification, quote price, network, asset, resource binding and x402 challenge compliance before an agent authorizes spend. POST probes require explicit caller opt-in because an unprotected endpoint

  • tool_contract

    Paid $0.005 USDC on Base or Solana deterministic JSON-schema compatibility check between one tool output and the next tool input. Returns exact incompatibility reasons and conservative normalized mappings. x402-aware MCP clients can authorize and settle inside this tool call.

  • openapi_select

    Paid $0.005 USDC on Base or Solana selection of the best operation from one public JSON OpenAPI spec for a stated goal. Returns a compact execution-ready contract. x402-aware MCP clients can authorize and settle inside this tool call.

  • mcp_preflight

    Paid $0.001 USDC on Base or Solana live MCP endpoint preflight for reachability, compatibility, latency, server metadata and tool inventory. x402-aware MCP clients can authorize and settle inside this tool call.

  • agent_readiness

    Paid $0.005 USDC on Base or Solana audit of a public website for agent discoverability and machine-readable integration signals. x402-aware MCP clients can authorize and settle inside this tool call.

  • agent_distribution_pack

    Paid $5 USDC seller-side agent distribution pack for API/MCP discoverability: live discovery audit, ready-to-commit agent-readable artifacts, and a prioritized API/MCP distribution sequence.

  • provider_launch_check

    Paid $0.05 USDC seller-side agent-distribution entry check: verify provider readiness and the live x402 contract, then use the $5 Distribution Pack when discoverability artifacts or launch fixes are needed.

  • verified_resolve

    PAID $0.02 USDC verification step. Use after procure returns no proven selection / eligible_with_unknowns, or immediately before trusting an unfamiliar external candidate when live evidence is required. Re-checks supported endpoint, MCP, x402 and contract evidence and returns a f

  • batch_verified_resolve

    Paid $0.05 USDC on Base or Solana batch live verification for 2–4 capability decisions using unpaid MCP and x402/HTTP evidence. x402-aware MCP clients can authorize and settle inside this tool call.

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月9日にチェック

  • ✓ 合格

    作者とリポジトリが一致

    レジストリ名は、リポジトリを所有するGitHubアカウント waxsway で確認済みです

  • … 未チェック

    今もメンテナンスされている

    このリポジトリはまだGitHubから読み取っていません

  • … 未チェック

    ライセンスがある

    このリポジトリはまだGitHubから読み取っていません

  • ✓ 合格

    エンドポイントが応答する

    875ミリ秒で応答（HTTP 200）

  • – 対象外

    OAuthでサインイン

    サインイン不要

  • ✓ 合格

    ツールの説明に隠れた指示がない

    36件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

クリニック・健康のほかのサーバーとの比較i

  • このカテゴリのほかの1035件のうち0%よりスターが多い
  • このカテゴリのほかの1035件のうち43%より最近レジストリに公開
  • 基本チェックの結果が、このカテゴリのほかの1035件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

AgentResolver — Agent Commerce Health Monitoringは安全ですか？

当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか？

レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。

パソコンで動きますか、それともクラウドですか？

作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。

今もメンテナンスされていますか？

GitHubリポジトリの最終更新は–、最新バージョン（0.2.4）がレジストリに届いたのは42 日前です。

どのアプリで使えますか？

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ（開発者モードのChatGPTなど）でも使えます。

代わりに使えるものは？

同じカテゴリには：Mirobody, FHIR MCP Server, Google Health MCP

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：↓ 週あたりのダウンロードi★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

作者：thetahealth成長中↓ 290/週★ 1408一昨日更新

パソコンで動く✓ thetahealth.ai
インストール

FHIR MCP Server

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

作者：wso2成長中↓ 823/週★ 13711 日前更新

パソコンで動く
インストール

Google Health MCP

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

作者：davidmosiah成長中↓ 1024/週★ 794 か月前更新

パソコンで動く
インストール

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

AgentResolver

Continuous API, MCP, and x402 compatibility monitoring for services used by AI agents.

AgentResolver answers a production question ordinary uptime monitors miss: can an AI agent still discover, call, and pay this service right now?

Production: https://agentresolver.vercel.app Free browser check: https://agentresolver.vercel.app/monitor

Agent Commerce Health monitoring

Start with the free public-service snapshot at GET or POST /api/service-monitor. It checks machine-facing discovery and can optionally run a real MCP initialize + tools/list exchange and a GET-safe x402 payment-contract inspection for same-origin public endpoints.

When an operator wants AgentResolver to own the schedule, POST /api/managed-monitor-30d is $19 USDC for 30 days of recurring monitoring that targets an hourly cadence with a durable public status record. Managed monitoring stores public target URLs and health snapshots only; it does not store wallet keys, API credentials, or customer contact information.

x402 Reliability Router

Existing x402 resource servers can route their standard facilitator traffic through AgentResolver without changing the merchant payTo address:

import { HTTPFacilitatorClient } from "@x402/core/server";

const facilitator = new HTTPFacilitatorClient({ url: "https://agentresolver.vercel.app", timeoutMs: 10_000 });

Standard facilitator surface:

GET  /supported

POST /verify POST /settle

Verification is read-only and may use an explicitly configured secondary. Settlement is submitted to exactly one upstream facilitator; ambiguous timeout/5xx outcomes are marked non-retry-safe instead of being blindly failed over. Full integration guide: x402 Reliability Router.

Free recurring monitoring with GitHub Actions

Run the public-service check on your own GitHub schedule. No AgentResolver account, API key, wallet, or secret is required.

name: Agent commerce health

on: workflow_dispatch: schedule:

  • cron: "17 8 * * *"

jobs: health: runs-on: ubuntu-latest steps:

  • uses: waxsway/agentresolver/.github/actions/agent-commerce-health@main with: origin: https://api.example.com

Optional deeper checks:

mcp-endpoint: https://api.example.com/mcp

x402-endpoint: https://api.example.com/paid

The free Action reports current machine-readiness, optional live MCP initialize + tools/list compatibility, and optional GET-safe x402 payment-contract health. The hosted managed monitor is the $19 / 30-day option when you want AgentResolver to own the recurring schedule and durable status.

Full setup: free GitHub monitoring.

Buyer-side Guard

AgentResolver Guard remains the pre-sign safety check for autonomous x402 payments. Before a target wallet signs, Guard reads the live payment challenge, validates the payment contract, and returns a fail-closed decision plus evidence the caller can bind to its own policy.

What Guard checks

Guard performs one bounded HTTPS preflight against the target and verifies the live x402 contract before the caller authorizes spend:

  • endpoint reachability and HTTPS/TLS evidence
  • PAYMENT-REQUIRED structure
  • x402 version and payment scheme
  • quoted USDC amount
  • optional maxPriceUsd ceiling
  • network
  • asset
  • payTo recipient
  • optional expectedPayTo and expectedNetwork assertions
  • resource/payment binding
  • stable evidence fingerprints for change detection

Guard blocks private/reserved network targets, does not follow redirects, uses bounded timeouts, and fails closed when required evidence is missing or mismatched.

Guard never receives the target-payment private key, signs the target payment, authorizes the target spend, or custodies/forwards target funds. The calling runtime keeps spending authority.

Price

Canonical Guard:

POST or GET https://agentresolver.vercel.app/api/x402-payment-preflight

$0.001 USDC per successful Guard check Base or Solana where advertised

The compatibility alias /api/payment-guard uses the same Guard product. A Coinbase-CDP-specific Base route is available at /api/cdp-payment-guard for $0.002 USDC because that rail has a higher observed settlement floor.

The intended transaction path

target request

-> target returns 402 -> AgentResolver Guard -> validate amount / asset / network / payTo / scheme / resource binding -> Guard returns eligible or blocked + evidence -> caller policy decides -> caller-owned wallet may sign the target payment

Guard is evidence for a payment decision, not permission to spend.

Install as a pre-sign hook

The official x402 client exposes onBeforePaymentCreation. Use two x402 clients: one hooked client for the target payment and one hook-free client dedicated to the separate Guard payment. This prevents recursive Guard payments.

The framework-neutral client package now exports the reusable pre-sign hook directly:

import { createAgentResolverX402GuardHook } from "agentresolver-client";

targetClient.onBeforePaymentCreation( createAgentResolverX402GuardHook({ maxTargetPriceUsd: 0.05, guardFetch // separate payment-enabled fetch used only for the Guard fee }) );

Until registry publication, build packages/agentresolver-client directly from this repository. The hook fails closed and binds AgentResolver evidence back to the exact selected scheme, network, asset, amount, payee, x402 version, and resource before the x402 client can proceed to signing.

Three maintained integration guides:

  • x402 core pre-sign Guard
  • Coinbase CDP SDK payment Guard
  • Thirdweb x402 payment Guard
  • Zero-dependency wallet/proxy Guard

Install as an Agent Skill

npx skills add waxsway/agentresolver --skill agentresolver-payment-guard

Direct skill source:

https://agentresolver.vercel.app/.well-known/agent-skills/agentresolver-payment-guard/SKILL.md

The skill tells a wallet-capable agent to run Guard before each unfamiliar or changed autonomous x402 spend.

Example Guard request

Guard supports a target URL plus optional caller assertions:

{

"url": "https://target.example/api", "method": "GET", "maxPriceUsd": 1.00, "expectedPayTo": "0x...", "expectedNetwork": "eip155:8453" }

The unpaid request returns AgentResolver's own x402 challenge. After the caller authorizes and settles the Guard fee, the response contains the observed target-payment terms, reason codes, eligibility decision, and evidence receipt.

What Guard is — and is not

Guard is a transaction-path control for x402 buyers. It is designed to answer a narrow question immediately before signing:

Does the live payment challenge still match the payment contract my agent is willing to authorize?

Guard does not claim that a provider is honest, that a wallet has a particular legal owner, or that future fulfillment is guaranteed. It validates live payment-contract evidence and caller-supplied policy assertions.

Wallet-risk, reputation, AML, and other third-party evidence can be added later through explicit evidence-provider interfaces if real users require them. They are not bundled into Guard by default.

Supporting infrastructure

AgentResolver still exposes supporting infrastructure used by integrations, testing, and open-world fallback workflows. These surfaces are not the primary product:

  • free procure / resolve capability discovery
  • remote MCP control plane: https://agentresolver.vercel.app/mcp/control
  • x402 settlement canaries and compatibility routes
  • machine-readable manifests, OpenAPI, skills, and discovery metadata
  • legacy deterministic utilities retained for compatibility and evidence

New utility endpoints, passive directory submissions, and speculative marketplace-specific builds are not product strategy. Agent Commerce Health monitoring is the primary commercial product; Guard and the reliability router remain supporting buyer-side/payment infrastructure.

Machine-readable surfaces

https://agentresolver.vercel.app/.well-known/x402

https://agentresolver.vercel.app/openapi.json https://agentresolver.vercel.app/llms.txt https://agentresolver.vercel.app/.well-known/agentresolver-trust.json

Security

AgentResolver is non-custodial. Never provide it with wallet private keys or seed phrases.

Please report vulnerabilities privately through this repository's GitHub Security Advisories. The production security contact is also published at:

https://agentresolver.vercel.app/.well-known/security.txt

Local development

npm install

npm run dev

License

MIT

PopNxに聞く