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.

io.github.CloudCorpRecords/routerbase

OCI · GHCR.IO/CLOUDCORPRECORDS/ROUTERBASE · 2 COMPONENTS

Router defaults, PSTI/CRA compliance checks, and MAC lookup via the hosted ssid.ai MCP service.

41 Trust /100

Last scanned (22 hours ago)

Scores higher than 46% of OCI servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 270 tokens (~67/item across 4 items; 4 tools + 0 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 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 2 Nov 26 41

    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 4 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/routerbase@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 4 exposed · ~270 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
check_router_compliance ~47

Check a router model against UK PSTI and EU CRA universal-default-password rules.

NameTypeReqDescription
slugstringyesRouter model slug to check against the UK PSTI and EU CRA rules.

No output schema declared.

No examples provided.

get_router_defaults ~85

Get the manufacturer-cited factory login defaults for a router model by slug, or by brand and model.

NameTypeReqDescription
brandstring–Router brand name; used together with model when no slug is given.
modelstring–Router model name; used together with brand when no slug is given.
slugstring–Router model slug identifying the record to fetch.

No output schema declared.

No examples provided.

lookup_mac ~48

Look up a MAC address: vendor/OUI from the upstream service plus a local classification of the address kind.

NameTypeReqDescription
macstringyesMAC address to look up, in any common separator format.

No output schema declared.

No examples provided.

submit_correction ~90

Submit a cited correction to a router record for verification. Requires an ssid Pro API key.

NameTypeReqDescription
fieldstringyesRecord field the correction proposes to change.
proposedValuestringyesProposed corrected value for the field.
slugstringyesSlug of the router record the correction applies to.
sourceUrlstringyesURL of the source that cites the corrected value.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/routerbase MCP server?

io.github.CloudCorpRecords/routerbase runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/routerbase:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cloudcorprecords/routerbase

# add to Claude Code
claude mcp add cloudcorprecords-routerbase -- docker run --rm -i ghcr.io/cloudcorprecords/routerbase:0.1.0
Common questions

What is the io.github.CloudCorpRecords/routerbase MCP server?

io.github.CloudCorpRecords/routerbase is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/routerbase. Router defaults, PSTI/CRA compliance checks, and MAC lookup via the hosted ssid.ai MCP service. This page covers its container image (ghcr.io/cloudcorprecords/routerbase).

Is the io.github.CloudCorpRecords/routerbase MCP server safe to use?

io.github.CloudCorpRecords/routerbase scores 41 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 io.github.CloudCorpRecords/routerbase MCP server expose?

io.github.CloudCorpRecords/routerbase exposes 4 tools: get_router_defaults, check_router_compliance, lookup_mac, submit_correction. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/routerbase MCP server still maintained?

io.github.CloudCorpRecords/routerbase is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/routerbase MCP server under?

io.github.CloudCorpRecords/routerbase declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.