MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Other

TwinEthos Lite

Which AI laws apply to an AI feature in a market: cited provisions, who they cover, dates, guards.

Checks passed
13 / 22

1 failed · 8 not measured

Median response
330 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
5

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 330 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name TwinEthos Lite.

  • Pass
    Lists tools

    tools/list returned 5 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 330 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 330 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    16 of 16 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-04T15:45:46.086095Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using TwinEthos Lite

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http twinethos-lite https://api.twinethos.com/lite/mcp

Capabilities

Tools 5

coming_into_force

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.

Discovered
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 (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.

Discovered
plan_guards

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.

Discovered
recently_in_force

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.

Discovered
search_laws

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected330 ms5