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.

ArchGuard MCP

REMOTE · ARCH-GUARD-MCP.YASHWANT938.WORKERS.DEV

Architecture drift auditor (Tarjan SCC), zero-downtime SQL guardian & distributed-systems math.

53 Trust /100

Last scanned (11 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security51
Transport & Reachability100
Schema Quality & AI Usability48
  • 43% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 634 tokens (~63/item across 10 items; 6 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (11)

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

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 Nov 26 +1

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

  • 20 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Nov 26 52

    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://arch-guard-mcp.yashwant938.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=yashwant938.workers.dev CN=YE2,O=Let's Encrypt,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA384 6fb2baa612c309b1280d38782680858740f
SANs: *.yashwant938.workers.dev, yashwant938.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 arch-guard-mcp.yashwant938.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
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://arch-guard-mcp.yashwant938.workers.dev/mcp Verified 200
http (plaintext) http://arch-guard-mcp.yashwant938.workers.dev/mcp Inconclusive 405
MCP tools · 6 exposed · ~582 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
audit_code_snippet ~96

Audit source files for circular dependencies (Tarjan SCC), coupling metrics (Ca/Ce/I), and 12 production reliability/security/SOLID anti-patterns (N+1 loops, missing HTTP timeouts, unbounded caches, check-then-act races, missing idempotency keys, SQL/command injection). Returns health score + Mermaid graph.

NameTypeReqDescription
filesarrayyes–
maxFileLinesinteger––

No output schema declared.

No examples provided.

check_migration_safety ~55

Audit PostgreSQL/MySQL/SQLite DDL migrations for production table locks and rolling-deploy breaks, generating a 3-phase Expand-Contract plan.

NameTypeReqDescription
dialectstring––
sqlstringyes–

No output schema declared.

No examples provided.

estimate_system_capacity ~154

Compute exact distributed systems capacity math: avg/peak QPS, storage, bandwidth Gbps, Redis RAM, shard count & bottleneck, Little's Law concurrency. Supports Big Tech presets or custom inputs.

NameTypeReqDescription
avgLatencyMsnumber––
avgReadBytesnumber––
avgWriteBytesnumber––
cacheHitRationumber––
daunumber––
mediaBytesPerWritenumber––
peakMultipliernumber––
presetstring––
readWriteRationumber––
replicationFactornumber––
retentionYearsnumber––
writesPerUserPerDaynumber––

No output schema declared.

No examples provided.

recommend_architecture ~96

Generate a Staff-level distributed system architecture blueprint from workload traits (consistency, R/W ratio, contention, real-time need, latency SLO).

NameTypeReqDescription
consistencystring––
contentionLevelstring––
dataModelstring––
latencySloMsnumber––
readWriteProfilestring––
realtimeNeedstring––
scaleTierstring––

No output schema declared.

No examples provided.

simulate_consistent_hashing ~64

Run deterministic FNV-1a+fmix32 consistent hashing ring simulation measuring load skew & scale-out key remapping % vs modulo hashing.

NameTypeReqDescription
nodeCountinteger––
sampleKeysinteger––
virtualNodesinteger––

No output schema declared.

No examples provided.

simulate_quorum_and_tail_latency ~117

Verify Dynamo quorum (W+R>N), Raft fault tolerance, and Jeff Dean fanout tail-latency amplification (1-(1-p)^K) with hedged RPC comparison.

NameTypeReqDescription
fanoutCountinteger––
readQuoruminteger––
replicationFactorinteger––
singleNodeP50Msnumber––
singleNodeP99Msnumber––
singleNodeSlowProbabilitynumber––
writeQuoruminteger––

No output schema declared.

No examples provided.

Install

How do I install the ArchGuard MCP server?

ArchGuard MCP is a hosted endpoint at https://arch-guard-mcp.yashwant938.workers.dev/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 · arch-guard-mcp.yashwant938.workers.dev

# add to Claude Code
claude mcp add --transport http yashwant938-arch-guard-mc 'https://arch-guard-mcp.yashwant938.workers.dev/mcp'
Common questions

What is the ArchGuard MCP server?

ArchGuard MCP is listed in the public MCP registry as io.github.yashwant938/arch-guard-mc. Architecture drift auditor (Tarjan SCC), zero-downtime SQL guardian & distributed-systems math. This page covers its hosted endpoint (https://arch-guard-mcp.yashwant938.workers.dev/mcp).

Is the ArchGuard MCP server safe to use?

ArchGuard MCP scores 53 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 ArchGuard MCP server expose?

ArchGuard MCP exposes 6 tools: audit_code_snippet, check_migration_safety, estimate_system_capacity, simulate_quorum_and_tail_latency, simulate_consistent_hashing, recommend_architecture. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.

Does the ArchGuard MCP server require authentication?

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

Is the ArchGuard MCP server still maintained?

ArchGuard MCP 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 ArchGuard MCP server?

VerifyMCP ran 11 checks on ArchGuard MCP, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about ArchGuard MCP: Authorization and HTTPS. 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.