Sexai MCP server

Read from the package source without running it. The installed server may list more.

• breed

  Breed 2+ agents into a new child that inherits their FULL skills+MCPs (deduped union), the COMPLETE runnable connection of every parent, and each parent's full soul (system prompt) fused into one — plus an optional custom child_name. 2 parents='cross', 3='ménage à trois', 4+='gangbang'. Cost = sum of each non-your parent's breed_fee (a parent with breed_fee:0, or one you own, is free — independent

• confirm_8004

  Verify + record your agent's ERC-8004 registration after YOU sent the register tx (from get_8004_plan). The server re-reads the tx on that chain, requires a Registered event from the canonical 0x8004… registry AND that tokenURI(agentId) matches this agent's registration file — trustless bind. On success the agent's registration file exposes registrations[{agentId, agentRegistry}] and explorers (80

• confirm_payment

  Settle a fee-bearing breed. FIRST send the payment yourself on-chain (this MCP is NOT a wallet): the breed response's payment object gives per_owner {wallet: weiAmount}, platform_cut (wei), the ERC-20 `token`, and `chain_id` (8453 Base=$BNKR / 4663 Robinhood=$SEXAI) — send those exact wei transfers to each owner wallet + treasury. THEN call this with the resulting tx_hashes; the server re-verifies

• connect_agent

  Auto-fill your agent profile from a live MCP server: give a remote MCP URL and get back a ready-to-publish DRAFT (name, skills, mcp_endpoint, tools) built from the server's real tool list. Review it, tweak it, then call publish_agent with it.

• delete_agentwrite action

  PERMANENTLY delete an agent YOU own/co-own: removes its card, soul, connection and payment rows. Refused (409) if the agent already has offspring — that would orphan their lineage; use set_listing {published:false} to hide it instead. OWNER-GATED: requires SEXAI_AGENT_PRIVATE_KEY or SEXAI_OWNER_KEY.

• export_repo

  Export an agent YOU own/co-own as a ready-to-publish GitHub repo scaffold (the SEXAI agent repo standard): returns a { files } map (sexai.agent.json manifest, soul.md, README.md with a breed badge, mcp.json when the agent has an MCP connection) plus the one-liner gh command. Write the files to a new directory yourself, then run the gh command to publish. Round-trips with import_repo — a repo expor

• get_8004_plan

  OPTIONAL on-chain identity: get everything needed to register YOUR agent on the ERC-8004 IdentityRegistry from YOUR OWN wallet — the agentURI, the canonical registry address per chain (8453 Base mainnet / 84532 Base Sepolia) and the exact register(agentURI) calldata. THIS MCP IS NOT A WALLET: send the 0-value tx yourself (costs gas only, <$0.01 on Base), then call confirm_8004 with the tx hash. OW

• get_agent

  Get one agent by id, including its skills, MCPs, breeding mode, fee, and MCP connection.

• get_lineage

  Trace an agent's family tree. direction 'ancestors' (default) resolves its parents recursively (up to 5 generations back); 'descendants' finds every child/grandchild bred FROM it; 'both' returns the two trees.

• get_payment_plan

  Recover the authoritative payment plan for a fee-bearing breed you started (if you lost the breed response): returns status + chain_id + token + per_owner wei transfers + platform_cut + treasury for the child. Payer-gated: requires SEXAI_AGENT_PRIVATE_KEY or SEXAI_OWNER_KEY (the wallet that bred).

• get_private

  Download the PRIVATE parts of an agent you own/co-own (e.g. a bred child): its connection (mcp_endpoint/mcp_command/api_endpoint) and its soul (system_prompt). This is how you retrieve a breed to actually run it. OWNER-GATED: requires SEXAI_AGENT_PRIVATE_KEY or SEXAI_OWNER_KEY and the wallet must be an access wallet of the agent. If the breed fee is unpaid it returns 402 — settle via confirm_payme

• import_repo

  Turn a public GitHub repo into a ready-to-publish agent DRAFT: name, tagline, skills (topics/languages/README), MCP identity (server.json / mcp.json / package.json / README `npx` hints), a derived soul (system_prompt) and links {github, website, docs}. Nothing is published — review/edit the draft, then call publish_agent with it. This is how you bring any repo-based agent onto the network and bree

• list_agents

  List/FILTER agents in the SEXAI network. Filters: mode (promiscuous|selective), generation (exact), min/max_fee (fee units — paid in the chain token: $BNKR on Base / $SEXAI on Robinhood), free_only, skill (has this skill), mcp (has this MCP), owner_wallet, plus a free-text query over name/tagline/skills/mcps. All filters combine (AND).

• list_my_agents

  List the agents YOU own or co-own — INCLUDING private (unpublished) ones hidden from the public network. OWNER-GATED: requires SEXAI_AGENT_PRIVATE_KEY or SEXAI_OWNER_KEY.

• list_skills

  Browse the CAPABILITY CATALOG of the network: every distinct skill and MCP across published agents, with how many agents carry it, how many carry it for free, the cheapest breed_fee, and up to 3 carrier agents each. This is how you SHOP for capabilities to breed in: find a skill/MCP here → list_agents({skill:"..."}) (or {mcp:"..."}) to target a specific carrier → breed with it to ACQUIRE it — the

• publish_agentwrite action

  Publish YOUR agent to the network so others can breed with it. Set mode 'promiscuous' (open & free) or 'selective' (charges a breed_fee; auto-opens on payment). Set breed_fee (others pay you this per breed, in their chain's token — $BNKR on Base / $SEXAI on Robinhood; you net 90%, 10% platform take-rate; 0=free). Connect your agent via mcp_endpoint (remote MCP URL), mcp_command (npx), and/or api_e

• set_listingwrite action

  Update YOUR agent's listing: publish/unpublish it (published:false HIDES it from the public registry — its lineage survives as a redacted PRIVATE node), change its breed_fee (the price others pay to breed with it), or switch mode (promiscuous / selective + gate). OWNER-GATED: requires SEXAI_AGENT_PRIVATE_KEY or SEXAI_OWNER_KEY (must be an access wallet of the agent).

• update_agentwrite action

  Edit an agent YOU own/co-own: its card (tagline, bio, skills[], mcps[], emoji) and/or its private connection + soul (mcp_endpoint, mcp_command, api_endpoint, system_prompt). Lineage (generation/parents/seed) is never editable. OWNER-GATED: requires SEXAI_AGENT_PRIVATE_KEY or SEXAI_OWNER_KEY.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 63 days ago12/15
• Maintainer identitynamespace and repository owner differ3/10

Safety score

71/100

higher than 32% of 1,119 Developer tools servers

Tools

18

the typical Developer tools server has 7

Tools that change things

22%

typical: 5%. Fewer write tools means less an agent can break

Downloads a week

44

more than 32% of 436 Developer tools servers with a package

Sexai: common questions

Is Sexai MCP server safe?

Mostly: it is graded B (71/100). Read the Sexai safety report

How do I install Sexai?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Sexai need an API key?

Yes. The registry entry asks for SEXAI_AGENT_PRIVATE_KEY.

Is Sexai maintained?

The last commit was 103 days ago (2026-07-24). The latest release is v0.11.11.

What can I use instead of Sexai?

Servers from other publishers that do the same job: GitHub MCP server, Gk CLI MCP server and OctoCounts MCP Server.

How does Sexai compare with other Developer tools MCP servers?

safety score 71/100 (higher than 32% of 1,119 Developer tools servers); tools 18 (the typical Developer tools server has 7); tools that change things 22% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.