原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

AgentResolver — Agent Commerce Health Monitoring

作者:waxsway版本 0.2.4i★ 0i在云端运行
注册名称io.github.waxsway/agentresolver

安装方法

概览

作者提供的说明(英文原文)

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

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 诊所与健康

安装

选择你使用的 AI 应用,然后复制设置。

通过 4/4 项检查 · 你的提问会经过开发者的服务器(agentresolver.vercel.app)

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1+ Add2https://…3Add4
  2. 点击“+ Add” → “Add custom connector”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称AgentResolver — Agent Commerce Health Monitoring
    Remote MCP server URL · 地址https://agentresolver.vercel.app/mcp

    Authentication 保持 Claude 检测到的设置,然后点击 Add

  3. 在聊天中开启

    +ConnectorsAgentResolver — Agent Commerce Health Monitoring

  4. 试一试

    用 AgentResolver — Agent Commerce Health Monitoring 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 AgentResolver — Agent Commerce Health Monitoring,或回答中出现 AgentResolver — Agent Commerce Health Monitoring 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

仅企业版 ChatGPT 可连接

适用于网页版 ChatGPT Business、Enterprise 或 Edu,需由工作区管理员或所有者添加 · 使用 Free、Plus 或 Pro:你的 ChatGPT 方案暂时无法自行连接 MCP

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称AgentResolver — Agent Commerce Health Monitoring
    Connection · 地址https://agentresolver.vercel.app/mcp
  3. 在聊天中选择 AgentResolver — Agent Commerce Health Monitoring

    开启新聊天,输入前先从插件列表中选择 AgentResolver — Agent Commerce Health Monitoring

  4. 试一试

    用 AgentResolver — Agent Commerce Health Monitoring 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 AgentResolver — Agent Commerce Health Monitoring,或回答中出现 AgentResolver — Agent Commerce Health Monitoring 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http agentresolver https://agentresolver.vercel.app/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 AgentResolver — Agent Commerce Health Monitoring 在列表中并显示已连接

  4. 试一试

    用 AgentResolver — Agent Commerce Health Monitoring 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 AgentResolver — Agent Commerce Health Monitoring,或回答中出现 AgentResolver — Agent Commerce Health Monitoring 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 AgentResolver — Agent Commerce Health Monitoring 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 AgentResolver — Agent Commerce Health Monitoring,或回答中出现 AgentResolver — Agent Commerce Health Monitoring 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 AgentResolver — Agent Commerce Health Monitoring 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 AgentResolver — Agent Commerce Health Monitoring,或回答中出现 AgentResolver — Agent Commerce Health Monitoring 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://agentresolver.vercel.app/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 AgentResolver — Agent Commerce Health Monitoring 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

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

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

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

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.2.4
发布到注册中心i
2026年9月27日
代码最后更新i
2026年11月10日
作者
waxsway
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 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月11日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 waxsway 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 875 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 36 个工具描述,未发现针对 AI 的隐藏指令

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

使用 Google 登录后发帖

用户评价

还没有评价

用 Google 登录后写评价

与“诊所与健康”中的其他服务器比较i

  • 星标数多于此分类中其他 1069 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1069 个服务器的 41% 更新
  • 基础检查结果等于或优于此分类中其他 1069 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

AgentResolver — Agent Commerce Health Monitoring 安全吗?

它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.2.4)于44天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于支持远程 MCP 的应用,例如 ChatGPT Business 及以上方案。

有什么可以替代它?

同一分类中有:Medplum MCP, Mirobody, Apple Health

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Medplum MCP

Securely access and manage FHIR healthcare data stored in Medplum.

作者:medplum广泛使用★ 27874个月前更新

在云端运行✓ medplum.com

Mirobody

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

作者:thetahealth正在增长↓ 290/周★ 1442昨天更新

在你的电脑上运行✓ thetahealth.ai

Apple Health

Local-first Apple Health MCP server for questions about your sleep, workouts and heart data.

作者:neiltron正在增长↓ 106/周★ 5752个月前更新

在你的电脑上运行

作者的 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:

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