Skip to content
Back to the index

ens

pipeworx.ioInfrastructure

PulseGate's liveness check found it on 3 Oct 2026; it has been in the index since 22 Aug 2026. How this is checked

ENS MCP Server exposes JSON-RPC tools for resolving Ethereum Name Service names to wallet addresses and profile records, and reverse-resolving addresses to primary ENS names. It is designed for AI agents and developer applications through an HTTP MCP endpoint.

Inferred · not functionally tested

WebAPICloud-managed
ens preview
Visit pipeworx.io

Overview

6 features

Purpose: Resolving ENS names and Ethereum addresses into readable identities and profile information.

Inferred · not functionally tested

Audience: AI agent and application developers

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

ens is an API design, testing & docs project. Inferred · not functionally tested: It focuses on resolving ENS names and Ethereum addresses into readable identities and profile information. Inferred · not functionally tested: It is built as a B2B product for AI agent and application developers. Basis unknown · not verified: It ships for the web and API.

Behind ens is Pipeworx. Inferred · not functionally tested: Among its 6 catalogued features are ENS name resolution, reverse address lookup, and ethereum address lookup. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • ENS name resolution
  • Reverse address lookup
  • Ethereum address lookup
  • Profile records
  • Social profile lookup
  • JSON-RPC endpoint

Topics: Inferred · not functionally tested

Tags
ens-resolutionethereum-identitymcp-serverweb3-data

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCP
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed22 Aug · 00:57 UTC
    Ens seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about ens

What is ens?
Inferred · not functionally tested: Ens focuses on resolving ENS names and Ethereum addresses into readable identities and profile information. It is catalogued under API design, testing & docs on PulseGate.
Who should use ens?
Inferred · not functionally tested: ens is a B2B product built for AI agent and application developers.
What platforms does ens run on?
Basis unknown · not verified: ens runs on the web and API.
Is ens still active?
PulseGate's liveness check found it on 3 Oct 2026.
Who develops ens?
ens is developed by Pipeworx.
Does ens have an API or integrations?
Inferred · not functionally tested: Yes — ens exposes an MCP server.

Similar projects

Closest matches by what these projects do