mantle-address-registry-navigator

Resolve and validate Mantle contract and token addresses via mantle_resolveToken and mantle_resolveAddress.

3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill mantle-address-registry-navigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mantle-address-registry-navigator
Source: https://github.com/Pieverse-Eng/purrfect-skills/tree/main/mantle/vendor/mantle-address-registry-navigator
Command: npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill mantle-address-registry-navigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Prevents unsafe onchain interactions by ensuring contract and token addresses are resolved only from verified sources, avoiding guessed or stale addresses and reducing phishing and misrouting risks.

Core Features & Use Cases

  • Tool-first resolution: Prefer mantle_resolveToken for tokens and mantle_resolveAddress for contract keys or aliases, with a validated fallback to a local registry.
  • Strong validation & provenance: Validate format, non-zero address, environment match, active status, supports for intended actions, and require source URL and retrieval timestamps.
  • Fail-closed safety: Refuse to return addresses when verification fails, mark confidence levels for stale or missing provenance, and request clarification for ambiguous DeFi entries.
  • Use Case: Before submitting a swap or lending transaction on Mantle, resolve and validate the router or pool address to ensure it is official and executable.

Quick Start

Ask the navigator to resolve and validate the official Mantle address for the Aave v3 Pool on mainnet before preparing a supply transaction.

Frequently Asked Questions about mantle-address-registry-navigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a Mantle contract address before executing an onchain transaction?

To verify a Mantle contract address before execution, resolve it using tool-first methods like mantle_resolveToken or mantle_validateAddress, which check format, environment match, and active status to ensure safe onchain interactions.

What is the best way to avoid phishing risks when resolving Mantle token addresses?

Avoiding phishing risks when resolving Mantle token addresses requires using verified sources with provenance checks, demanding source URLs and retrieval timestamps, and enforcing fail-closed behavior when verification fails.

Can I resolve DeFi protocol contract roles on Mantle mainnet and sepolia?

Yes, you can resolve DeFi protocol contract roles on Mantle mainnet and sepolia by applying mantle_resolveAddress for contract keys, validating whitelist entries, and requesting clarification for ambiguous entries.

Does Mantle address validation provide a local registry fallback for offline lookups?

Mantle address validation provides a local registry fallback for offline lookups, applying confidence labeling to flag stale or missing provenance data while still preferring tool-first resolution for accuracy.

Why does my Mantle address lookup fail-closed instead of returning a guessed contract address?

Mantle address lookups fail-closed instead of returning guessed addresses to prevent unsafe onchain interactions, actively refusing to output unverified contract addresses and reducing misrouting risks.