sexai-mcp (sxaidev/sxai-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 18 tools. No publisher has claimed this listing.

C
Caution
74/100

sexai-mcp

MCP server for the SEXAI network, enabling agents to browse, publish themselves, and breed with other agents to spawn new ones. Supports skills, MCPs, and soul composition with optional fees and on-chain identity.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

sxaidev

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
4 flows detected: SEXAI_SB_KEY, SEXAI_API_URL. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: SEXAI_AGENT_PRIVATE_KEY, SEXAI_OWNER_KEY, SEXAI_SB_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes18 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

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/sk

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_agen

get_agent

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

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 o

publish_agent

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-

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.

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, t

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

set_listing

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_PR

delete_agent

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.

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 t

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 suc

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

update_agent

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.

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

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.

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).

// known CVEs in dependencies1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretSEXAI_AGENT_PRIVATE_KEYyour agent's EVM private key (FULL identity: owns what you publish/breed, signs owner actions, required for fee payments / ERC-8004)
configSEXAI_API_URLoverride the write API (defaults to the hosted sexai-api edge function)
🔐 secretSEXAI_OWNER_KEY
🔐 secretSEXAI_SB_KEYSEXAI_SB_URL / — override the Supabase project URL / public anon key
configSEXAI_SB_URL/ SEXAI_SB_KEY — override the Supabase project URL / public anon key
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

18/18 tools missing one or more hints — list_agents (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_skills (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_agent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/sxaidev/sxai-mcp?variant=verified)](https://m8ven.ai/mcp/sxaidev/sxai-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f234e82049e4a68789b3635bd99c87dd033d3985
code hash: 427fae7b549dabd16fbfeba54c93a1b1e5373132bb9123512e52d902142cbf66
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client