registry-mcp

Name: registry-mcp
Author: io.github.foretak

MCPattestedlive

v0.4.2io.github.foretakMITUpdated 22d agonpm GitHub

The company registry MCP: brreg orgnr, Companies House, Bolagsverket organisationsnummer.

Endpoint healthlive

checked 8 days ago · 403ms

100% of the last 3 checks reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). 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.

638Downloads/wk

22d agoLast update

Reads these credentials

COMPANIES_HOUSE_API_KEYAPI keyoptional
Companies House REST API key, required for the United Kingdom (GB). Free from developer.company-information.service.gov.uk. Unset means GB lookups return an upstream_error naming this variable; every…
BOLAGSVERKET_CLIENT_IDOAuth appoptional
Bolagsverket OAuth 2 client id, required for Sweden (SE) together with BOLAGSVERKET_CLIENT_SECRET. Free, no contract: request both from Bolagsverket's kundanmälan form. Unset means SE lookups return…
BOLAGSVERKET_CLIENT_SECRETOAuth appoptional
Bolagsverket OAuth 2 client secret, the other half of BOLAGSVERKET_CLIENT_ID. Both are needed before Sweden (SE) can answer.

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

LicenseMIT

Version0.4.2

Sourcenpm+mcp-registry

npmregistry-mcp

GitHubforetak/registry-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

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 · 6a82dbc

Dependencies✓ 0 resolved · none vulnerable

Tool surface—

Security scan✓ Cleanv0.4.2 · 21d agoHow well does this scan work?

EvalsNone

IndexedSep 6, 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 source21d ago

Forge read 1 source file 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

The company registry MCP: brreg orgnr, Companies House, Bolagsverket organisationsnummer.

Keywords

mcp

Alternatives

Comparing tool surfaces…

registry-mcp

Tools

Dependency tree