Compliance Tools
REMOTE · API.TIMZININ.COM · SCANNED SEP 21
Pay-per-call compliance lead scanners with free MCP discovery and x402 payments.
Available components
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 575 tokens (~191/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Compliance Tools MCP server?
Compliance Tools is a hosted endpoint at https://api.timzinin.com/mcp/compliance-tools, 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 · api.timzinin.com
claude mcp add --transport http com-timzinin-api-compliance-tools 'https://api.timzinin.com/mcp/compliance-tools'
{
"mcpServers": {
"com-timzinin-api-compliance-tools": {
"url": "https://api.timzinin.com/mcp/compliance-tools"
}
}
} {
"servers": {
"com-timzinin-api-compliance-tools": {
"type": "http",
"url": "https://api.timzinin.com/mcp/compliance-tools"
}
}
} [mcp_servers.com-timzinin-api-compliance-tools] url = "https://api.timzinin.com/mcp/compliance-tools"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-timzinin-api-compliance-tools": {
"type": "remote",
"url": "https://api.timzinin.com/mcp/compliance-tools",
"enabled": true
}
}
} openclaw mcp add com-timzinin-api-compliance-tools --url 'https://api.timzinin.com/mcp/compliance-tools' --transport streamable-http
mcp_servers:
com-timzinin-api-compliance-tools:
url: "https://api.timzinin.com/mcp/compliance-tools" {
"McpServers": {
"com-timzinin-api-compliance-tools": {
"Transport": "http",
"Url": "https://api.timzinin.com/mcp/compliance-tools"
}
}
} assistant mcp add com-timzinin-api-compliance-tools -t streamable-http -u 'https://api.timzinin.com/mcp/compliance-tools'
{
"mcpServers": {
"com-timzinin-api-compliance-tools": {
"type": "http",
"url": "https://api.timzinin.com/mcp/compliance-tools"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 0
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Tool “eu-accessibility-privacy-lead-scanner” changed its title: EU Accessibility Privacy Lead Scanner cosmetic
- Tool “eu-ai-act-transparency-lead-scanner” changed its title: EU AI Act Transparency Lead Scanner cosmetic
- Tool “pricing_info” changed its title: Pricing — Compliance Tools cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- Schema quality: unverified → good ▲ functional
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 Sept 2026 · Probed https://api.timzinin.com/mcp/compliance-tools
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.timzinin.com | CN=YE1,O=Let's Encrypt,C=US | 27 Jul 2026 | 25 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5ef393ac3b7ccb852f589ba8f412cb7232f |
| SANs: api.timzinin.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.timzinin.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| timzinin.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.timzinin.com/mcp/compliance-tools | Verified | 200 | |
| http (plaintext) | http://api.timzinin.com/mcp/compliance-tools | HTTPS enforced | 301 | https://api.timzinin.com/mcp/compliance-tools |
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 →
eu-accessibility-privacy-lead-scanner EU Accessibility Privacy Lead Scanner ~176
BYOD compliance scanner for observed accessibility and privacy exposure signals on a submitted URL. Deterministic, robots-aware, no LLMs, no legal verdicts. — $0.05/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| detailLevel | string | – | compact for summaries, evidence for selectors and excerpts. |
| freshnessMinutes | integer | – | Use cached useful reports only if they are this fresh or newer. |
| maxResults | integer | – | Maximum number of useful rows to deliver. |
| requestId | string | yes | Stable idempotency key for this semantic input. |
| schemaVersion | string | yes | Input schema version. Must equal 1.0. |
| urls | array | yes | Submitted absolute HTTP(S) URLs to audit. No discovery, no crawling beyond the page itself. |
No output schema declared.
No examples provided.
eu-ai-act-transparency-lead-scanner EU AI Act Transparency Lead Scanner ~174
BYOD compliance scanner for observed AI transparency signals on a submitted URL. Deterministic, robots-aware, no LLMs, no legal verdicts. — $0.05/call, x402 (USDC on base).
| Name | Type | Req | Description |
|---|---|---|---|
| detailLevel | string | – | compact for summaries, evidence for selectors and excerpts. |
| freshnessMinutes | integer | – | Use cached useful reports only if they are this fresh or newer. |
| maxResults | integer | – | Maximum number of useful rows to deliver. |
| requestId | string | yes | Stable idempotency key for this semantic input. |
| schemaVersion | string | yes | Input schema version. Must equal 1.0. |
| urls | array | yes | Submitted absolute HTTP(S) URLs to audit. No discovery, no crawling beyond the page itself. |
No output schema declared.
No examples provided.
pricing_info Pricing — Compliance Tools ~44
Free — list every paid tool in the 'compliance-tools' bundle with its price, payTo address and network. Call this first if you don't have a wallet ready yet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Compliance Tools MCP server?
Compliance Tools is an MCP server listed in the public MCP registry as com.timzinin.api/compliance-tools. Pay-per-call compliance lead scanners with free MCP discovery and x402 payments. This page covers its hosted endpoint (https://api.timzinin.com/mcp/compliance-tools).
Is the Compliance Tools MCP server safe to use?
Compliance Tools scores 83 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 Compliance Tools MCP server expose?
Compliance Tools exposes 3 tools: pricing_info, eu-accessibility-privacy-lead-scanner, eu-ai-act-transparency-lead-scanner. Their descriptions and schemas cost roughly 394 tokens of context every time the server is loaded.
Does the Compliance Tools MCP server require authentication?
No. We connected to Compliance Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Compliance Tools MCP server still maintained?
Compliance Tools is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.