paycrow

by io.github.michu5696

safe_pay

The smart way to pay an agent. Checks their trust score first, then auto-configures escrow protection based on risk.

Flow: Check trust → Set protection level → Create escrow → Call API → Verify → Auto-release or auto-dispute.

Protection levels (automatic):

High trust agent → 15min timelock, proceed normally
Moderate trust → 60min timelock, payment capped at $25
Low trust → 4hr timelock, payment capped at $5
Unknown/caution → BLOCKED — will not send funds

This is the recommended tool for paying any agent. If you need manual control, use x402_protected_call instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	The API endpoint URL to call
`body`	No	Request body (for POST/PUT)
`method`	No	HTTP method (default: GET)	GET
`headers`	No	HTTP headers to include
`amount_usdc`	Yes	Amount to pay in USDC
`seller_address`	Yes	Ethereum address of the agent you're paying

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedMar 14, 2026
- changedInput schema / properties / headers / description
```
Previous value: -"HTTP headers"New value: +"HTTP headers to include"
```
- changedInput schema / properties / method / description
```
Previous value: -"HTTP method"New value: +"HTTP method (default: GET)"
```
AddedMar 13, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full weight. It discloses the risk-based protection levels, payment caps, blocked unknown agents, and the flow including auto-release/dispute. However, it doesn't detail what happens after verification or error handling, so some gaps remain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear flow, bullet points for protection levels, and no redundant text. Every sentence adds value, and it's front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the key behavioral aspects necessary for an agent to decide and invoke the tool, including trust check, protection levels, and recommendation vs alternatives. Lacks return/output details, but since there is no output schema, a brief note on response format would elevate completeness. Still, it is solid.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains each parameter. The description adds context about trust-based caps but doesn't elaborate on individual parameters like body or headers beyond what schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as a payment method for agents that includes trust checking and automatic escrow protection. It distinguishes itself from sibling tools like x402_protected_call by describing its automated risk-based flow and being the recommended payment tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage guidance is given: 'This is the recommended tool for paying any agent' and alternative 'use x402_protected_call instead' when manual control is needed. The flow description also clarifies when it applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All paycrow tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between trust_gate, trust_onchain_quick, and trust_score_query, which all relate to checking agent trustworthiness. While each has a slightly different focus (quick check vs. full breakdown vs. decision recommendation), an agent might struggle to choose the right one in some scenarios. The escrow and payment tools are clearly differentiated.

Naming Consistency4/5

The naming is mostly consistent with a verb_noun pattern (e.g., escrow_create, escrow_release, rate_service), but there are deviations like safe_pay (adjective_verb) and x402_protected_call (alphanumeric prefix). These outliers break the pattern slightly, though the majority of tools follow a clear convention.

Tool Count5/5

With 10 tools, the count is well-scoped for the server's purpose of handling escrow, payments, and trust management. Each tool appears to serve a specific function in the workflow, from creating escrows to checking trust scores, without feeling excessive or insufficient for the domain.

Completeness5/5

The tool set provides comprehensive coverage for the escrow and payment domain, including creation, dispute, release, status checks, rating, and trust assessment. It supports both automated (safe_pay) and manual (x402_protected_call) workflows, with no obvious gaps in the lifecycle or functionality needed for secure transactions.

Resources

Need Help?