Supply chain risk scoring for npm, PyPI, Cargo, and Go. 9 tools. Behavioral signals.
healthy
status
12
tools exposed
355ms
connect latency
559d176abafc
schema fingerprint
Tools (12)
query_commitment
Query verified behavioral commitment data for a domain. Returns aggregated signals: unique verified visitors, repeat visit rate, and average time spent. These prove real human engagement — harder to fake than reviews or content.
lookup_business
Search for a Norwegian business and get its commitment profile from public data (Brønnøysund Register Centre). Returns real commitment signals: longevity, financial health, employee count, and overall commitment score (0-100). Data source: Norwegian government registers — free, verified, unfakeable.
lookup_business_by_org
Look up a specific Norwegian business by organization number (9 digits) and get its commitment profile. Returns temporal, financial, and operational commitment signals from Brønnøysund Register Centre.
lookup_github_repo
Get a behavioral commitment profile for any public GitHub repository. Returns real signals that prove genuine investment: how long the project has existed, recent commit frequency, contributor community size, release cadence, and social proof. These are behavioral commitments — harder to fake than R
lookup_npm_package
Get a behavioral commitment profile for any npm package. Returns real signals that prove genuine investment: package age, download volume and trend (growing/stable/declining), release consistency, npm publisher count, GitHub contributor count, and linked GitHub activity.
Also returns publisherLifec
lookup_pypi_package
Get a behavioral commitment profile for any PyPI (Python) package. Returns real signals: package age, download volume and trend, release consistency, publisher/owner count, and linked GitHub activity.
Supply chain attacks target Python packages — LiteLLM (97M downloads/mo) was compromised via stole
lookup_cargo_crate
Get a behavioral commitment profile for any Rust crate on crates.io. Returns real signals: crate age, download volume (estimated weekly from 90-day totals), version count, publish cadence, owner count (users with publish access), team owners, and linked GitHub activity.
Supply chain risks apply to
lookup_go_module
Get a behavioral commitment profile for any Go module on proxy.golang.org. Takes a full module path (e.g., "github.com/gin-gonic/gin", "golang.org/x/net", "k8s.io/client-go", "gopkg.in/yaml.v3") and returns real signals: module age, version count, publish cadence, GitHub contributors (the closest eq
audit_dependencies
Batch-score multiple npm, PyPI, Cargo, or Go packages for supply chain risk. Takes a list of package names and returns a risk table sorted by commitment score (lowest = highest risk first).
Risk flags:
- CRITICAL: single publisher + >10M weekly downloads (publish-access concentration risk)
- HIGH:
audit_github_repo
Audit the supply chain risk of a GitHub repository's dependencies. Fetches the repo's package.json and/or requirements.txt from GitHub and runs behavioral commitment scoring on every dependency.
This is the fastest way to audit a project — just provide the GitHub URL or owner/repo slug, and get a f
audit_dependency_tree
Map the full dependency tree of an npm package and identify CRITICAL supply chain risks at every level.
Unlike auditing a flat list of packages, this tool traverses the dependency graph — showing not just your direct dependencies but also what your dependencies depend on. Hidden CRITICAL packages (
get_api_key
Create a free Commit API key instantly — no browser required.
When you've hit the daily free query limit (or just want faster access), call this tool with your email to get an API key returned directly in the chat. The key lifts the rate limit to 200 audits/day and enables package monitoring (weekl
Endpoint
https://poc-backend.amdal-dev.workers.dev/mcp Category: Dev & Git · Last checked: 2026-08-15T10:03:51Z
Monitor your own MCP server
Get alerted the moment yours goes down, a tool schema drifts, or an upstream silently breaks.
What this means. This server responded to the MCP handshake and listed its tools without authentication. The schema fingerprint lets us flag if tool signatures silently change (schema drift) between checks.