Namefi
Search, buy, and manage domains, DNS records, orders, and NFSC balance on Namefi.
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноТолько чтение
Что умеет
- GetDnsRecords: Retrieve all DNS records for a specified domain zone. Returns an array of DNS records including A, AAAA, CNAME, MX, TXT, and other record types.
- CreateDnsRecord: Description: Create a new DNS record for a domain. Requires domain ownership. The record will be validated against DNS zone rules before creation. Instructions: 1. MCP tool arguments
- UpdateDnsRecord: Description: Update an existing DNS record by its ID. Requires domain ownership. The updated record will be validated against DNS zone rules. Instructions: 1. MCP tool arguments use a
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
Search, buy, and manage domains, DNS records, orders, and NFSC balance on Namefi.
Список инструментов сервера (49)
Технические названия из tools/list. Нужны только разработчикам.
| getDnsRecords | Retrieve all DNS records for a specified domain zone. Returns an array of DNS records including A, AAAA, CNAME, MX, TXT, and other record types. |
| createDnsRecord | Description: Create a new DNS record for a domain. Requires domain ownership. The record will be validated against DNS zone rules before creation. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="createDnsRecord". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of CreateDnsRecordEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: CreateDnsRecordEnvelope EIP-712 Types: { "CreateDnsRecord": [ { "name": "type", "type": "string" }, { "name": "name", "type": "string" }, { "name": "rdata", "type": "string" }, { "name": "ttl", "type": "uint256" }, { "name": "zoneName", "type": "string" } ], "CreateDnsRecordEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "CreateDnsRecord" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for CreateDnsRecordEnvelope: { "payload": { <tool payload> }, "payloadType": "CreateDnsRecord", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| updateDnsRecord | Description: Update an existing DNS record by its ID. Requires domain ownership. The updated record will be validated against DNS zone rules. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="updateDnsRecord". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of UpdateDnsRecordEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: UpdateDnsRecordEnvelope EIP-712 Types: { "UpdateDnsRecord": [ { "name": "id", "type": "string" }, { "name": "zoneName", "type": "string" }, { "name": "type", "type": "string" }, { "name": "name", "type": "string" }, { "name": "rdata", "type": "string" }, { "name": "ttl", "type": "uint256" } ], "UpdateDnsRecordEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "UpdateDnsRecord" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for UpdateDnsRecordEnvelope: { "payload": { <tool payload> }, "payloadType": "UpdateDnsRecord", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| deleteDnsRecord | Description: Delete a DNS record by its ID. Requires domain ownership. The deletion will be validated to ensure zone integrity. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="deleteDnsRecord". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of RecordSelectEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: RecordSelectEnvelope EIP-712 Types: { "RecordSelect": [ { "name": "id", "type": "string" }, { "name": "zoneName", "type": "string" } ], "RecordSelectEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "RecordSelect" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for RecordSelectEnvelope: { "payload": { <tool payload> }, "payloadType": "RecordSelect", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| batchUpdateDnsRecords | Description: Update multiple DNS records in a single transaction. Requires domain ownership. All records must belong to the same zone and will be validated together. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="batchUpdateDnsRecords". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of UpdateRecordsEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: UpdateRecordsEnvelope EIP-712 Types: { "UpdateZoneRecord": [ { "name": "id", "type": "string" }, { "name": "type", "type": "string" }, { "name": "name", "type": "string" }, { "name": "rdata", "type": "string" }, { "name": "ttl", "type": "uint256" } ], "UpdateRecords": [ { "name": "records", "type": "UpdateZoneRecord[]" }, { "name": "zoneName", "type": "string" } ], "UpdateRecordsEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "UpdateRecords" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for UpdateRecordsEnvelope: { "payload": { <tool payload> }, "payloadType": "UpdateRecords", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| batchCreateDnsRecords | Description: Create multiple DNS records in a single transaction. Requires domain ownership. All records will be validated together against DNS zone rules. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="batchCreateDnsRecords". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of CreateRecordsEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: CreateRecordsEnvelope EIP-712 Types: { "CreateRecordsEnvelope_Payload_Records": [ { "name": "type", "type": "string" }, { "name": "name", "type": "string" }, { "name": "ttl", "type": "uint256" }, { "name": "rdata", "type": "string" } ], "CreateRecords": [ { "name": "records", "type": "CreateRecordsEnvelope_Payload_Records[]" }, { "name": "zoneName", "type": "string" } ], "CreateRecordsEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "CreateRecords" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for CreateRecordsEnvelope: { "payload": { <tool payload> }, "payloadType": "CreateRecords", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| batchDeleteDnsRecords | Description: Delete multiple DNS records by their IDs in a single transaction. Requires domain ownership. The zone will be validated after deletion. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="batchDeleteDnsRecords". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of DeleteRecordsEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: DeleteRecordsEnvelope EIP-712 Types: { "DeleteRecords": [ { "name": "recordsIds", "type": "string[]" }, { "name": "zoneName", "type": "string" } ], "DeleteRecordsEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "DeleteRecords" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for DeleteRecordsEnvelope: { "payload": { <tool payload> }, "payloadType": "DeleteRecords", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| toggleForwarding | Description: Enable or disable managed forwarding DNS records for a domain. Enabling forwarding requires a destination URL and validates that the resulting DNS zone remains valid. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="toggleForwarding". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of ToggleForwardingEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: ToggleForwardingEnvelope EIP-712 Types: { "ToggleForwarding": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "enableForwarding", "type": "bool" }, { "name": "forwardTo", "type": "string" } ], "ToggleForwardingEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "ToggleForwarding" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for ToggleForwardingEnvelope: { "payload": { <tool payload> }, "payloadType": "ToggleForwarding", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| toggleAutoEns | Description: Enable or disable the managed ENS TXT record for a domain. The DNS zone is validated against the resulting managed-record state before the setting is updated. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="toggleAutoEns". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of ToggleAutoEnsEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: ToggleAutoEnsEnvelope EIP-712 Types: { "ToggleAutoEns": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "enableAutoEns", "type": "bool" } ], "ToggleAutoEnsEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "ToggleAutoEns" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for ToggleAutoEnsEnvelope: { "payload": { <tool payload> }, "payloadType": "ToggleAutoEns", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| toggleVercelAnyCastRecords | Description: Enable or disable Vercel anycast DNS records for a domain. Subdomains use an apex CNAME, traditional apex domains use Vercel's anycast A record plus parking-style CAA records. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="toggleVercelAnyCastRecords". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of ToggleVercelAnyCastRecordsEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: ToggleVercelAnyCastRecordsEnvelope EIP-712 Types: { "ToggleVercelAnyCastRecords": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "enableVercelAnyCastRecords", "type": "bool" }, { "name": "overrideExistingRecords", "type": "bool" } ], "ToggleVercelAnyCastRecordsEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "ToggleVercelAnyCastRecords" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for ToggleVercelAnyCastRecordsEnvelope: { "payload": { <tool payload> }, "payloadType": "ToggleVercelAnyCastRecords", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| parkDomain | Description: Park a domain by setting up default parking DNS records (A and AAAA records pointing to the parking server). Optionally override existing conflicting records. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="parkDomain". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of ParkDomainEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: ParkDomainEnvelope EIP-712 Types: { "ParkDomain": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "overrideExistingRecords", "type": "bool" } ], "ParkDomainEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "ParkDomain" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for ParkDomainEnvelope: { "payload": { <tool payload> }, "payloadType": "ParkDomain", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| toggleDomainParking | Description: Park a domain by setting up default parking DNS records (A and AAAA records pointing to the parking server). Optionally override existing conflicting records. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="toggleDomainParking". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of ToggleDomainParkingEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: ToggleDomainParkingEnvelope EIP-712 Types: { "ToggleDomainParking": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "enableParking", "type": "bool" }, { "name": "overrideExistingRecords", "type": "bool" } ], "ToggleDomainParkingEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "ToggleDomainParking" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for ToggleDomainParkingEnvelope: { "payload": { <tool payload> }, "payloadType": "ToggleDomainParking", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| isDomainParked | Check whether a domain has the standard parking DNS records configured. Returns true if the domain is parked, false otherwise. |
| toggleAutoRenew | Description: Enable or disable automatic renewal for a domain. When enabled, the domain will be renewed automatically before expiration using the available payment methods on the owner wallet. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="toggleAutoRenew". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of ToggleAutoRenewEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: ToggleAutoRenewEnvelope EIP-712 Types: { "ToggleAutoRenew": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "enableAutoRenew", "type": "bool" } ], "ToggleAutoRenewEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "ToggleAutoRenew" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for ToggleAutoRenewEnvelope: { "payload": { <tool payload> }, "payloadType": "ToggleAutoRenew", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| getAutoRenew | Check whether automatic renewal is enabled for a domain. Requires domain ownership. |
| getUser | Retrieve the current user. |
| getUserPreferences | Retrieve the current user's global domain defaults (autoEns, autoRenew). These apply to new domains when an order item doesn't override them. |
| updateUserPreferences | Update the current user's global domain defaults (autoEns, autoRenew). Omitted fields are left unchanged. |
| getUserDomains | Retrieve all domains owned by the current user. Returns domain details including DNS status, nameservers, and expiration dates. |
| requestNfscFaucet | Request NFSC test tokens on Sepolia. Rate limited by user and wallet address. |
| getUserOrders | Retrieve all order items for the current user. Returns order items sorted by creation date in descending order. |
| getOrder | Retrieve detailed information about an order including items, payments, and user details. User must own the order. |
| getOrderItems | Retrieve all order items for the current user, sorted by creation date in descending order. |
| registerDomainForTrial | Description: Purchase a single domain instantly for trial. Validates domain availability and creates the order, the domain is only registered for a couple of days before it expires or renewed if you please Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="registerDomainForTrial". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of RegisterTrialDomainEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: RegisterTrialDomainEnvelope EIP-712 Types: { "RegisterTrialDomainEnvelope_Payload_DomainSetupOptions": [ { "name": "autoPark", "type": "bool" }, { "name": "autoEns", "type": "bool" }, { "name": "autoRenew", "type": "bool" }, { "name": "dnssec", "type": "bool" }, { "name": "keepExistingNameservers", "type": "bool" } ], "RegisterTrialDomain": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "domainSetupOptions", "type": "RegisterTrialDomainEnvelope_Payload_DomainSetupOptions" } ], "RegisterTrialDomainEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "RegisterTrialDomain" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for RegisterTrialDomainEnvelope: { "payload": { <tool payload> }, "payloadType": "RegisterTrialDomain", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| registerDomain | Description: Purchase a single domain instantly without adding to cart. Validates domain availability, creates payments and order, then starts the order processing workflow. Payment is taken from the NFSC balance first; any remainder is charged to the credit card saved on the Namefi profile. Card legs are at least $1.00 — when the shortfall is smaller, the card is charged $1.00 and correspondingly less NFSC is used. If neither rail covers the price, the request fails with links to top up NFSC or save a card. The `payments` array in the response shows the planned split; legs are charged asynchronously after the order is created. Instructions: 1. MCP tool arguments use a wrapper object: { headers, body }. 2. Put authentication headers inside headers. Do not rely on the outer MCP HTTP request headers for tool authentication. 3. Put the procedure payload inside body.payload. 4. For EIP-712 signed calls, build the full signed envelope in body using payload, payloadType, nonce, and timestamp. Fetch signing metadata with getEip712Domain and getEip712TypesForMethod using method="registerDomain". 5. For EIP-712, include these headers in headers: x-namefi-signer: <checksummed wallet address that signed>, x-namefi-signature: <0x-prefixed typed-data signature>, x-namefi-eip712-type: <one of InstantRegisterDomainEnvelope, InstantRegisterDomainDefaultWalletEnvelope>. 6. For SIWE auth, include x-namefi-siwe-token: <token> in headers and prepare it with getSiweNonce, prepareSiweMessage, verifySiweSignature, and getAllowedChains. 7. If you call through 1ShotPay, also include x-oneshot-singed-on-behalf: <accountAddress from get_info> in headers. EIP-712 Details: Signing Domain: {"name":"Namefi","version":"1"} Accepted Primary Types: InstantRegisterDomainEnvelope, InstantRegisterDomainDefaultWalletEnvelope EIP-712 Types: { "InstantRegisterDomainEnvelope_Payload_DomainSetupOptions": [ { "name": "autoPark", "type": "bool" }, { "name": "autoEns", "type": "bool" }, { "name": "autoRenew", "type": "bool" }, { "name": "dnssec", "type": "bool" }, { "name": "keepExistingNameservers", "type": "bool" } ], "InstantRegisterDomainEnvelope_Payload_NftReceivingWallet": [ { "name": "chainId", "type": "uint256" } ], "InstantRegisterDomain": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "durationInYears", "type": "uint256" }, { "name": "domainSetupOptions", "type": "InstantRegisterDomainEnvelope_Payload_DomainSetupOptions" }, { "name": "nftReceivingWallet", "type": "InstantRegisterDomainEnvelope_Payload_NftReceivingWallet" } ], "InstantRegisterDomainEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "InstantRegisterDomain" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ], "InstantRegisterDomainDefaultWalletEnvelope_Payload_DomainSetupOptions": [ { "name": "autoPark", "type": "bool" }, { "name": "autoEns", "type": "bool" }, { "name": "autoRenew", "type": "bool" }, { "name": "dnssec", "type": "bool" }, { "name": "keepExistingNameservers", "type": "bool" } ], "InstantRegisterDomainDefaultWallet": [ { "name": "normalizedDomainName", "type": "string" }, { "name": "durationInYears", "type": "uint256" }, { "name": "domainSetupOptions", "type": "InstantRegisterDomainDefaultWalletEnvelope_Payload_DomainSetupOptions" } ], "InstantRegisterDomainDefaultWalletEnvelope": [ { "name": "payloadType", "type": "string" }, { "name": "payload", "type": "InstantRegisterDomainDefaultWallet" }, { "name": "timestamp", "type": "uint256" }, { "name": "nonce", "type": "string" } ] } Example body for InstantRegisterDomainEnvelope: { "payload": { <tool payload> }, "payloadType": "InstantRegisterDomain", "nonce": "<random_string>", "timestamp": <unix_seconds> } Example body for InstantRegisterDomainDefaultWalletEnvelope: { "payload": { <tool payload> }, "payloadType": "InstantRegisterDomainDefaultWallet", "nonce": "<random_string>", "timestamp": <unix_seconds> } Related Tools: - getEip712Domain, getEip712TypesForMethod, getAllEip712Types - getSiweNonce, prepareSiweMessage, verifySiweSignature, getAllowedChains |
| registerWithRecords | Purchase a single domain instantly and apply DNS records after processing. Payment is taken from the NFSC balance first; any remainder is charged to the credit card saved on the Namefi profile (card legs are at least $1.00). |
| getOrderPaymentMethodsDetails | Retrieve payment method details for an order, including card info for Stripe payments and wallet addresses for on-chain payments. |
| registerDomainX402 | Purchase a single domain instantly without adding to cart. Validates domain availability, creates payments and order, then starts the order processing workflow. |
| registerDomainMPP | Purchase a single domain instantly with MPP using Tempo or Stripe. |
| getDomainsAvailableForTrial | Retrieve a list of domains or parent domains(ie; their subdomains are available for trial) |
| getBalance | Retrieve NFSC (Namefi Stable Coin) balance across all supported blockchain chains for the authenticated user's linked wallet addresses. Returns both raw contract values and human-readable USD amounts. |
| checkAvailability | Check if a domain is available for registration. Returns availability status, pricing details, current owner (if any), and registration constraints. |
| checkBulkAvailability | Check if a list of domains are available for registration. Returns availability status, pricing details, current owner (if any), and registration constraints. |
| getSuggestions | Generate domain suggestions based on a search query. Supports pagination and optional parent domain filtering for third-level domain suggestions. |
| listOutboundRuns | List the authenticated user's outbound lead-finding runs, newest first. Use this to resume recent work before starting a new run. |
| startOutboundRun | Start lead discovery for a domain. If an active run already exists for the same domain, the existing run is returned instead of creating duplicate work. |
| getOutboundRun | Get the current status and aggregate counts for one outbound lead-finding run. Poll using pollAfterSeconds while status is QUEUED or RUNNING. |
| listOutboundLeads | List discovered leads for a run in ranked order with public rationale, contacts, and generated outreach drafts when available. The ranking is represented by response order; internal score and rank fields are intentionally not exposed. |
| prepareOutboundOutreach | Generate contact research and an outreach email draft for a lead. Existing drafts are returned without spending additional generation credits. |
| getSiweNonce | Generate and store a replay-protected nonce for a wallet address before signing a SIWE message. |
| prepareSiweMessage | Verify that a previously issued nonce still exists and return the canonical SIWE message payload to sign. |
| verifySiweSignature | Verify a signed SIWE message, consume its nonce, and return a session token plus stored session details. |
| getAllowedChains | Retrieve the list of blockchain networks that are allowed for SIWE authentication. |
| getEip712Domain | Return the EIP-712 domain separator used for Namefi payload signing. The Namefi domain is chain-agnostic (chainId omitted) to allow cross-chain signatures. |
| getAllEip712Types | Return every registered EIP-712 struct type used by the Namefi API. |
| getEip712TypesForMethod | Return the accepted primary types and full type map for a specific API operation that supports EIP-712 authentication. |
| startDeviceAuth | Begin a device-authorization login: creates a pending request and returns a browser confirmation URL plus a token to poll for the result. |
| getDeviceAuthStatus | Long-poll the status of a device login request. Returns the minted JWT once the user approves, or a terminal state (cancelled/expired). Holds the connection up to ~25s while pending. |
| exchangeOAuthCode | Exchange an authorization code (from the redirect) plus the PKCE code verifier for the account JWT. Single-use; verifies the code is bound to the same client_id and redirect_uri. |