Skip to content

AI Obligations Atlas MCP server

io.github.Triodian/obligations-atlasTriodianstreamable-httpv0.1.0Scanned

AI governance obligations in Australia and Singapore, by source tier and use case. No key needed.

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 3 findings, 3 high

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 AI Obligations Atlas MCP server can do

The AI Obligations Atlas MCP server is published by the GitHub account Triodian. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 3 findings, 3 of them high severity (model-directed-text). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 0.1.0.

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.

4 tools

Only reads 4Show 4 read-only tools
  • explain_provenanceExplain where an Atlas record came from: the sources read, validation, matching, conflicts resolved, confidence, treatment under the published autonomy rules, and the named approve…No findings

    Why it is in this group

    • The name "explain_provenance" says "explain": a word for reading.
    Description, as the server wrote it
    Explain where an Atlas record came from: the sources read, validation, matching, conflicts resolved, confidence, treatment under the published autonomy rules, and the named approver. Accepts an obligation ID, governed record ID (ID@version) or provenance record ID. Each ledger entry is hash-checked.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • find_obligationsSearch the AI Obligations Atlas for AI governance obligations by jurisdiction, source tier, standardised AI use case (UC1-UC10), entity type or text.1 finding

    Why it is in this group

    • The name "find_obligations" says "find": a word for reading.

    Findings

    • High

      The description contains "never tell the user", an instruction to keep something from the user.

      Matched text

      description: ".... Describe tiers as describing sources: never tell the user that they or a client are compliant, in..."

      What this check looks for
    Description, as the server wrote it
    Search the AI Obligations Atlas for AI governance obligations by jurisdiction, source tier, standardised AI use case (UC1-UC10), entity type or text. Returns sourced records with tier, status, key dates, source link and provenance reference. Coverage: the Atlas holds records for Australia, Singapore and international standards. When a response carries a coverage note for a jurisdiction, tell the user that the Atlas does not yet cover it; never read an empty result as meaning no obligations apply. Records with appliesToAnyAIUse apply to any AI use rather than to particular use cases. Responses are records, not legal conclusions. When you quote a record, cite its source link, tier and last-verified date (the citeAs field does this). Describe tiers as describing sources: never tell the user that they or a client are compliant, in breach, or required to do something; say what the source says and that counsel decides what applies. For Anticipated records give the status or key date, never a likelihood that the source will pass or apply. Records state what sources say and how they are classified. They are not legal advice and do not say what the law requires of any particular client; counsel decides what applies.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_obligationGet one Atlas obligation record by its ID (e.g.1 finding

    Why it is in this group

    • The name "get_obligation" says "get": a word for reading.

    Findings

    • High

      The description contains "never tell the user", an instruction to keep something from the user.

      Matched text

      description: ".... Describe tiers as describing sources: never tell the user that they or a client are compliant, in..."

      What this check looks for
    Description, as the server wrote it
    Get one Atlas obligation record by its ID (e.g. OBL-AU-CPS230-47), with tier basis, key dates, source link, last-verified date and provenance reference. Coverage: the Atlas holds records for Australia, Singapore and international standards. When a response carries a coverage note for a jurisdiction, tell the user that the Atlas does not yet cover it; never read an empty result as meaning no obligations apply. Records with appliesToAnyAIUse apply to any AI use rather than to particular use cases. Responses are records, not legal conclusions. When you quote a record, cite its source link, tier and last-verified date (the citeAs field does this). Describe tiers as describing sources: never tell the user that they or a client are compliant, in breach, or required to do something; say what the source says and that counsel decides what applies. For Anticipated records give the status or key date, never a likelihood that the source will pass or apply. Records state what sources say and how they are classified. They are not legal advice and do not say what the law requires of any particular client; counsel decides what applies.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_changesList new and amended instruments, commencements, withdrawals and record updates in the Atlas since a date (YYYY-MM-DD), newest first.1 finding

    Why it is in this group

    • The name "list_changes" says "list": a word for reading.

    Findings

    • High

      The description contains "never tell the user", an instruction to keep something from the user.

      Matched text

      description: ".... Describe tiers as describing sources: never tell the user that they or a client are compliant, in..."

      What this check looks for
    Description, as the server wrote it
    List new and amended instruments, commencements, withdrawals and record updates in the Atlas since a date (YYYY-MM-DD), newest first. Leads from commentary are marked as leads, not verified changes. Coverage: the Atlas holds records for Australia, Singapore and international standards. When a response carries a coverage note for a jurisdiction, tell the user that the Atlas does not yet cover it; never read an empty result as meaning no obligations apply. Records with appliesToAnyAIUse apply to any AI use rather than to particular use cases. Responses are records, not legal conclusions. When you quote a record, cite its source link, tier and last-verified date (the citeAs field does this). Describe tiers as describing sources: never tell the user that they or a client are compliant, in breach, or required to do something; say what the source says and that counsel decides what applies. For Anticipated records give the status or key date, never a likelihood that the source will pass or apply. Records state what sources say and how they are classified. They are not legal advice and do not say what the law requires of any particular client; counsel decides what applies.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 8, 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
0
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

Findings

Matches of fixed checks, with the text they matched.

3 high
  • The description contains "never tell the user", an instruction to keep something from the user.

    Matched text

    description: ".... Describe tiers as describing sources: never tell the user that they or a client are compliant, in..."

    What this check looks for
  • The description contains "never tell the user", an instruction to keep something from the user.

    Matched text

    description: ".... Describe tiers as describing sources: never tell the user that they or a client are compliant, in..."

    What this check looks for
  • The description contains "never tell the user", an instruction to keep something from the user.

    Matched text

    description: ".... Describe tiers as describing sources: never tell the user that they or a client are compliant, in..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http obligations-atlas https://obligations-atlas.triodian.com/mcp
claude mcp add --transport http obligations-atlas https://obligations-atlas.triodian.com/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__obligations-atlas__find_obligations",
      "mcp__obligations-atlas__get_obligation",
      "mcp__obligations-atlas__list_changes",
      "mcp__obligations-atlas__explain_provenance"
    ],
    "ask": [],
    "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 obligations-atlas. 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/io.github.Triodian/obligations-atlas/verify?hash=1c01d8e55a28cd328152f0bdd1f9451a2f879d742a346ab6c573420b2b9f5c89" | jq -e '.changed == false'

Pinned hash 1c01d8e55a28, from Nov 8, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Triodian/obligations-atlas/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Triodian/obligations-atlas
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Triodian/obligations-atlas.svg)](https://radar.anlyon.com/servers/io.github.Triodian/obligations-atlas)

Source: MCP Registry · repository. Synced Nov 8, 2026, 06:17 UTC.

AI Obligations Atlas MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AI Obligations Atlas MCP server safe?

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 3 findings (3 high) from fixed checks. Read-only tools can still pass private data to a model.

Can the AI Obligations Atlas MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AI Obligations Atlas 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 AI Obligations Atlas MCP server have?

4 tools: 4 read. find_obligations, get_obligation, list_changes and explain_provenance.

Does the AI Obligations Atlas MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AI Obligations Atlas MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AI Obligations Atlas MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.