@icedq/mcp-server

MCPattested
v2.0.3io.github.icedq-toolsUnknownUpdated 18d agonpmGitHub

MCP Server for iceDQ Data Reliability Platform

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
1GitHub stars
18d agoLast update
Reads these credentials
  • ICEDQ_CLIENT_SECRETOAuth appoptional

    OAuth client secret. Required when AUTH_TYPE is 'username_password'.

  • ICEDQ_PASSWORDAPI keyoptional

    Your iceDQ password. Required when AUTH_TYPE is 'username_password'.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.icedq-tools
LicenseUnknown
Version2.0.3
Sourcenpm+mcp-registry
npm@icedq/mcp-server
GitHubicedq-tools/mcp-server
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 8eb12b6
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv1.0.5 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

MCP Server for iceDQ Data Reliability Platform

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.