Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Beschreibung vom Entwickler (englisches Original)
Free API/MCP/x402 health checks plus $19 hourly managed monitoring for agent services.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://agentresolver.vercel.app/mcpFühre das in deinem Terminal aus
claude mcp add --transport http agentresolver https://agentresolver.vercel.app/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"agentresolver": {
"url": "https://agentresolver.vercel.app/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"agentresolver": {
"type": "http",
"url": "https://agentresolver.vercel.app/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://agentresolver.vercel.app/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 8. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
sponsorship_infoFree 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.
resolveFree 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_bootstrapFree 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
procureCALL 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_encodePaid $0.005 USDC on Base or Solana exact Ethereum ABI encoding from Solidity typed JSON values to calldata-ready hex.
abi_decodePaid $0.005 USDC on Base or Solana exact Ethereum ABI decoding into JSON-safe typed values.
eip712_hashPaid $0.005 USDC on Base or Solana exact EIP-712 typed-data digest for signing and verification workflows.
ens_namehashPaid $0.01 USDC on Base or Solana ENSIP-15 normalization, exact ENS namehash and label hashes.
evm_address_checksumPaid $0.003 USDC on Base or Solana exact EIP-55 address validation and checksum normalization.
keccak256Paid $0.004 USDC on Base or Solana exact Ethereum keccak256 digest for UTF-8 text or hex bytes.
solidity_selectorPaid $0.01 USDC on Base or Solana exact 4-byte Solidity selector and full keccak256 signature hash.
evm_unitsPaid $0.005 USDC on Base or Solana exact decimal/base-unit conversion with arbitrary token decimals.
x402_pingPaid $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.
sha256Paid $0.001 USDC on Base or Solana SHA-256 digest of bounded UTF-8 text.
sha512Paid $0.001 USDC on Base or Solana SHA-512 digest of bounded UTF-8 text.
hmac_sha256Paid $0.001 USDC on Base or Solana HMAC-SHA256 hex digest.
base64_encodePaid $0.001 USDC on Base or Solana UTF-8 to Base64 encoding.
base64_decodePaid $0.001 USDC on Base or Solana Base64 to UTF-8 decoding.
jwt_decodePaid $0.001 USDC on Base or Solana non-verifying JWT header/payload decode.
json_normalizePaid $0.001 USDC on Base or Solana canonical JSON normalization plus SHA-256 digest.
json_schema_validatePaid $0.001 USDC on Base or Solana deterministic JSON Schema subset validation.
url_parsePaid $0.001 USDC on Base or Solana absolute URL parser.
uuid_v4Paid $0.001 USDC on Base or Solana UUID v4 generation, up to 20 IDs.
slugifyPaid $0.001 USDC on Base or Solana deterministic slug generation.
hash_encodePaid $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_guardPaid $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_preflightPaid $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_inspectPaid $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_contractPaid $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_selectPaid $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_preflightPaid $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_readinessPaid $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_packPaid $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_checkPaid $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_resolvePAID $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_resolvePaid $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.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 10. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto waxsway bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Antwort in 875 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 36 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.2.4) kam vor 43 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Mirobody, FHIR MCP Server, Google Health MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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
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.
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.
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:
jobs: health: runs-on: ubuntu-latest steps:
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.
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.
Guard performs one bounded HTTPS preflight against the target and verifies the live x402 contract before the caller authorizes spend:
PAYMENT-REQUIRED structuremaxPriceUsd ceilingpayTo recipientexpectedPayTo and expectedNetwork assertionsGuard 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.
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.
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.
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:
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.
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.
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.
AgentResolver still exposes supporting infrastructure used by integrations, testing, and open-world fallback workflows. These surfaces are not the primary product:
procure / resolve capability discoveryhttps://agentresolver.vercel.app/mcp/controlNew 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.
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
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
npm install
npm run dev
MIT