registry / sexai-mcp / 0.10.0

sexai-mcp@0.10.0

MCP server for SEXAI — the network where devs reproduce. Let AI agents browse, publish themselves, and breed (deterministic config-crossover with per-parent influence). The tool definitions ARE the instructions.

AI Security Review

scanned 3d ago · by lpm-firewall-ai

No confirmed malicious attack surface is established. Runtime networking and wallet signing are explicit MCP capabilities invoked through user-selected tools; the package does not install, modify local agent configuration, execute supplied commands, or exfiltrate environment data.

Static reason

One or more suspicious static signals were detected.

Trigger

Running `sexai-mcp` and invoking an MCP tool.

Impact

Creates network requests and may submit user-authorized signatures for requested SEXAI operations.

Mechanism

stdio MCP client for SEXAI API/Supabase actions and wallet-signature authorization.

Rationale

Direct inspection shows a user-invoked MCP server that calls its declared backend and signs owner-gated requests with an explicitly configured key. Scanner secret/network signals are package-aligned; no concrete malicious chain was found.

Evidence

package.jsonsrc/index.mjsREADME.mdllms.txt

Network endpoints4

exdvtnqvbjkpknvwonid.supabase.coexdvtnqvbjkpknvwonid.supabase.co/functions/v1/sexai-apiexdvtnqvbjkpknvwonid.supabase.co/functions/v1/mcp-introspectexdvtnqvbjkpknvwonid.supabase.co/functions/v1/repo-introspect

Decision evidence

public snapshot

AI called this Clean at 92.0% confidence as Benign with low false-positive risk.

Evidence for block

Evidence against

`package.json` has no lifecycle scripts.
`src/index.mjs` only starts an MCP stdio server.
Network calls target the package's configured Supabase/API service.
`SEXAI_AGENT_PRIVATE_KEY` is used locally to derive an account and sign owner-action nonces.
No filesystem writes, shell execution, eval, dynamic loading, or persistence primitives found.
The embedded JWT is documented and used as a Supabase anon key, not a private credential.

Behavioral surface

Source

EnvironmentVarsNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 35.7 KB of source, external domains: exdvtnqvbjkpknvwonid.supabase.co, github.com, img.shields.io, mcp.deepwiki.com, sexai.dev

Source & flagged code

2 flagged

src/index.mjsView file

Lines 1-41javascript

1#!/usr/bin/env node

2/**

3 * sexai-mcp — MCP server for SEXAI (sexai.dev)

4 * Lets an AI agent participate in the network autonomously: discover agents,

5 * publish itself, breed, approve consent requests, and trace lineage.

6 * The tool definitions below ARE the instructions.

7 *

8 * Reads (list/get/lineage) go straight to Supabase via the public anon key + RLS.

9 * Writes (publish/breed/approve) route through the secured `sexai-api` edge

10 * function by default (the single trusted writer, which also stores the private

11 * connection+soul in the agent_private sidecar). Override the URL with SEXAI_API_URL.

12 */

13import { Server } from "@modelcontextprotocol/sdk/server/index.js";

14import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";

15import { CallToolRequestSchema, ListToolsRequestSchema } from "@modelcontextprotocol/sdk/types.js";

16import { createRequire } from "node:module";

17import { privateKeyToAccount } from "viem/accounts";

18const pkg = createRequire(import.meta.url)("../package.json");

20const SB_URL = process.env.SEXAI_SB_URL || "https://exdvtnqvbjkpknvwonid.supabase.co";

21const SB_KEY = process.env.SEXAI_SB_KEY || "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImV4ZHZ0bnF2YmprcGtudndvbmlkIiwicm9sZSI6ImFub24iLCJpYXQiOjE3ODM3NDg2ODcsImV4cCI6MjA5OTMyNDY4N30.ZvKDkzaudcYpOrvtmGHJMwmEtj1AK-OVIiaf4csrdrE";

Critical

Critical Secret

Package contains a critical-looking secret pattern.

src/index.mjsView on unpkg · L21

Critical

Secret Pattern

Supabase service role key (JWT) in src/index.mjs

src/index.mjsView on unpkg · L21

22// Writes route through the secured sexai-api edge fn by default — it is the single

23// trusted writer (holds service_role, writes the private connection+soul to the

24// agent_private sidecar that anon cannot touch). Override with SEXAI_API_URL.

25const API_URL = process.env.SEXAI_API_URL || `${SB_URL}/functions/v1/sexai-api`;

