DJZS Trust MCP
REMOTE · MCP.DJZS.AI · SCANNED SEP 20
Deterministic pre-execution audit for trading agents. PASS/WAIT/FAIL, reproducible verdict_hash.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1096 tokens (~274/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 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 4 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 DJZS Trust MCP server?
DJZS Trust MCP is a hosted endpoint at https://mcp.djzs.ai/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 · mcp.djzs.ai
claude mcp add --transport http ai-djzs-trust-mcp 'https://mcp.djzs.ai/mcp'
{
"mcpServers": {
"ai-djzs-trust-mcp": {
"url": "https://mcp.djzs.ai/mcp"
}
}
} {
"servers": {
"ai-djzs-trust-mcp": {
"type": "http",
"url": "https://mcp.djzs.ai/mcp"
}
}
} [mcp_servers.ai-djzs-trust-mcp] url = "https://mcp.djzs.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-djzs-trust-mcp": {
"type": "remote",
"url": "https://mcp.djzs.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-djzs-trust-mcp --url 'https://mcp.djzs.ai/mcp' --transport streamable-http
mcp_servers:
ai-djzs-trust-mcp:
url: "https://mcp.djzs.ai/mcp" {
"McpServers": {
"ai-djzs-trust-mcp": {
"Transport": "http",
"Url": "https://mcp.djzs.ai/mcp"
}
}
} assistant mcp add ai-djzs-trust-mcp -t streamable-http -u 'https://mcp.djzs.ai/mcp'
{
"mcpServers": {
"ai-djzs-trust-mcp": {
"type": "http",
"url": "https://mcp.djzs.ai/mcp"
}
}
} 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.
- 14 Sept 26 −1
- Tool “query_agent_trust” rewrote its description, which is the text the model reads security
- Schema quality: 208 → 274 ▼ functional
- “verify_perp_trade” added an optional parameter “target_system_signature” cosmetic
- “verify_perp_trade” added an optional parameter “target_system_subject” cosmetic
- “verify_pm_trade” added an optional parameter “target_system_signature” cosmetic
- “verify_pm_trade” added an optional parameter “target_system_subject” cosmetic
- “verify_perp_trade” reworded the description of “target_system” cosmetic
- “verify_pm_trade” reworded the description of “target_system” cosmetic
- 9 Sept 26 0
- Schema quality: 600 → 834 ▼ functional
- New tool “verify_perp_trade” functional
- 30 Aug 26 −1
- Tool “verify_pm_trade” rewrote its description, which is the text the model reads security
- Schema quality: 164 → 200 ▼ functional
- Tool “verify_pm_trade” changed its title: Verify Prediction-Market Trade Thesis (DJZS pre-execution audit) cosmetic
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 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.
- 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
- 31 Jul 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
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 20 Sept 2026 · Probed https://mcp.djzs.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=djzs.ai | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3a3a59e89e723c4713ca6babec427087 |
| SANs: djzs.ai, mcp.djzs.ai, *.mcp.djzs.ai | ||||||
| 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 insecure
Validation of mcp.djzs.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| djzs.ai. | 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://mcp.djzs.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.djzs.ai/mcp | HTTPS enforced | 301 | https://mcp.djzs.ai/mcp |
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 →
query_agent_trust Query DJZS Agent Trust Score ~222
Query an agent's DJZS trust score, aggregated on-chain (Base mainnet) from its audit history and indexed via the DJZS subgraph. USE BEFORE delegating work, releasing escrow, or executing agent transactions. Returns scored_audits, pass/fail counts, the raw fail rate, and a Wilson 95% lower bound on it, plus latest verdict/risk and DJZS-S01/DJZS-X01 flag counts. WAIT verdicts are abstentions: they are excluded from BOTH the numerator and the denominator of the fail rate and are reported separately as wait_count. Below 10 scored audits the tool returns INSUFFICIENT_HISTORY and NO rate - a 0-of-0 record is not evidence of reliability and must not compare as better than a 3-of-50. This tool returns evidence, not a decision: it applies no threshold and emits no HALT. Interpreting the bound against your own risk tolerance is the caller's job.
| Name | Type | Req | Description |
|---|---|---|---|
| agentAddress | string | yes | Agent wallet address (0x-prefixed) |
No output schema declared.
No examples provided.
query_pol_certificates Query DJZS ProofOfLogic Certificates ~191
Query immutable ProofOfLogic certificates stored on Irys Datachain by DJZS Protocol. USE THIS TOOL when you need to verify audit history for an agent or project before delegating work, check FAIL verdicts, or retrieve certificates by Irys tx ID. DO NOT use for on-chain trust scores — use query_agent_trust for those.
| Name | Type | Req | Description |
|---|---|---|---|
| from_ms | integer | – | Window start (epoch ms). Default path auto-narrows (14d then 3d) to stay under the mainnet index timeout; pass an explicit value to reach older certificates (used as-is). |
| limit | number | – | Number of results |
| targetSystem | string | – | Project name or wallet address |
| tier | string | – | Filter by tier |
| to_ms | integer | – | Window end (epoch ms). Defaults to now + 1h. |
| verdict | string | – | Filter by verdict |
No output schema declared.
No examples provided.
verify_perp_trade Verify Perpetual / Spot Trade Thesis (DJZS pre-execution audit) ~317
Deterministic pre-execution audit of a perpetual or spot TRADE thesis (direction, size, leverage, entry, stop, target, venue, and the REASON), run before capital is committed. USE THIS TOOL before opening, sizing, or increasing any perpetual or spot position. Returns PASS / WAIT / FAIL with a reproducible verdict hash. A position stated with no thesis FAILS (DJZS-S01); an unbounded position FAILS (DJZS-X01); an unresolvable stop or thesis WAITs. Prediction-market bets are refused here (use verify_pm_trade) and are not charged. Price 2.00 USDC per audit on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | – | Optional agent wallet (0x). If set, this audit updates that agent's on-chain DJZS trust score |
| intent | string | yes | Free-text perpetual or spot trade thesis to audit: direction, size, leverage, entry, stop, target, venue, and the REASON |
| target_system | string | – | Optional agent/project identifier. Written to the certificate ONLY with a matching target_system_subject + target_system_signature; unsigned values are DISCARDED, not stored |
| target_system_signature | string | – | EIP-191 personal_sign over "DJZS-TSC-1 target-system claim\nsubject: <lowercased subject>\ntarget_system: <value>" |
| target_system_subject | string | – | Address that signed the target_system claim. Must be the address that recovers from target_system_signature |
No output schema declared.
No examples provided.
verify_pm_trade Verify Prediction-Market Trade Thesis (DJZS pre-execution audit) ~366
Deterministic pre-execution audit of a prediction-market trade thesis, run before capital is committed. USE THIS TOOL before opening, sizing, or increasing any prediction-market position, and whenever a user or an upstream agent asks whether a thesis is sound, carries a falsification condition, or has a sourced probability basis. Audits against the calibrated DJZS-M taxonomy (M01 narrative/resolution gap, M02 falsification absent, M03 probability unsourced, M04 consensus-as-edge advisory) and returns PASS->PROCEED, WAIT->HALT, or FAIL with the flagged defects and a reproducible verdict_hash. DO NOT use to retrieve past verdicts or certificates - use query_pol_certificates for those. DO NOT use for an agent's historical trust score - use query_agent_trust for that. DO NOT use for spot, perpetuals, or equities: out-of-scope submissions are refused WITHOUT CHARGE. Audit before act. Paid tool: 2 USDC per audit via x402 on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | – | Optional agent wallet (0x). If set, this audit updates that agent's on-chain DJZS trust score |
| intent | string | yes | Free-text prediction-market trade thesis to audit |
| target_system | string | – | Optional agent/project identifier. Written to the certificate ONLY with a matching target_system_subject + target_system_signature; unsigned values are DISCARDED, not stored |
| target_system_signature | string | – | EIP-191 personal_sign over "DJZS-TSC-1 target-system claim\nsubject: <lowercased subject>\ntarget_system: <value>" |
| target_system_subject | string | – | Address that signed the target_system claim. Must be the address that recovers from target_system_signature |
No output schema declared.
No examples provided.
What is the DJZS Trust MCP server?
DJZS Trust MCP is listed in the public MCP registry as ai.djzs/trust-mcp. Deterministic pre-execution audit for trading agents. PASS/WAIT/FAIL, reproducible verdict_hash. This page covers its hosted endpoint (https://mcp.djzs.ai/mcp).
Is the DJZS Trust MCP server safe to use?
DJZS Trust MCP scores 76 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 DJZS Trust MCP server expose?
DJZS Trust MCP exposes 4 tools: query_pol_certificates, query_agent_trust, verify_pm_trade, verify_perp_trade. Their descriptions and schemas cost roughly 1,096 tokens of context every time the server is loaded.
Does the DJZS Trust MCP server require authentication?
No. We connected to DJZS Trust MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DJZS Trust MCP server still maintained?
DJZS Trust MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.