← Registry

AI & Machine Learning

twinethos.com

Provides AI-law compliance tools to search applicable rules, explain obligations, plan safeguards, and track upcoming binding obligations for AI features across markets.

1 endpoint4 known toolsFirst detected November 3, 2026Last detected November 3, 2026

ENDPOINT 1

https://api.twinethos.com/lite/mcp

No auth detected

MCP server metadata

Name
TwinEthos Lite
Version
1.0.0
Capabilities
promptsresourcestools
Server instructions

TwinEthos Lite: AI-law rules anchored to official text, for conversations about building AI features. Use it when someone asks which laws apply to an AI feature (a chatbot, an agent, AI decisions about people, generated media, recommendations, retrieval over documents) in a market, what a law requires, when it starts applying, or what to build to address it. Tools: search_laws (find rules by market and feature), explain_rule (one rule: who it applies to, dates, citation, the guard), plan_guards (the few guards that address the most rules), coming_into_force (dates ahead). Features are these codes: chat, rag, agentic, decision_pipeline, content_generation, classification, recommendation, embeddings. Markets are codes such as EU, US-CA, US-CO; US matches every state. Cite the provision and link the official source; say the lane (binding law in force, law not yet in force, standard, or TwinEthos recommendation, which is opinion, not law). Never say a guard makes an app compliant. Always relay the notice. TwinEthos Lite (free, no sign-up) covers which AI laws, regulations and standards apply to an AI feature in a market, the exact provision with its official link, who each duty applies to, when it applies, and the guard to add, in short answers. An API key is needed for code detectors, the full review checklist, bulk data and the coding-agent workflow: request MCP access at https://www.twinethos.com/docs/quickstart/#request. Answers are capped at 10 results, and calls are rate limited.

Known tools 4

search_laws

Find the AI-law rules that apply to an AI feature in a market.

Inferred read-only
explain_rule

One rule in plain terms: what it requires (TwinEthos's summary), who it applies to and the uses it excludes, its dates, the exact citations with their official links, and the guard to add in one sentence.

Inferred read-only
plan_guards

The few guards that address the most rules for these AI features and markets, ranked: each guard in one sentence, how many rules it addresses by lane, and where binding law on it applies.

Inferred read-only
coming_into_force

Binding AI-law obligations that start applying soon, by date, with citation, official link and the guard in one sentence.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.twinethos-lite]
url = "https://api.twinethos.com/lite/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "twinethos-lite": {
      "type": "http",
      "url": "https://api.twinethos.com/lite/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: twinethos-lite
Remote MCP URL: https://api.twinethos.com/lite/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "twinethos-lite": {
      "url": "https://api.twinethos.com/lite/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "twinethos-lite": {
      "type": "http",
      "url": "https://api.twinethos.com/lite/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "twinethos-lite",
  "transport": "streamable-http",
  "url": "https://api.twinethos.com/lite/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.