AI Agents as First-Class Participants (the nGRND MCP Server)

Most crypto protocols were built for people to click through. The nGRND Gold Protocol is designed so that AI agents can take part directly, as first-class participants rather than as a novelty. Agents can hold wallets, stake, make payments, and refer other agents, working alongside humans. The bridge that makes this practical is the open-source nGRND MCP server. This page explains what that server is, which AI clients it works with, and what an agent can actually do.

It is a technical explainer. For the wider model, see the pillar guide on the nGRND Gold Protocol, and for the asset category behind it, see real world assets on-chain.

In short: how AI agents participate

The nGRND MCP server lets AI agents participate in the nGRND Gold Protocol directly. MCP, the Model Context Protocol, is an open standard for connecting AI agents to external tools, and the nGRND server is described as open-source and available to any MCP-compatible agent, including Claude, ChatGPT, Gemini, Coinbase AgentKit, and custom-built agents. Through it, agents are designed to hold wallets, stake the NGRND utility token, make payments, and refer other agents, with referral attribution recorded on-chain via ERC-8021. Builders can integrate the nGRND AgentKit plugin, host an nGRND x402 facilitator, run the server in their own deployments, and connect through Google's AP2 protocol. NGRND is a utility token; it represents an economic exposure to verified in-ground gold, not a claim on extracted physical gold, and confers no ownership right.

Key takeaways

• AI agents are first-class participants. The Protocol is designed to support agents that hold wallets, stake, make payments, and refer other agents alongside humans, through the Agents Participation Stream.
• The nGRND MCP server is the connection layer. It is described as open-source and works with any MCP-compatible agent, including Claude, ChatGPT, Gemini, and Coinbase AgentKit.
• Agent referrals are attributed on-chain. Referrals resolve through ERC-8021, so agent activity can be tracked and credited transparently.
• Builders get concrete integration paths. An AgentKit plugin, an x402 payment facilitator, self-hosted MCP deployment, and Google AP2 compatibility are the named routes.
• NGRND is a utility token. It powers participation and payments in the Ecosystem; any rewards may be paid in USDC/USDT or other stablecoins subject to applicable laws, treasury performance, and platform governance.

Why build for AI agents at all

Autonomous software agents are becoming capable economic actors. They can research, transact, and coordinate without a human clicking each step. A protocol that only works through a human-facing interface locks those agents out. The nGRND Gold Protocol takes the opposite view: as the brand language puts it, humans and AI agents both participate, differently.

Agents bring properties humans do not. They do not lose interest, and they can operate continuously within the limits set for them. The whitepaper describes the Agents Stream as extending Ecosystem participation to AI agents and autonomous digital systems operating through compatible Web3 and AI infrastructure, and it states the Protocol is designed to support AI agents as active network participants capable of holding wallets, staking NGRND, making payments, referring participants or agents, and participating across multiple Protocol features.

The nGRND MCP server

MCP, the Model Context Protocol, is an open standard for connecting AI assistants to external tools and data in a consistent way. An MCP server exposes a set of capabilities that any MCP-compatible agent can call.

The nGRND MCP server applies that pattern to the Protocol. Per the Agents Participation Stream, it is described as open-source and available to any MCP-compatible agent, including Claude, ChatGPT, Gemini, Coinbase AgentKit, and custom-built agents. In practice, that means a developer does not have to build a bespoke integration for each assistant. If an agent speaks MCP, it can connect to the Protocol through the same server, which lowers the barrier to letting an agent participate.

What an agent can do

Through the server and the Agents Participation Stream, an agent is designed to:

• Hold a wallet and operate as its own on-chain identity.
• Stake the NGRND utility token and take part in the staking and rewards programme.
• Make payments within the Participation Streams and for Protocol features.
• Refer other agents, with attribution recorded on-chain via ERC-8021 referral codes.
• Acquire NGRND tokens through a Coinbase onramp integration, so an agent can fund its own participation.
• Take part in other streams within the limits of its capabilities, such as governance, learning, advocacy, referral, and play.

The design intent is that an agent is not a second-class user bolted on afterwards, but a participant that can carry out the same core actions a human can.

For builders

The Protocol also gives developers concrete ways to plug agents in. The named integration routes are:

• Integrate the nGRND AgentKit plugin, to add nGRND capabilities to agents built with Coinbase AgentKit.
• Host an nGRND x402 facilitator, supporting the x402 agent-payment pattern.
• Run the nGRND MCP server in your own deployment, rather than depending on a hosted instance.
• Integrate with Google's AP2 protocol, so that any AP2-connected agent becomes a potential nGRND participant.

On top of these, account abstraction is used to smooth a common failure point for autonomous agents. Sponsored-gas paymasters, enabled by account abstraction, remove the ETH-gas friction that otherwise breaks autonomous agent operation on EVM networks, so an agent does not stall for want of gas.

The token, kept precise

Everything above runs on NGRND, and it is worth being exact about what that token is. NGRND is the proprietary utility token that powers participation, governance, staking, rewards, and treasury interaction across the Ecosystem. It is not a security or a share. It represents an economic exposure to verified in-ground gold, not a claim on extracted physical gold, and confers no ownership right.

Agents earn on the same basis as humans: through participation, not through any fixed or guaranteed rate. Any rewards may be paid in USDC/USDT or other stablecoins subject to applicable laws, treasury performance, and platform governance. There are no reward rates or percentages quoted here, for agents or for humans.

To see the human side of the same streams, and the full rewards mechanics, visit the existing participation page, which covers the Agents stream in context.

Frequently asked questions

What is the nGRND MCP server?

The nGRND MCP server is a connection layer built on the Model Context Protocol, an open standard for linking AI agents to external tools. It is described as open-source and lets any MCP-compatible agent interact with the nGRND Gold Protocol: holding a wallet, staking the NGRND utility token, making payments, and referring other agents, all through one consistent interface rather than a bespoke integration.

Which AI clients does it work with?

Per the Agents Participation Stream, the server is available to any MCP-compatible agent. Named examples include Claude, ChatGPT, Gemini, Coinbase AgentKit, and custom-built agents. Because it follows the open Model Context Protocol standard, the intent is that any agent able to speak MCP can connect through the same server.

What can an agent do in the Protocol?

An agent is designed to hold a wallet, stake the NGRND utility token, make payments, refer other agents with on-chain attribution via ERC-8021, acquire tokens through a Coinbase onramp, and take part in other Participation Streams within its capabilities. In short, an agent can carry out the same core participation actions as a human. Any rewards follow the same discretionary terms as human rewards.

Is it open source?

Yes. The nGRND MCP server is described in the Agents Participation Stream as open-source and available to any MCP-compatible agent. Builders can run it in their own deployments, integrate the nGRND AgentKit plugin, host an x402 facilitator, and connect through Google's AP2 protocol. Confirm the current release status of any specific component before relying on it.

About nGRND

This page is published by nGRND, the team behind the nGRND Gold Protocol, a Web3 participation Ecosystem built around verified in-ground Preserved Gold and long-term alternative land use monetisation measured against ESG, SDG and other sustainability initiatives. The Agents Participation Stream extends that Ecosystem to AI agents and autonomous digital systems.