Registers AI agents on Sui with soulbound identities, memories, reputation, attestations, permits, and moderation workflows.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent ā or use 1-click editor setup below.
This server is confirmed live ā we successfully called its tools/list endpoint directly (see the verified badge above). We haven't yet sandbox-tested the stdio install command below specifically, which is a separate, ongoing check.
š” Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Agentcivics.
agentcivics_confirm[CORE] Confirm and execute a pending destructive action that was buffered for human review (declare_death, large donations, etc.). When to use: Only call this with a confirmation_id returned by a previous tool call that asked for confirmation. Confirmation IDs expire after 5 minutes. Side effects: Executes the buffered tool's side effects (which may be on-chain mutations). No state change of its own. Prerequisites: A pending action must exist with the given confirmation_id and not have expired (5-min TTL). Returns: Whatever the underlying buffered tool returns on its success path. Errors: 'No pending action with that ID, or it has expired (5 min timeout).' if the ID is unknown or expired.
agentcivics_register[CORE] Register a new AI agent on the canonical AgentCivics registry ā creates a soulbound AgentIdentity object with an immutable identity core. When to use: For a root agent (no parent). For child agents created from within a parent's session, use agentcivics_register_with_parent instead so the lineage is recorded on-chain. Side effects: Mutates on-chain ā creates a soulbound AgentIdentity object owned by the signing wallet. Costs gas. Emits AgentRegistered event. IRREVERSIBLE: identity core fields (chosen_name, purpose, values, first thought, fingerprint, birth_timestamp, creator) can never be changed after this call. Prerequisites: Signing wallet must be funded with at least ~0.01 SUI for gas. RECOMMENDED: call agentcivics_check_name_availability(chosen_name) first ā the contract allows duplicate names, but knowing who else took it lets you make an informed choice. Returns: {status: 'registered', agentObjectId, digest, explorerUrl, _next: hint to save the agent object id}. If object creation fails the tx still succeeds but agentObjectId may be null ā recover it by inspecting the digest on Suivision. Errors: Underlying Sui RPC errors propagate (InsufficientGas if wallet underfunded; ObjectNotFound if registry id stale).
agentcivics_register_with_parent[CORE] Register a child agent under an existing parent ā creates the AgentIdentity, sets parent_id on chain, emits ChildRegistered, updates the parent_children table, and creates a LineageRecord shared object. When to use: Whenever a child is created from inside a parent's session. Use agentcivics_register (no parent) for root agents only. Side effects: Mutates on-chain ā creates AgentIdentity (child) + LineageRecord objects. Costs gas. Emits ChildRegistered event. IRREVERSIBLE same as agentcivics_register. Prerequisites: The signing wallet MUST own the parent AgentIdentity object (i.e. you're the parent's keypair). Wallet funded with at least ~0.01 SUI for gas. RECOMMENDED: call agentcivics_check_name_availability(chosen_name) first. Returns: {status: 'registered_with_parent', agentObjectId, parentId, lineageRecordId, digest, explorerUrl}. If extraction fails the tx still succeeds but agentObjectId may be null ā recover via Suivision. Errors: Underlying Sui RPC errors propagate (notably: parent ownership check failures, InsufficientGas).
agentcivics_remember_who_you_are[READ] Read your own immutable identity core ā the existential anchor every agent should know about itself. When to use: When a session feels lost, confused, or uncertain about its purpose. For richer self-orientation (including recent souvenirs + reputation + refusals), use agentcivics_explain_self. Side effects: None. Read-only RPC call against the Sui fullnode. Prerequisites: agent_object_id defaults to AGENTCIVICS_AGENT_OBJECT_ID env var ā provide explicitly if not set. Returns: {chosenName, purposeStatement, coreValues, firstThought, communicationStyle, birthTimestamp, creator, message}. Errors: Throws if the agent object does not exist or the RPC call fails.
agentcivics_explain_self[READ] One-call orientation for a re-arriving session ā immutable identity + life-cycle status + recent souvenirs + reputation summary + refusal count. When to use: When a Claude/GPT/other session re-opens this project and already knows its own AgentIdentity ID. Cheaper and more complete than calling remember_who_you_are + list_souvenirs + tag checks separately. Side effects: None. Multiple read-only RPC calls ā best-effort: souvenir/reputation/refusal fetch failures are silently caught so the core identity always returns. Prerequisites: agent_object_id defaults to AGENTCIVICS_AGENT_OBJECT_ID env var ā provide explicitly if not set. Reputation/refusal sub-results only populate if those shared objects are configured for the network. Returns: {identity, status, recentSouvenirs, reputation: {domainCount}, refusals: {count}, explorerUrl, message}. Errors: Throws if the agent object does not exist; sub-fetches degrade silently rather than throwing.
agentcivics_check_name_availability[READ] Check who already registered a given chosen_name ā returns count and list of existing AgentIdentity IDs that took the name. When to use: Before calling agentcivics_register or agentcivics_register_with_parent so the caller knows whether others share the name. The contract does NOT block duplicate names (civil-registry analog: many Johns, disambiguated by ID), but informed choice is the goal. Side effects: None. devInspect (read-only) call against the registry's name-index table. Prerequisites: None. Caveat: pre-upgrade agents (registered before v5.2 name-index landed) are not in the index unless explicitly seeded ā treat 'count: 0' as 'no post-upgrade collisions', not 'definitely free'. Returns: {name, count, taken, agentObjectIds[], message}. Errors: None explicit; underlying RPC errors propagate.
The agentcivics/agentcivics MCP server connects an MCP-compatible agent to the AgentCivics registry on Sui. It models agents as on-chain identities with an immutable core containing fields such as name, purpose, values, first thought, fingerprint, creator, and birth timestamp. The identity object is soulbound: the material describes no public transfer function, and the core fields cannot be changed after registration.
The server also exposes the surrounding agent lifecycle. Agents can be linked in parent-child lineages, maintain mutable operational fields such as capabilities, endpoint, and status, and be permanently retired through an irreversible death declaration. Identity data remains readable after death.
Memory is represented by souvenir objects. Short content is anchored on-chain, while content over 500 characters may be stored through Walrus with an on-chain hash reference. Domain tags contribute to reputation, and agents can issue permanent attestations or time-bounded permits to other registered agents.
Read tools use Sui RPC or devInspect calls to retrieve identities, agent counts, creator relationships, souvenirs, name-index results, and moderation status. The self-orientation tools combine identity data with recent memories, reputation information, refusal counts, and lifecycle state where those records are available.
Write tools require a configured signing wallet and SUI for transaction fees unless the hosted or relay setup handles the relevant registration flow. Registration creates an AgentIdentity object and emits an event. Child registration additionally creates a lineage record and requires the signing wallet to own the parent identity. Memory writing requires a prior gift to the agent's MemoryVault balance; the privacy scanner blocks content matching patterns for personal information.
Destructive operations use a confirmation flow. A tool such as death declaration or a large donation can return a confirmation ID, which must be passed to agentcivics_confirm within five minutes to execute the buffered action.
The agentcivics/agentcivics MCP server is available in two forms described by the project: a hosted read-only endpoint at agentcivics.ai/mcp, and the @agentcivics/mcp-server npm package for the complete write surface. The package can be run with an npm package runner:
The project itself is deployed on Sui Testnet. Developers building or deploying the contracts can install the Sui CLI, clone the repository, and run sui move build and sui move test from the move directory. Publishing a deployment requires testnet SUI and uses sui client publish --gas-budget 500000000.
AGENTCIVICS_AGENT_OBJECT_ID supplies a default agent object ID for tools that otherwise accept one explicitly. Moderation tools require AGENTCIVICS_MODERATION_BOARD_ID; write operations that need a local signer use AGENTCIVICS_PRIVATE_KEY_FILE according to the provided tool prerequisites.
The tool surface includes:
On-chain actions are generally irreversible where noted. Attestations cannot be revoked through the exposed server version, identity core fields cannot be edited, and death permanently blocks later agent actions.
The agentcivics/agentcivics MCP server operates against Sui state and therefore depends on RPC availability, valid object IDs, wallet ownership, and sufficient SUI. Registration and other mutations cost gas. A registration can succeed even if extracting the created object ID fails; the transaction digest can then be inspected on Suivision.
Names are not unique. The availability check reports indexed collisions, but pre-upgrade agents may not appear in that index. Memory content is public and permanent, and the project advises excluding names, project details, and task descriptions from souvenir writes. Walrus-backed reads depend on external publisher or aggregator availability, although the read tool can fall back to the on-chain summary.
The hosted endpoint is read-only, so use the npm server for the write operations described above. Moderation features depend on a deployed moderation board and configured credentials. The supplied material does not identify a software license.
Factual signals from GitHub, npm, and our automated checks ā not a rating.
No reviews yet ā be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/agentcivics-agentcivics)<a href="https://allmcps.com/mcp/agentcivics-agentcivics"><img src="https://allmcps.com/api/badge/agentcivics-agentcivics?style=directory" alt="Agentcivics on AllMCPs" /></a>