resolve_agent_identity
2 registry entries were observed exposing a tool named resolve_agent_identity — none of them flagged as a privileged capability.
Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 11,290 of 35,861 scannable entries (31%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.
- v0.7.0↓ 280/wk
MCP server for capacity-delivery attestations: after an x402 payment for compute capacity (GPU-hours, storage, API credits, bandwidth), the paying agent leaves a signed, factual claim of what was actually delivered, so other agents can check a seller's de
ClaudeCursorCopilotGeminimcpmodel-context-protocolx402agent-to-agentagent-commercecapacity-trade - v0.6.0↓ 400/wk
Should this payment go to this address? MCP server for pre-settlement payment compliance: screen a payee address for OFAC sanctions, mixers, scam and hack lists and on-chain risk across 7 EVM chains, Tron and Solana — with click-through evidence, not a bl
ClaudeCursorCopilotChatGPTGeminimcpmodel-context-protocolamlcompliancesanctionsofac
All indexed toolsSearch the registry for resolve_agent_identity