TwinEthos Lite MCP server
com.twinethos/litetwinethos.comstreamable-httpv1.0.1Scanned
Which AI laws apply to an AI feature in a market: cited provisions, who they cover, dates, guards.
5 tools: 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the TwinEthos Lite MCP server can do
The TwinEthos Lite MCP server is published by twinethos.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: plan_guards, coming_into_force and recently_in_force), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 3Claude Code: ask
coming_into_forceBinding AI-law obligations that start applying soon, soonest first, with citation, official link and the guard in one sentence.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Binding AI-law obligations that start applying soon, soonest first, with citation, official link and the guard in one sentence. When to use: someone asks what is coming, what to prepare for, or which AI laws take effect next year. For dates already passed, use recently_in_force. Features and markets narrow the list (each left out covers everything); within_days sets how far ahead to look. Each entry's guard is the change to make in the application (a notice, a check, a human review step). Dates can change; returns at most 10, and `total` says how many there are. Limits: informational data, not legal advice.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
plan_guardsThe few guards that address the most rules for these AI features and markets, ranked: each guard in one sentence (a guard is a change to make in the application's code or settings,…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The few guards that address the most rules for these AI features and markets, ranked: each guard in one sentence (a guard is a change to make in the application's code or settings, such as a notice, a check or a human review step), how many rules it addresses by lane, where binding law on it applies, and up to three example rule ids. When to use: someone asks what to build first, or how to cover several markets at once. Ranked by the markets with binding law in force, then law coming, then rules addressed. Leave out features or markets to rank over all of them. Returns at most 5 guards; pass an example rule_id to explain_rule for detail. Limits: informational data, not legal advice.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
recently_in_forceBinding AI-law obligations that started applying recently, newest first, with citation, official link and the guard in one sentence.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Binding AI-law obligations that started applying recently, newest first, with citation, official link and the guard in one sentence. When to use: someone asks what took effect recently, when the most recent AI law in a market started applying, or what changed this year. For dates ahead, use coming_into_force. Features and markets narrow the list (each left out covers everything); within_days sets how far back to look. Each date is when a duty started applying, not when the law was enacted; a later phase of a law already in force is marked as one. Each entry's guard is the change to make in the application (a notice, a check, a human review step). Returns at most 10, and `total` says how many there are. Limits: informational data, not legal advice.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
Only reads 2Show 2 read-only tools
explain_ruleOne 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…No findings
Why it is in this group
- The name "explain_rule" says "explain": a word for reading.
Description, as the server wrote it 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 (a guard is the change to make in the application's code or settings, such as a notice, a check or a human review step, that addresses the rule's duty). When to use: after search_laws, coming_into_force, recently_in_force or plan_guards, with a rule_id one of them returned, or when someone names a rule id. An unknown id returns an error naming search_laws. It never returns the official text itself. Limits: informational data, not legal advice.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
search_lawsFind the AI-law rules (EU AI Act, US state AI laws, China, Korea and other markets) that apply to an AI feature in a market, each with its cited provision and official link.No findings
Why it is in this group
- The name "search_laws" says "search": a word for reading.
Description, as the server wrote it Find the AI-law rules (EU AI Act, US state AI laws, China, Korea and other markets) that apply to an AI feature in a market, each with its cited provision and official link. When to use: someone asks which laws, regulations or standards apply to what they are building, or where a kind of AI feature is regulated (chatbot disclosure, hiring and employment decisions, credit or insurance decisions, deepfakes and digital replicas, companion chatbots and minors, AI-generated content labels, training data). The filters combine: a rule must cover one of the markets and one of the patterns given, and match the words if any are given; each filter left out matches everything. Returns at most 10 rules, most relevant first (the words matched, then the rules specific to the features, then binding law in force), each with its lane, citation, official link, applies-from date and its page in the TwinEthos explorer. It does not sort by date: use coming_into_force or recently_in_force for dates. Limits: informational data, not legal advice.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.twinethos.com/lite/mcp: tools/list returned 5 tools to an anonymous client, including plan_guards (write), coming_into_force (write), recently_in_force (write)
Posture changes
- Nov 11, 2026
- Tools that change things, listed without credentials: 2 to 3
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:coming_into_forceChanges thingsdescriptioninputSchema
- Changed:explain_ruleOnly readsdescriptioninputSchema
- Changed:plan_guardsChanges thingsdescriptioninputSchema
- Changed:recently_in_forceChanges thingsdescriptioninputSchema
- Changed:search_lawsOnly readsdescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Tools1 added, 4 changed.+1 added~4 changedView diff
- Added:recently_in_forceChanges things
- Changed:coming_into_forceChanges thingsdescription
- Changed:explain_ruleOnly readsdescription
- Changed:plan_guardsChanges thingsdescription
- Changed:search_lawsOnly readsdescription
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http lite https://api.twinethos.com/lite/mcpclaude mcp add --transport http lite https://api.twinethos.com/lite/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__lite__search_laws",
"mcp__lite__explain_rule"
],
"ask": [
"mcp__lite__plan_guards",
"mcp__lite__coming_into_force",
"mcp__lite__recently_in_force"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lite. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.twinethos/lite/verify?hash=26aa1f75adcf8401ab36df8827ddef4db8f194374b44aba7fb0e22017652f64c" | jq -e '.changed == false'Pinned hash 26aa1f75adcf, from Nov 18, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.twinethos/lite/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.twinethos/lite)Source: MCP Registry. Synced Nov 4, 2026, 16:17 UTC.
TwinEthos Lite MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TwinEthos Lite MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the TwinEthos Lite MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TwinEthos Lite MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the TwinEthos Lite MCP server have?
- 5 tools: 3 write, 2 read. plan_guards, coming_into_force, recently_in_force, search_laws and explain_rule.
Does the TwinEthos Lite MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the TwinEthos Lite MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TwinEthos Lite MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.