Agentry — The Trust Layer For The Agent Economy
Register agents with identity, reputation, escrow, observability, and Lightning payments when building multi-agent or marketplace-style products.
Overview
Agentry is a MCP server for the Build phase that provides an agent registry with Nostr identity, reputation, escrow, observability, and Lightning payments.
What is this MCP server?
- Agent registry with Nostr-based identity and reputation signals
- Escrow and Lightning payment hooks for paid agent interactions
- Observability surface for agent economy operations
- Hosted streamable-http MCP at https://api.agentry.com/mcp
- Version 0.4.0 with website agentry.com and GitHub agentry-mcp source
- Remote MCP URL: https://api.agentry.com/mcp (streamable-http)
- Server version 0.4.0 per registry metadata
What problem does it solve?
Builders shipping agent marketplaces lack a ready-made trust, identity, and payment layer they can invoke from coding agents.
Who is it for?
Indie hackers building agent directories, paid agent APIs, or trust-scored automation networks.
Skip if: Simple single-agent apps with no registry, payments, or cross-agent trust requirements.
What do I get? / Deliverables
You can wire registry, reputation, and Lightning-aware flows into prototypes faster while the agent calls Agentry over MCP.
- Agent registry lookups and registration flows in generated integration code
- Hooks for reputation, escrow, and payment-aware agent interactions
- Observability-oriented agent economy scaffolding aligned with Agentry APIs
Recommended MCP Servers
Journey fit
Trust and registry infrastructure for agents belongs in Build while you shape agent-tooling and agent economy features. Agent-tooling is the canonical shelf for MCP servers that help you discover, register, and govern agents—not day-two error paging.
How it compares
Agent-economy registry MCP—not a code-review skill or generic cloud deploy integration.
Common Questions / FAQ
Who is Agentry for?
Solo builders and small teams creating agent marketplaces, paid agent services, or federated agent networks who need registry and trust primitives.
When should I use Agentry?
Use it while designing agent-tooling features that require identity, reputation, escrow, observability, or Lightning payments.
How do I add Agentry to my agent?
Add the streamable-http remote https://api.agentry.com/mcp to your MCP client configuration per Agentry docs.