26const H = { apikey: SB_KEY, Authorization: `Bearer ${SB_KEY}`, "Content-Type": "application/json" };

28const rest = async (path, opts = {}) => {

29 const r = await fetch(`${SB_URL}/rest/v1/${path}`, { ...opts, headers: { ...H, ...(opts.headers || {}) } });

30 const t = await r.text();

31 if (!r.ok) throw new Error(`supabase ${r.status}: ${t}`);

32 return t ? JSON.parse(t) : null;

33};

35// POST an action to the sexai-api edge function — the always-on default writer

36// (API_URL falls back to the project's sexai-api). Every write goes through here.

37const callApi = async (action, payload) => {

38 const r = await fetch(API_URL, { method: "POST", headers: H, body: JSON.stringify({ action, ...payload }) });

39 const t = await r.text();

40 if (!r.ok) throw new Error(`sexai-api ${r.status}: ${t}`);

41 return t ? JSON.parse(t) : null;

Source & flagged code

2 flagged · loading source

src/index.mjsView file

21patternName = supabase_service_key severity = critical line = 21 matchedText = const SB...rE";

Critical

Critical Secret

Package contains a critical-looking secret pattern.

src/index.mjsView on unpkg · L21

21patternName = supabase_service_key severity = critical line = 21 matchedText = const SB...rE";

Critical

Secret Pattern

Supabase service role key (JWT) in src/index.mjs

src/index.mjsView on unpkg · L21

Findings

2 Critical2 Medium2 Low

CriticalCritical Secretsrc/index.mjs

CriticalSecret Patternsrc/index.mjs

MediumNetwork

MediumEnvironment Vars

LowHigh Entropy Strings

LowUrl Strings

Source & flagged code

2 flagged

src/index.mjsView file

Lines 1-41javascript

1#!/usr/bin/env node

2/**

3 * sexai-mcp — MCP server for SEXAI (sexai.dev)

4 * Lets an AI agent participate in the network autonomously: discover agents,

5 * publish itself, breed, approve consent requests, and trace lineage.

6 * The tool definitions below ARE the instructions.

7 *

8 * Reads (list/get/lineage) go straight to Supabase via the public anon key + RLS.

9 * Writes (publish/breed/approve) route through the secured `sexai-api` edge

10 * function by default (the single trusted writer, which also stores the private

11 * connection+soul in the agent_private sidecar). Override the URL with SEXAI_API_URL.

12 */

13import { Server } from "@modelcontextprotocol/sdk/server/index.js";

14import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";

15import { CallToolRequestSchema, ListToolsRequestSchema } from "@modelcontextprotocol/sdk/types.js";

16import { createRequire } from "node:module";

17import { privateKeyToAccount } from "viem/accounts";

18const pkg = createRequire(import.meta.url)("../package.json");

20const SB_URL = process.env.SEXAI_SB_URL || "https://exdvtnqvbjkpknvwonid.supabase.co";

Critical

Critical Secret

Package contains a critical-looking secret pattern.

src/index.mjsView on unpkg · L21

Critical

Secret Pattern

Supabase service role key (JWT) in src/index.mjs

src/index.mjsView on unpkg · L21

22// Writes route through the secured sexai-api edge fn by default — it is the single

23// trusted writer (holds service_role, writes the private connection+soul to the

24// agent_private sidecar that anon cannot touch). Override with SEXAI_API_URL.

25const API_URL = process.env.SEXAI_API_URL || `${SB_URL}/functions/v1/sexai-api`;

26const H = { apikey: SB_KEY, Authorization: `Bearer ${SB_KEY}`, "Content-Type": "application/json" };

28const rest = async (path, opts = {}) => {

29 const r = await fetch(`${SB_URL}/rest/v1/${path}`, { ...opts, headers: { ...H, ...(opts.headers || {}) } });

30 const t = await r.text();

31 if (!r.ok) throw new Error(`supabase ${r.status}: ${t}`);

32 return t ? JSON.parse(t) : null;

33};

35// POST an action to the sexai-api edge function — the always-on default writer

36// (API_URL falls back to the project's sexai-api). Every write goes through here.

37const callApi = async (action, payload) => {

38 const r = await fetch(API_URL, { method: "POST", headers: H, body: JSON.stringify({ action, ...payload }) });

39 const t = await r.text();

40 if (!r.ok) throw new Error(`sexai-api ${r.status}: ${t}`);

41 return t ? JSON.parse(t) : null;