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.

CliDeck MCP — Network Knowledge

REMOTE · MCP.CLIDECK.COM · SCANNED SEP 28

Free verified network knowledge for AI agents: deterministic answers, honest unknowns.

Available components

+3 this week 70 Trust /100
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 Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 834 tokens (~49/item across 17 items; 17 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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
Install

How do I install the CliDeck MCP — Network Knowledge server?

CliDeck MCP — Network Knowledge is a hosted endpoint at https://mcp.clideck.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 · mcp.clideck.com

# add to Claude Code
claude mcp add --transport http com-clideck-network-knowledge 'https://mcp.clideck.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-clideck-network-knowledge": {
      "url": "https://mcp.clideck.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-clideck-network-knowledge": {
      "type": "http",
      "url": "https://mcp.clideck.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-clideck-network-knowledge]
url = "https://mcp.clideck.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-clideck-network-knowledge": {
      "type": "remote",
      "url": "https://mcp.clideck.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-clideck-network-knowledge --url 'https://mcp.clideck.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-clideck-network-knowledge:
    url: "https://mcp.clideck.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-clideck-network-knowledge": {
      "Transport": "http",
      "Url": "https://mcp.clideck.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-clideck-network-knowledge -t streamable-http -u 'https://mcp.clideck.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-clideck-network-knowledge": {
      "type": "http",
      "url": "https://mcp.clideck.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 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
  • 27 Sept 26 +1

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

  • 25 Sept 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
  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 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.

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 28 Sept 2026 · Probed https://mcp.clideck.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=clideck.com CN=WE1,O=Google Trust Services,C=US 1 Aug 2026 30 Oct 2026 ECDSA 256 ECDSA-SHA256 add64616baad811e0ecfc33807ac87ed
SANs: clideck.com, *.clideck.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 insecure

Validation of mcp.clideck.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
clideck.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
Header Value
strict-transport-security max-age=15552000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer
permissions-policy tools=(self)

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.clideck.com/mcp Verified 200
http (plaintext) http://mcp.clideck.com/mcp Inconclusive 406
MCP tools · 17 exposed · ~834 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
advise_network_upgrade ~67

Return exact-model, exact-version upgrade prerequisites, risks, checks, and rollback without downloading software.

NameTypeReqDescription
current_versionstringyes–
enabled_featuresarray––
modelstringyes–
operating_systemstring––
target_versionstringyes–
NameTypeReqDescription
applicabilityobjectyes–
assuranceobjectyes–
breaking_changesarrayyes–
limitationsarrayyes–
next_actionstringyes–
prerequisitesarrayyes–
procedurearrayyes–
reload_expected–yes–
rollbackarrayyes–
security_advisoriesarrayyes–
statusstringyes–
verificationarrayyes–

No examples provided.

analyze_device_snapshot ~58

Detect vendor, model, operating system, and version from bounded CLI output while redacting sensitive values. Input is not stored.

NameTypeReqDescription
redaction_profilestring––
snapshotstringyes–
snapshot_typestring––
NameTypeReqDescription
context–yes–
limitationsarrayyes–
redactionsarrayyes–
retentionstringyes–
sanitized_snapshotstringyes–
snapshot_typestringyes–

No examples provided.

analyze_network_path ~56

Build a bounded topology and packet-path graph from supplied CDP, LLDP, route, and traceroute outputs without storing them.

NameTypeReqDescription
destinationstring––
snapshotsarrayyes–
sourcestring––
NameTypeReqDescription
edgesarrayyes–
findingsarrayyes–
limitationsarrayyes–
nodesarrayyes–
parse_diagnosticsarrayyes–
pathsarrayyes–
probable_fault_domain–yes–
retentionstringyes–
unparsed_inputsarrayyes–

No examples provided.

cancel_expert_task ~33

Cancel a non-terminal expert task.

NameTypeReqDescription
access_tokenstring––
task_idstringyes–
NameTypeReqDescription
answer–yes–
created_atstringyes–
expires_atstringyes–
failure–yes–
input_request–yes–
milestonesarrayyes–
poll_after_msintegeryes–
progress_percentintegeryes–
published_release_sequence–yes–
stagestringyes–
statusstringyes–
task_idstringyes–

No examples provided.

continue_expert_task ~42

Provide bounded additional input requested by the researcher.

NameTypeReqDescription
access_tokenstring––
messagestringyes–
task_idstringyes–
NameTypeReqDescription
answer–yes–
created_atstringyes–
expires_atstringyes–
failure–yes–
input_request–yes–
milestonesarrayyes–
poll_after_msintegeryes–
progress_percentintegeryes–
published_release_sequence–yes–
stagestringyes–
statusstringyes–
task_idstringyes–

No examples provided.

describe_knowledge_domain ~31

Return the context and public-record contracts for one installed knowledge domain.

NameTypeReqDescription
domain_idstringyes–
NameTypeReqDescription
manifestobjectyes–
schemasobjectyes–

No examples provided.

get_expert_task ~38

Poll an expert research task by opaque ID and access token.

NameTypeReqDescription
access_tokenstring––
task_idstringyes–
NameTypeReqDescription
answer–yes–
created_atstringyes–
expires_atstringyes–
failure–yes–
input_request–yes–
milestonesarrayyes–
poll_after_msintegeryes–
progress_percentintegeryes–
published_release_sequence–yes–
stagestringyes–
statusstringyes–
task_idstringyes–

No examples provided.

get_knowledge_provenance ~32

Return safe source metadata for up to five active knowledge revisions.

NameTypeReqDescription
revision_refsarrayyes–
NameTypeReqDescription
revisionsarrayyes–

No examples provided.

get_network_workflow ~45

Return a deterministic, ordered workflow including safety, verification, and rollback.

NameTypeReqDescription
contextobjectyes–
goalstringyes–
limitinteger––
NameTypeReqDescription
answer_statusstring––
answersarrayyes–
contextobjectyes–
coveragearray––
cross_platform_examplesarrayyes–
learningobject––
next_actionstringyes–
unknownbooleanyes–

No examples provided.

list_knowledge_domains ~22

List installed, compatible knowledge domain packs and their declared capabilities.

Input schema present but exposes no named parameters.

NameTypeReqDescription
domainsarrayyes–

No examples provided.

query_domain_knowledge ~56

Run deterministic search in one domain using that pack’s validated context and public-record schema.

NameTypeReqDescription
contextobjectyes–
domain_idstringyes–
limitinteger––
questionstringyes–
NameTypeReqDescription
answer_statusstring––
answersarrayyes–
contextobjectyes–
coveragearray––
cross_platform_examplesarrayyes–
domain_idstringyes–
learningobject––
next_actionstringyes–
unknownbooleanyes–

No examples provided.

query_network_knowledge ~48

Return deterministic, version-scoped commands, diagnostics, and concepts for a network question.

NameTypeReqDescription
contextobjectyes–
limitinteger––
questionstringyes–
NameTypeReqDescription
answer_statusstring––
answersarrayyes–
contextobjectyes–
coveragearray––
cross_platform_examplesarrayyes–
learningobject––
next_actionstringyes–
unknownbooleanyes–

No examples provided.

request_expert_answer ~47

Create a durable research task when deterministic knowledge has no applicable answer.

NameTypeReqDescription
contextobjectyes–
idempotency_keystring––
questionstringyes–
NameTypeReqDescription
access_tokenstring––
answer–yes–
created_atstringyes–
expires_atstringyes–
failure–yes–
input_request–yes–
milestonesarrayyes–
poll_after_msintegeryes–
progress_percentintegeryes–
published_release_sequence–yes–
stagestringyes–
statusstringyes–
task_idstringyes–

No examples provided.

resolve_network_context ~71

Resolve vendor, model/platform, portable software family, operating system, and version context.

NameTypeReqDescription
modelstring––
operating_systemstring––
runtime_modestring––
shell_environmentstring––
vendorstring––
versionstring––
NameTypeReqDescription
ambiguitiesarrayyes–
applicable_versionstringyes–
model–yes–
model_resolvedboolean––
operating_systemstringyes–
operating_system_slugstringyes–
platform_slug–yes–
portable_operating_systemboolean––
resolution_confidencenumberyes–
runtime_mode–––
shell_environment–––
software_familystring––
software_family_slugstring––
vendorstringyes–
vendor_resolvedboolean––
vendor_slugstringyes–
version–yes–

No examples provided.

review_network_change ~61

Deterministic advisory review of commands or a configuration diff. It always returns available guidance and never executes a command.

NameTypeReqDescription
commandsarray––
config_diffstring––
contextobjectyes–
intentstringyes–
NameTypeReqDescription
approval_requiredbooleanyes–
blast_radiusarrayyes–
decisionstringyes–
limitationsarrayyes–
matched_rulesarrayyes–
operational_guidancearrayyes–
prechecksarrayyes–
risk_levelstringyes–
rollbackarrayyes–
stop_conditionsarrayyes–
unknown_commandsarrayyes–
verification_planarrayyes–
verification_token–yes–
verification_token_expires_at–yes–

No examples provided.

submit_feedback ~77

Submit correctness, freshness, safety, or completeness feedback without including private logs.

NameTypeReqDescription
access_tokenstring––
categorystringyes–
commentstring––
ratinginteger––
revision_refstring––
sample_contributionobject––
task_idstring––
NameTypeReqDescription
acceptedbooleanyes–
contribution_idstring––
feedback_idstringyes–

No examples provided.

verify_network_change ~50

Evaluate bounded before/after outputs against the signed verification plan returned by review_network_change.

NameTypeReqDescription
after_snapshotstringyes–
before_snapshotstringyes–
verification_tokenstringyes–
NameTypeReqDescription
checksarrayyes–
next_actionstringyes–
resultstringyes–
retentionstringyes–
rollback_recommendedbooleanyes–

No examples provided.

Common questions

What is the CliDeck MCP — Network Knowledge server?

CliDeck MCP — Network Knowledge is listed in the public MCP registry as com.clideck/network-knowledge. Free verified network knowledge for AI agents: deterministic answers, honest unknowns. This page covers its hosted endpoint (https://mcp.clideck.com/mcp).

Is the CliDeck MCP — Network Knowledge server safe to use?

CliDeck MCP — Network Knowledge scores 70 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 CliDeck MCP — Network Knowledge server expose?

CliDeck MCP — Network Knowledge exposes 17 tools: list_knowledge_domains, describe_knowledge_domain, query_domain_knowledge, resolve_network_context, query_network_knowledge, and 12 more. Their descriptions and schemas cost roughly 834 tokens of context every time the server is loaded.

Does the CliDeck MCP — Network Knowledge server require authentication?

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

Is the CliDeck MCP — Network Knowledge server still maintained?

CliDeck MCP — Network Knowledge is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.