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.

Hamn

MCPB · HAMN-0.1.3.MCPB · 2 COMPONENTS

MCP server for App Store Connect: releases, TestFlight, reviews, reports. Read-only by default.

−29 this week 1 Trust /100

Last scanned (16 hours ago)

Scores higher than 6% of MCPB servers

Category CI/CD and DevOps

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: we could not find this package in its registry.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency3
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: 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.

  • 4 Nov 26 −30
    • Tool safety: pass → unverified ▼ security
    • Stability: fail → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 67 → unverified ▼ functional
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 2 to 5.

  • 27 Oct 26 −13
    • Provenance: pass → fail ▼ security
    • The attested source repository moved: idoo/hamn security
    • Maintenance: unverified → fail ▼ functional
    • License: pass → fail ▼ functional
    • Licence: MIT functional
  • 26 Oct 26 −6
    • Stability: 0.00 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Source repository: pass → fail ▼ security
    • Stability: 0.00 → fail ▼ security
    • Maintenance: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 67 → unverified ▼ functional
    • MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
    • Package version: 0.1.0 → 0.1.3 functional
    • Package version: 0.1.0 → 0.1.2 functional
  • 25 Oct 26 49

    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 mcpb/https://github.com/idoo/hamn/releases/download/v0.1.3/hamn-0.1.3.mcpb@0.1.3

Provenance Package not found

The registry answered that no such package exists, so no provenance could be looked up.

Result Package not found
Ecosystem mcpb
Reason Metadata unavailable

Background: How many MCP packages publish verified provenance →

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. 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 →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

Install

How do I install the Hamn MCP server?

Hamn ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, c6e9a58135a0e76e43956bf60697590931d07b8178d5edb7cf7a5559c25204b3; the commands to do that are on this page. If it does not match, do not open it.

mcpb · hamn-0.1.3.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

c6e9a58135a0e76e43956bf60697590931d07b8178d5edb7cf7a5559c25204b3

macOS / Linux

echo "c6e9a58135a0e76e43956bf60697590931d07b8178d5edb7cf7a5559c25204b3  hamn-0.1.3.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\hamn-0.1.3.mcpb).Hash -eq "c6e9a58135a0e76e43956bf60697590931d07b8178d5edb7cf7a5559c25204b3"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.