No user-submitted related servers found.
Scored across 15 tools
Descriptions work hard to separate tools (e.g. 'Answers a different question from address screening'), but real overlaps remain: payment_decision and compliance_decision both return allow|review|decline and differ mainly by paid/free settlement, while screen_address, batch_screen, deep_trace, evidence_bundle and compliance_decision all touch AML screening of addresses. The three control-baseline tools (baseline_controls, counterparty_control_baseline, attest_control_baseline) are also easy to confuse at a glance.
All names use snake_case, which is good, but the grammatical pattern is mixed: verb_noun tools (screen_address, verify_payment_requirements, attest_control_baseline, resolve_agent_identity) sit alongside noun-phrase tools (baseline_controls, payment_decision, compliance_decision, evidence_bundle, recent_flagged) and an awkward noun_verb (payee_decide). Readable in practice but not a predictable single convention.
15 tools is at the upper edge of the comfortable range but is justified by the genuinely broad domain: address/endpoint/batch screening, tracing, decisioning, agent identity, control attestation, calldata decoding, and requirement verification. Each tool maps to a distinct operational step rather than padding.
The surface covers the full payment-safety lifecycle: pre-payment screening, endpoint screening, tracing, decisioning, identity resolution, control baselines (read/file/counterparty), calldata intent, signed-requirement verification, and signed evidence. Minor gaps exist (e.g. no explicit tool for retrieving a named agent's full published mandate or a general list-pagination beyond recent_flagged), but agents can work around them.