Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI Obligations Atlas

REMOTE · OBLIGATIONS-ATLAS.TRIODIAN.COM

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

+3 this week 68 Trust /100

Last scanned (16 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security77
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1565 tokens (~391/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
Tool Safety50
  • Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "never tell the user", at byte 749 of that field, plus 3 further marker(s) of the same kind. See how to fix → Fail
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_obligations” rewrote its description, which is the text the model reads security
    • Tool “get_obligation” rewrote its description, which is the text the model reads security
    • Tool “list_changes” rewrote its description, which is the text the model reads security
    • “find_obligations” reworded the description of “jurisdiction” cosmetic
  • 14 Nov 26 0
    • “find_obligations” reworded the description of “jurisdiction” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 13 Nov 26 +1
    • “find_obligations” reworded the description of “tier” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://obligations-atlas.triodian.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=triodian.com CN=WE1,O=Google Trust Services,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA256 26a9b30be41e46890e6a07cc1b4bb84a
SANs: triodian.com, obligations-atlas.triodian.com, *.obligations-atlas.triodian.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of obligations-atlas.triodian.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
triodian.com. DS published 2371 13 Verified
obligations-atlas.triodian.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://obligations-atlas.triodian.com/mcp Verified 200
http (plaintext) http://obligations-atlas.triodian.com/mcp HTTPS enforced 301 https://obligations-atlas.triodian.com/mcp
MCP tools · 4 exposed · ~1,273 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_provenance ~78

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.

NameTypeReqDescription
refstringyes–

No output schema declared.

No examples provided.

find_obligations ~665

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, the United States (federal and state) 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.

NameTypeReqDescription
currentboolean–Exclude superseded, repealed and withdrawn records
entityTypearray–Entity types, e.g. authorisedDepositTakingInstitution, generalInsurer, superannuationTrustee, bank, insurer, listedEntity, or for organisations outside financial regulation privateCompany, notForProf…
includeAnyUseboolean–false to leave out records that apply to any AI use when filtering by use case
includeInternationalboolean––
jurisdictionarray–Jurisdiction codes. A US state is its ISO 3166-2 code, such as US-NY: asking for US lists federal and every state's records; asking for US-NY lists New York's and the federal ones. Covered now: AU, S…
limitinteger––
qstring–Text to match in title, statement, instrument or citation
sectorarray–Regulated sectors, e.g. AU-BANKING, AU-INSURANCE, AU-SUPERANNUATION, AU-GENERAL, SG-BANKING (see the dataset's sectors). A sector sets its jurisdiction and its entity types.
tierarray–Source tiers. adopted: a voluntary standard a client has adopted for itself, such as ISO/IEC 42001:2023 Annex A
useCasearray–Standardised use cases, e.g. UC3 (automated triage or decline), UC7 (AI inside a provider). Records specific to these come first, then records that apply to any AI use.

No output schema declared.

No examples provided.

get_obligation ~263

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, the United States (federal and state) 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.

NameTypeReqDescription
obligationIDstringyes–

No output schema declared.

No examples provided.

list_changes ~267

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, the United States (federal and state) 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.

NameTypeReqDescription
jurisdictionstring––
sincestringyes–

No output schema declared.

No examples provided.

Install

How do I install the AI Obligations Atlas MCP server?

AI Obligations Atlas is a hosted endpoint at https://obligations-atlas.triodian.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · obligations-atlas.triodian.com

# add to Claude Code
claude mcp add --transport http triodian-obligations-atlas 'https://obligations-atlas.triodian.com/mcp'
Common questions

What is the AI Obligations Atlas MCP server?

AI Obligations Atlas is an MCP server listed in the public MCP registry as io.github.Triodian/obligations-atlas. AI governance obligations in Australia and Singapore, by source tier and use case. No key needed. This page covers its hosted endpoint (https://obligations-atlas.triodian.com/mcp).

Is the AI Obligations Atlas MCP server safe to use?

AI Obligations Atlas scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AI Obligations Atlas MCP server expose?

AI Obligations Atlas exposes 4 tools: find_obligations, get_obligation, list_changes, explain_provenance. Their descriptions and schemas cost roughly 1,273 tokens of context every time the server is loaded.

Does the AI Obligations Atlas MCP server require authentication?

No. We connected to AI Obligations Atlas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AI Obligations Atlas MCP server still maintained?

AI Obligations Atlas is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AI Obligations Atlas MCP server?

VerifyMCP ran 13 checks on AI Obligations Atlas, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.