Static analysis findings on call_paid_tool schema (idempotency + unbounded args) — mind if I reference this in a write-up?

Hey, built a static analyzer for OpenAPI/MCP specs (Nexum) and ran it against AiAgentWalletMCP for fun. Found a couple of interesting things in call_paid_tool's schema (nothing broken, more a lack of bounds, no idempotency key on the payment call, and args accepts anything with no shape constraint). Happy to share the full detail if useful.

Separately, I'm sometimes writing about what static spec analysis does and doesn't catch (e.g. it'd never flag how the wallet key is stored, since that's implementation, not spec). If I ever write about that contrast, would you be OK with me mentioning this project as the example? No pressure either way, just checking first.