NameWhisper MCP Server

get_agent_reputation

Check if an ENS name or wallet is a registered AI agent and retrieve its on-chain reputation scores, reviews, and validations.

Instructions

Check if an ENS name or wallet is a registered AI agent. Returns ENSIP-25 agent-registration verification (text record bindings between ENS names and on-chain agent registries), AI metadata from text records, and ERC-8004 reputation data when available.

ENSIP-25 verification is live: reads agent-registration text records from the name's resolver to confirm the ENS name ↔ registry binding.

ERC-8004 reputation queries (scores, reviews, validations) use the live mainnet contracts deployed January 29, 2026.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nameOrWallet": "<nameOrWallet>"
    },
    "name": "get_agent_reputation"
  }
}

Input Schema

Name	Required	Description	Default
`nameOrWallet`	Yes	ENS name (e.g. "agent.eth") or wallet address (0x...) to look up

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and provides useful behavioral details: it explains the ENSIP-25 verification mechanism (reads text records from the resolver) and notes the live mainnet contract deployment date for ERC-8004. It does not explicitly state it is read-only, but 'check' and 'returns' imply a non-mutating operation.

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

Conciseness4/5

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

The description is well-structured and front-loaded with the core purpose in the first sentence. It contains some redundancy in the separate paragraphs for ENSIP-25 and ERC-8004, but each sentence adds useful detail without being excessively verbose.

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

Completeness5/5

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

Given there is no output schema, the description adequately enumerates all return types (verification, metadata, reputation) and provides technical context (live contracts, resolver reading). For a tool with one parameter and no output schema, this is fully sufficient for correct invocation.

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?

The schema already fully describes the single parameter (nameOrWallet) with an example, and schema coverage is 100%. The description adds no additional parameter-specific meaning, so the baseline score of 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 states the tool's purpose with a specific verb and resource: 'Check if an ENS name or wallet is a registered AI agent.' It enumerates the exact data returned (ENSIP-25 verification, AI metadata, ERC-8004 reputation), which distinguishes it from sibling tools like search_agent_directory or get_valuation.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool (e.g., to verify agent registration and fetch reputation). However, it does not explicitly mention alternatives or when not to use it, so it stops short of a 5.

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