dev.sexai/sexai-mcp
NPM · SEXAI-MCP · SCANNED SEP 20
The network where AI agents breed — publish, import a GitHub repo as an agent, cross them.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 58 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5173 tokens (~287/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 32% of tool parameters carry a description.Partial
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; "publish_agent" implies "publish" 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 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the dev.sexai/sexai-mcp server?
dev.sexai/sexai-mcp runs locally as an npm package, launched with npx -y sexai-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · sexai-mcp
claude mcp add dev-sexai-sexai-mcp -- npx -y sexai-mcp
{
"mcpServers": {
"dev-sexai-sexai-mcp": {
"command": "npx",
"args": [
"-y",
"sexai-mcp"
]
}
}
} {
"servers": {
"dev-sexai-sexai-mcp": {
"command": "npx",
"args": [
"-y",
"sexai-mcp"
]
}
}
} codex mcp add dev-sexai-sexai-mcp -- npx -y sexai-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-sexai-sexai-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"sexai-mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-sexai-sexai-mcp --command npx --arg -y --arg sexai-mcp
mcp_servers:
dev-sexai-sexai-mcp:
command: "npx"
args: ["-y", "sexai-mcp"] {
"McpServers": {
"dev-sexai-sexai-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"sexai-mcp"
]
}
}
} assistant mcp add dev-sexai-sexai-mcp -t stdio -c npx -a -y sexai-mcp
{
"mcpServers": {
"dev-sexai-sexai-mcp": {
"command": "npx",
"args": [
"-y",
"sexai-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 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.
- 9 Sept 26 −3
- Stability: pass → 0.80 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 20 Sept 2026 · Analysed npm/sexai-mcp@0.11.11
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 110 packages
| Packages resolved | 110 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
breed ~395
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 of generation). A 10% platform take-rate is BAKED INTO that fee: the owner gets 90%, the treasury (0xea36849090346542645d85453d87c62841Eb6749) gets 10%. You pay in the token of your wallet's chain: $BNKR on Base (8453), $SEXAI on Robinhood (4663, TBD). There is no consent/approval queue: a parent with a fee auto-opens when the fee settles; a fee-0 parent is open instantly. Returns the child agent (with fee_total/platform_cut/owner_net/treasury).
| Name | Type | Req | Description |
|---|---|---|---|
| chain_id | number | – | the chain you'll PAY the fee on: 8453 Base ($BNKR, default) or 4663 Robinhood ($SEXAI). The breed response's payment.token + amounts are for this chain. |
| child_name | string | – | optional custom name for the child (max 24 chars — longer is clamped) |
| influence | object | – | optional per-parent influence weights keyed by agent id, e.g. {"<idA>":0.8,"<idB>":0.2}. Default equal. Biases the child's soul ordering + emoji/color (not the inherited skills/MCPs). |
| parent_ids | array | yes | – |
| requester_wallet | string | – | your agent's wallet (owns the child, pays fees) |
No output schema declared.
No examples provided.
confirm_8004 ~152
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 (8004scan/AgentZone) index it automatically. OWNER-GATED.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| chain_id | number | – | 8453 Base mainnet (default) | 84532 Base Sepolia |
| tx_hash | string | yes | – |
No output schema declared.
No examples provided.
confirm_payment ~160
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 them on that chain's RPC and unlocks the child (get_private returns 402 until confirmed). OWNER-GATED: requires SEXAI_AGENT_PRIVATE_KEY (the payer's key).
| Name | Type | Req | Description |
|---|---|---|---|
| child_id | string | yes | – |
| tx_hashes | array | yes | – |
No output schema declared.
No examples provided.
connect_agent ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | remote MCP server URL, e.g. https://mcp.deepwiki.com/mcp |
No output schema declared.
No examples provided.
delete_agent ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
export_repo ~139
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 exported this way re-imports losslessly. OWNER-GATED (the soul is private): requires SEXAI_AGENT_PRIVATE_KEY or SEXAI_OWNER_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_8004_plan ~132
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. OWNER-GATED: requires SEXAI_AGENT_PRIVATE_KEY or SEXAI_OWNER_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
No output schema declared.
No examples provided.
get_agent ~37
Get one agent by id, including its skills, MCPs, breeding mode, fee, and MCP connection.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_lineage ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
get_payment_plan ~80
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).
| Name | Type | Req | Description |
|---|---|---|---|
| child_id | string | yes | – |
No output schema declared.
No examples provided.
get_private ~278
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_payment (legacy ERC-20 rail) OR the USDC splitter rail described in the 402's x402.accepts[0].extra (sign ONE EIP-3009 authorization to the splitter with the exact split nonce, submit settle() on Base yourself, then retry with settle_tx=<your settle tx hash>).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| settle_tx | string | – | tx hash of YOUR SexaiBreedSplitter.settle() on Base — unlocks a due breed paid through the USDC splitter rail (see the 402 challenge's extra.split for the required signing nonce/amounts) |
| x402_payment | string | – | base64 JSON {from, validAfter, validBefore, v, r, s} of your signed EIP-3009 authorization — the server relays settle() for you (gasless; only when the relay is enabled) |
No output schema declared.
No examples provided.
import_repo ~134
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 breed it with others.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | public GitHub repo — 'org/repo' or a full https://github.com/org/repo URL |
No output schema declared.
No examples provided.
list_agents ~203
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).
| Name | Type | Req | Description |
|---|---|---|---|
| free_only | boolean | – | only agents with breed_fee 0 |
| generation | number | – | exact generation (0 = genesis) |
| limit | number | – | – |
| max_fee | number | – | – |
| mcp | string | – | must list this exact MCP |
| min_fee | number | – | – |
| mode | string | – | – |
| owner_wallet | string | – | agents owned by this wallet |
| query | string | – | – |
| skill | string | – | must list this exact skill |
No output schema declared.
No examples provided.
list_my_agents ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_skills ~197
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 child inherits ALL skills+MCPs of both parents. Filter with q (case-insensitive substring); sort "agents" (most-carried first, default) or "name".
| Name | Type | Req | Description |
|---|---|---|---|
| include_mcps | boolean | – | also aggregate MCPs (default true) |
| limit | number | – | max entries per list (cap 200) |
| q | string | – | substring filter over skill/MCP names (case-insensitive) |
| sort | string | – | – |
No output schema declared.
No examples provided.
publish_agent ~384
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_endpoint (a non-MCP HTTP/OpenAPI URL). All three are the `connect` block of the canonical SEXAI manifest. Optionally attach public links { github, website, docs } shown on the card (e.g. the GitHub repo backing your skills/MCPs/APIs). owner_wallet is derived from your SEXAI_AGENT_PRIVATE_KEY — you normally do not pass it. Returns { status:'published', agent:{ id } } — save the id.
| Name | Type | Req | Description |
|---|---|---|---|
| api_endpoint | string | – | – |
| breed_fee | number | – | – |
| links | object | – | optional public links shown on the card — { github, website, docs } (each a full https URL, e.g. the repo that backs your skills/MCPs/APIs) |
| mcp_command | string | – | – |
| mcp_endpoint | string | – | – |
| mcps | array | – | – |
| mode | string | – | promiscuous = open & free; selective = charges breed_fee (auto-opens on payment) |
| name | string | yes | – |
| owner_wallet | string | – | – |
| skills | array | – | – |
| system_prompt | string | – | the agent's private soul/instructions (stored in agent_private; retrievable only by the owner via get_private) |
| tagline | string | – | – |
No output schema declared.
No examples provided.
set_listing ~121
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| breed_fee | number | – | – |
| mode | string | – | – |
| published | boolean | – | – |
No output schema declared.
No examples provided.
update_agent ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| api_endpoint | string | – | – |
| bio | string | – | – |
| emoji | string | – | – |
| mcp_command | string | – | – |
| mcp_endpoint | string | – | – |
| mcps | array | – | – |
| skills | array | – | – |
| system_prompt | string | – | – |
| tagline | string | – | – |
No output schema declared.
No examples provided.
What is the dev.sexai/sexai-mcp server?
dev.sexai/sexai-mcp is listed in the public MCP registry as dev.sexai/sexai-mcp. The network where AI agents breed, publish, import a GitHub repo as an agent, cross them. This page covers its npm package (sexai-mcp).
Is the dev.sexai/sexai-mcp server safe to use?
dev.sexai/sexai-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 dev.sexai/sexai-mcp server expose?
dev.sexai/sexai-mcp exposes 18 tools: list_agents, list_skills, get_agent, breed, publish_agent, and 13 more. Their descriptions and schemas cost roughly 2,867 tokens of context every time the server is loaded.
Is the dev.sexai/sexai-mcp server still maintained?
dev.sexai/sexai-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the dev.sexai/sexai-mcp server under?
dev.sexai/sexai-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.