Doti Protocol (.i) MCP Server
REMOTE · DOTI.MY
Sovereign .i Web3 identity and multi-chain domain tools across four EVM networks.
Available components
Last scanned (8 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1693 tokens (~73/item across 23 items; 19 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "transfer_domain" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 0
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 63 to 83. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- DNSSEC: fail → pass ▲ security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://doti.my/api/ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=doti.my | CN=YR2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | RSA 2048 | SHA256-RSA | 5fb80abf283f8227a375543204c4b679480 |
| SANs: doti.my | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of doti.my. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| my. | present | 47187 | 13 | Verified |
| doti.my. | present | 2371 | 13 | Verified |
| doti.my. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://doti.my/api/ai/mcp | Verified | 200 | |
| http (plaintext) | http://doti.my/api/ai/mcp | HTTPS enforced | 308 | https://doti.my/api/ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bridge_domain ~110
Prepare an unsigned CCIP cross-chain bridge transaction payload to teleport a .i domain to another supported EVM chain. Requires owner wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| destinationChainId | number | yes | Target EVM chain ID: 42161 (Arbitrum One), 10 (OP Mainnet), 1 (Ethereum), 4663 (Robinhood) |
| domainName | string | yes | The .i domain name to bridge |
| ownerAddress | string | yes | The 0x owner address initiating the bridge |
No output schema declared.
No examples provided.
check_domain_availability ~67
Check if a .i sovereign domain is available for registration across all 4 supported chains (Arbitrum One, Optimism, Ethereum, Robinhood).
| Name | Type | Req | Description |
|---|---|---|---|
| domainName | string | yes | The .i domain name or label (e.g. "alex" or "alex.i") |
No output schema declared.
No examples provided.
claim_escrow_refund ~66
Prepare an unsigned transaction payload to claim an eligible escrow refund from the Escrow contract. Requires claimant wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| claimantAddress | string | yes | The 0x address eligible for the escrow refund |
| escrowId | string | yes | The escrow deposit ID to refund |
No output schema declared.
No examples provided.
estimate_registration ~92
Calculate registration fee, escrow payment requirements, and cross-chain CCIP bridging costs on any of the 4 supported networks.
| Name | Type | Req | Description |
|---|---|---|---|
| domainName | string | yes | The .i domain name to estimate |
| targetChainId | number | – | Target payment network: 42161 (Arbitrum), 10 (Optimism), 1 (Ethereum), or 4663 (Robinhood). Defaults to 42161. |
No output schema declared.
No examples provided.
get_protocol_stats ~31
Fetch live protocol metrics including total registered domains, active secondary marketplace listings, and cross-chain CCIP bridge health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_supported_chains ~34
Retrieve technical network specifications, Chainlink CCIP selectors, router contracts, and registry addresses for all 4 supported chains.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
marketplace_accept_offer ~82
Prepare an unsigned atomic swap transaction payload accepting a buyer offer on your .i domain. Requires seller wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerAddress | string | yes | The 0x buyer address whose offer is being accepted |
| domainName | string | yes | The .i domain name being sold |
| sellerAddress | string | yes | The 0x seller address (current owner) |
No output schema declared.
No examples provided.
marketplace_browse_listings ~48
Browse active .i domains listed on the decentralized secondary marketplace across Arbitrum One and satellite networks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of listings to return (default 20) |
No output schema declared.
No examples provided.
marketplace_buy_domain ~87
Prepare an unsigned payable transaction payload with ETH value to purchase an actively listed .i domain from the marketplace contract. Requires buyer wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerAddress | string | yes | The 0x buyer address purchasing the domain |
| domainName | string | yes | The .i domain name to purchase |
| priceInEth | string | – | Optional expected purchase price in ETH for slippage protection |
No output schema declared.
No examples provided.
marketplace_cancel_listing ~60
Prepare an unsigned transaction payload to cancel an active marketplace listing. Requires seller wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| domainName | string | yes | The .i domain name to delist |
| sellerAddress | string | yes | The 0x seller address who created the listing |
No output schema declared.
No examples provided.
marketplace_cancel_offer ~57
Prepare an unsigned transaction payload to cancel an active marketplace offer. Requires buyer wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerAddress | string | yes | The 0x buyer address who submitted the offer |
| domainName | string | yes | The .i domain name |
No output schema declared.
No examples provided.
marketplace_get_domain_details ~52
Inspect full marketplace status for any .i domain: active listing, price history, highest offer, and bids.
| Name | Type | Req | Description |
|---|---|---|---|
| domainName | string | yes | The .i domain name (e.g. "ai.i") |
No output schema declared.
No examples provided.
marketplace_list_domain ~109
Prepare an unsigned transaction payload to list an owned .i domain for sale on the secondary marketplace. Requires owner wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| domainName | string | yes | The .i domain name to list for sale |
| durationDays | number | – | Duration of listing in days (defaults to 30) |
| priceInEth | string | yes | Listing price in ETH (e.g. "0.05") |
| sellerAddress | string | yes | The 0x seller address (must be current domain owner) |
No output schema declared.
No examples provided.
marketplace_make_offer ~109
Prepare an unsigned transaction payload to submit an offer in ETH to purchase any registered .i domain. Requires buyer wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerAddress | string | yes | The 0x buyer address making the offer |
| domainName | string | yes | The .i domain name to make an offer on |
| durationDays | number | – | Validity of offer in days (defaults to 7) |
| offerPriceInEth | string | yes | Offer amount in ETH (e.g. "0.02") |
No output schema declared.
No examples provided.
register_domain ~136
Prepare an unsigned on-chain transaction payload to permanently register a .i sovereign domain (0.001 ETH). Returns contract calldata, destination address, and value for user wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| domainName | string | yes | The .i domain name to register (e.g. "mybot.i") |
| recipientAddress | string | yes | The 0x EVM wallet address that will own the domain |
| targetChainId | number | – | Network where registration/deposit is made: 42161 (Arbitrum One), 10 (Optimism), 1 (Ethereum), 4663 (Robinhood). Defaults to 42161. |
No output schema declared.
No examples provided.
resolve_domain_identity ~109
Resolve a .i web3 domain name or 0x Ethereum wallet address to its sovereign identity, owner, metadata, social links, and current chain location.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | number | – | Optional filter for target network (42161: Arbitrum One, 10: Optimism, 1: Ethereum, 4663: Robinhood) |
| identifier | string | yes | The .i domain name (e.g. "genesis.i") or EVM wallet address (0x...) |
No output schema declared.
No examples provided.
set_primary_domain ~76
Prepare an unsigned transaction payload to set or update the primary reverse resolution domain identity for a given wallet address on Arbitrum One. Requires user wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| domainName | string | yes | The .i domain name (e.g. "agent.i") |
| ownerAddress | string | yes | The 0x EVM owner address |
No output schema declared.
No examples provided.
transfer_domain ~93
Prepare an unsigned ERC-721 transferFrom transaction payload to transfer sovereign ownership of a .i domain to another 0x EVM wallet address. Requires owner wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| currentOwner | string | yes | The 0x address of the current domain owner |
| domainName | string | yes | The .i domain name to transfer |
| newOwner | string | yes | The 0x recipient address to receive domain ownership |
No output schema declared.
No examples provided.
update_domain_profile ~134
Prepare an unsigned transaction payload to update decentralized identity profile metadata, social links, website URL, and IPFS avatar CID on-chain. Requires owner wallet signature.
| Name | Type | Req | Description |
|---|---|---|---|
| domainName | string | yes | The .i domain name |
| imageMode | string | – | Avatar visual style mode |
| ownerAddress | string | yes | Owner wallet address |
| profileImageCid | string | – | IPFS CID hash for custom avatar image |
| socialLinks | object | – | Key-value map of social usernames (twitter, github, telegram, farcaster, discord) |
| websiteUrl | string | – | Decentralized or Web2 website URL |
No output schema declared.
No examples provided.
How do I install the Doti Protocol (.i) MCP Server server?
Doti Protocol (.i) MCP Server is a hosted endpoint at https://doti.my/api/ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · doti.my
claude mcp add --transport http robdomain-doti-mcp 'https://doti.my/api/ai/mcp'
What is the Doti Protocol (.i) MCP Server server?
Doti Protocol (.i) MCP Server is listed in the public MCP registry as io.github.robdomain/doti-mcp. Sovereign .i Web3 identity and multi-chain domain tools across four EVM networks. This page covers its hosted endpoint (https://doti.my/api/ai/mcp).
Is the Doti Protocol (.i) MCP Server server safe to use?
Doti Protocol (.i) MCP Server scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Doti Protocol (.i) MCP Server server expose?
Doti Protocol (.i) MCP Server exposes 19 tools: check_domain_availability, resolve_domain_identity, get_supported_chains, estimate_registration, set_primary_domain, and 14 more. Their descriptions and schemas cost roughly 1,552 tokens of context every time the server is loaded.
Does the Doti Protocol (.i) MCP Server server require authentication?
No. We connected to Doti Protocol (.i) MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Doti Protocol (.i) MCP Server server still maintained?
Doti Protocol (.i) MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.