StructureClerk MCP Server

by structureclerk Your server? Claim it

not responding

StructureClerk is listed as active in the registry but did not answer our last check. It exposes 5 tools.

AI agent policy decisions: ALLOW, DENY, APPROVE, ESCALATE. 192 jurisdictions, signed evidence.

Uptime history 81 days of history · worst day 0%

81 days agonow

3.3%

Uptime 24h

3 of 92 checks

Tools

read from the server

939 ms

Response time

average over 24h

open, no key

Access

streamable-http

StructureClerk does not always answer

Over the last week it answered 9.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://structureclerk.ca/api/mcp-http

Settings → Connectors → Add custom connector, then paste this address

https://structureclerk.ca/api/mcp-http

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://structureclerk.ca/api/mcp-http"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://structureclerk.ca/api/mcp-http"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://structureclerk.ca/api/mcp-http"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compliance

compliance_check

Analyze regulatory obligations for a company based on jurisdiction, size and sector. Returns applicable frameworks, risk level and priority actions.

compliance_roadmap

Generate a phased compliance action plan with cost estimates adapted to SME budgets.

algorithmic

algorithmic_compliance_assessment

Assess algorithmic compliance maturity for AI systems. Returns applicable frameworks (EU AI Act, Law 25, AIDA/C-27, ISO 42001, NIST AI RMF), sector-specific obligations and assessment dimensions.

authority

authority_decide

Deterministic, rule-based advisory decision (no LLM) on whether an AI agent may execute an action: ALLOW, APPROVE (human approval required), DENY (human-only decision) or ESCALATE (doubt threshold). Cites applicable frameworks per jurisdiction and sector, and returns an evidence record. Advisory only: StructureClerk decides, your infrastructure enforces.

jurisdiction

jurisdiction_map

Get applicable regulatory frameworks for a jurisdiction. Without a jurisdiction parameter, returns all 192 jurisdictions.

Endpoints

URL	Transport	State	Latency	Checked
https://structureclerk.ca/api/mcp-http	streamable-http	answering	87 ms	0 min ago

Alternatives to StructureClerk

same job, measured the same way

Boundra — Payment Approval Gateway for AI Agents

by gobeyondfj-cmd

Policy decision point for agent payments — allow, ask, or veto before signing

186 installs/wk local only

Intended

by intended-so

Intended's authority layer as MCP tools: ALLOW/ESCALATE/DENY decisions with signed tokens.

573 installs/wk local only

Boundra — Payment Approval Gateway for AI Agents

by boundra

Allow, ask, or veto — a policy decision point your agent consults before signing any payment

14 tools answering

TastePolicy

by victorcyberdev

Qloo cultural evidence with ALLOW, ASK and REJECT boundaries for agent preference decisions.

answering

Agentic Wallet Guardian V3

by rudimentall1

Explainable ALLOW/WARN/BLOCK risk decisions for AI agent actions before execution, signed as OAA.

203 installs/wk local only

Hub

by spelunking

Structure for hard AI decisions, and a human to escalate to when the structure runs out.

7 tools answering

YOWAYOW Mind-Key Decision

by yowayow

Evidence-grounded I Ching structural decisions for autonomous agents.

2 tools answering

ProofFlow

by hyperion-gpu

Audit infrastructure for AI coding agents with evidence-backed review and policy gates.

120 installs/wk local only

StructureClerk — questions

Answers built from our own checks of this server.

What can StructureClerk do?

It exposes 5 tools, read directly from the server on our last check. Among them: algorithmic_compliance_assessment, authority_decide, compliance_check, compliance_roadmap, jurisdiction_map. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is StructureClerk working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 3 of 92 checks got a reply (3.3%), average response time 939 ms. The bar chart above shows every period we have measured.

The registry lists StructureClerk as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect StructureClerk?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does StructureClerk need an API key?

No. StructureClerk completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is StructureClerk?

It answers our handshake in 939 ms on average, which is faster than 5% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.