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.

Ambolt

NPM · @AMBOLT/MCP · 2 COMPONENTS

Company registers, financials, funding rounds, tenders and industry codes. Sourced and dated.

+36 this week 70 Trust /100

Last scanned (39 minutes ago)

Scores higher than 39% of npm servers

Category Developer Tools

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 430 tokens (~86/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +4
    • Stability: unverified → 0.30 ▲ functional
  • 13 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 +31
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → fail ▼ functional
    • Security disclosure: fail → unverified ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • Package version: 0.1.0 → 0.2.0 functional
  • 4 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Oct 26 19

    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 17 Oct 2026 · Analysed npm/@ambolt/mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~430 tokens

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 →

Tool Tokens
disposable_email_check ~71

Fast email address check without sending anything: syntax, domain MX records, disposable/temporary-mail domain (9,000+ listed), role address (info@, admin@) and likely typo of a popular provider. Does not confirm that a mailbox exists.

NameTypeReqDescription
emailstringyesEmail address to check.

No output schema declared.

No examples provided.

dns_lookup ~86

Resolve public DNS records for a domain (A, AAAA, MX, TXT, NS, CNAME) and report whether SPF and DMARC records are present, with their policies. DNS queries only; no connection is made to the domain itself.

NameTypeReqDescription
domainstringyesDomain name, e.g. example.com.
typesarray–Record types. Default: all.

No output schema declared.

No examples provided.

fx_rate_ecb ~115

European Central Bank euro foreign-exchange reference rates for any date since 1999, converted to any base currency. Reference rates published around 16:00 CET on working days; not tradable quotes.

NameTypeReqDescription
amountnumber–Amount of base currency to convert.
basestring–Base currency, ISO 4217.
datestring–YYYY-MM-DD. Default: latest. Weekends and holidays return the previous working day.
symbolsarray–Target currencies. Default: all.

No output schema declared.

No examples provided.

iban_validate ~58

Validate an IBAN offline: ISO 13616 checksum (mod 97), registered length for the country, and a normalised and grouped format. Does not check that the account exists.

NameTypeReqDescription
ibanstringyesIBAN, spaces allowed.

No output schema declared.

No examples provided.

package_vulnerabilities ~100

Check an npm or PyPI package version against a public vulnerability database: advisory ids, aliases (CVE, GHSA), summary, severity label and first fixed version, plus the latest published version. Informational; not a full security audit.

NameTypeReqDescription
ecosystemstringyesPackage ecosystem.
namestringyesPackage name, e.g. lodash or requests.
versionstring–Version to check. Default: latest published version.

No output schema declared.

No examples provided.

Install

How do I install the Ambolt MCP server?

Ambolt runs locally as an npm package, launched with npx -y @ambolt/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ambolt/mcp

# add to Claude Code
claude mcp add dev-ambolt-ambolt -- npx -y @ambolt/mcp
Common questions

What is the Ambolt MCP server?

Ambolt is an MCP server listed in the public MCP registry as dev.ambolt/ambolt. Company registers, financials, funding rounds, tenders and industry codes. Sourced and dated. This page covers its npm package (@ambolt/mcp).

Is the Ambolt MCP server safe to use?

Ambolt scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Ambolt MCP server expose?

Ambolt exposes 5 tools: disposable_email_check, dns_lookup, fx_rate_ecb, iban_validate, package_vulnerabilities. Their descriptions and schemas cost roughly 430 tokens of context every time the server is loaded.

Is the Ambolt MCP server still maintained?

Ambolt is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Ambolt MCP server under?

Ambolt declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.