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.okwithit9-debug/permitverdict-mcp

NPM · PERMITVERDICT-MCP · 2 COMPONENTS · SCANNED AUG 6

Crypto price-event settlement verdicts and US building-permit data, paid per call in USDC.

Available components

remote · permitverdict.com 68 npm · permitverdict-mcp 46
46 Trust /100
Trust breakdown (6 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 →

Supply Chain Security88
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 113 of 117 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 113 of 117 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to okwithit9-debug/permitverdict-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · permitverdict-mcp

# add to Claude Code
claude mcp add okwithit9-debug-permitverdict-mcp -- npx -y permitverdict-mcp
# add to Codex CLI
codex mcp add okwithit9-debug-permitverdict-mcp -- npx -y permitverdict-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "okwithit9-debug-permitverdict-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "permitverdict-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add okwithit9-debug-permitverdict-mcp --command npx --arg -y --arg permitverdict-mcp
# ~/.hermes/config.yaml
mcp_servers:
  okwithit9-debug-permitverdict-mcp:
    command: "npx"
    args: ["-y", "permitverdict-mcp"]
// mcp.json
{
  "mcpServers": {
    "okwithit9-debug-permitverdict-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "permitverdict-mcp"
      ]
    }
  }
}
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.

  • 6 Aug 26 46

    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 6 Aug 2026 · Analysed npm/[email protected]

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo okwithit9-debug/permitverdict-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/okwithit9-debug/permitverdict-mcp/.github/workflows/publish.yml@refs/tags/v0.2.4
Rekor log index 2360104975
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:7abe536f05e3c6cf879b2a45ea5ddc92629a4d0375a96596393d480973d01afd2f41be80ddbe9225772dac7b98759480e63c0a4d59c2985a4eb90def2
Dependencies 113 packages
Packages resolved 113
Deprecated 109
Stale 29
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. This package has not been through a sandbox run yet.