A
licenseNot graded
qualityC
maintenanceMCP server for verifying agent payment integrity on x402, providing tools to check payTo mismatches, market stats, and lookup endpoints.
1
MIT
PayCheck
by toolweather
Related Servers
Alternatives to PayCheck
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that preflights endpoints before agent payments, returning a trust verdict with proceed/caution/avoid recommendation.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for agent-native and human-accessible payments using MPP and x402 protocols, enabling payment flows from CLI or agent hosts.2 npmMIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI agents to safely interact with a double-entry payments ledger, enforcing idempotency, policy-based access control, and human-in-the-loop approval for high-value actions.-
acuris-agent-guardofficial
AlicenseNot gradedqualityCmaintenanceMCP server that verifies storefront merchants before AI agents make payments, checking if the merchant is a real legal entity bound to the domain, and returning a PROCEED, ABORT, or REVIEW decision to prevent payment to clones or fraudulent stores.MIT- AlicenseNot gradedqualityBmaintenanceA remote MCP server that lets any AI agent accept payments in Nigeria via cards, bank transfer, USSD, and mobile money through Paystack.MIT
TDQS
A4.7/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a sharply distinct purpose: check_merchant scores a payee, get_quota reads remaining allowance, and get_api_key mints a credential. The descriptions go further by explicitly stating what each tool must NOT be used for, eliminating boundary confusion.
Naming Consistency5/5
All three tools follow a clean verb_noun snake_case pattern (check_merchant, get_quota, get_api_key). The convention is uniform with no camelCase or stylistic drift.
Tool Count4/5
Three tools is at the low end but fits the narrow scope of a trust-scoring service: score a target, check quota, obtain a key. No tool is redundant, though a batch-check or reporting tool could plausibly earn a place.
Completeness4/5
The core lifecycle (authenticate, check quota, score a merchant) is fully covered with clear returns and error semantics. Minor gaps remain, such as no batch-scoring or dispute/appeal path, but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues