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

REMOTE · API.AMBOLT.DEV · 2 COMPONENTS

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

−1 this week 70 Trust /100

Last scanned (21 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 205 tokens (~205/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 14 days we've observed: 25 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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.

  • 13 Oct 26 −3
    • A breaking change shipped without a version bump: still 0.2.0 ▼ security
    • Tool “domain_ssl_sweep” was removed ▼ security
    • Tool “disposable_email_check” was removed ▼ security
    • Tool “dk_co2_intensity” was removed ▼ security
    • Tool “dk_electricity_prices” was removed ▼ security
    • Tool “dns_lookup” was removed ▼ security
    • Tool “doi_lookup” was removed ▼ security
    • Tool “domain_rdap” was removed ▼ security
    • Tool “ecb_key_rates” was removed ▼ security
    • Tool “ens_resolve” was removed ▼ security
    • Tool “entity_resolve” was removed ▼ security
    • Tool “eu_vat_validate” was removed ▼ security
    • Tool “funding_rounds_form_d” was removed ▼ security
    • Tool “fx_rate_ecb” was removed ▼ security
    • Tool “iban_validate” was removed ▼ security
    • Tool “industry_code_lookup” was removed ▼ security
    • Tool “lei_lookup” was removed ▼ security
    • Tool “nordic_company_lookup” was removed ▼ security
    • Tool “base_erc20_balance” was removed ▼ security
    • Tool “base_token_facts” was removed ▼ security
    • Tool “base_token_info” was removed ▼ security
    • Tool “base_transaction” was removed ▼ security
    • Tool “base_wallet_balances” was removed ▼ security
    • Tool “brazil_cnpj_lookup” was removed ▼ security
    • Tool “company_financials” was removed ▼ security
    • Tool “package_vulnerabilities” was removed ▼ security
    • Tool “rss_feed_normaliser” was removed ▼ security
    • Tool “sam_gov_opportunities” was removed ▼ security
    • Tool “sitemap_robots_doctor” was removed ▼ security
    • Tool “solana_swap_quote” was removed ▼ security
    • Tool “solana_swap_transaction” was removed ▼ security
    • Tool “solana_token_facts” was removed ▼ security
    • Tool “solana_token_price” was removed ▼ security
    • Tool “solana_token_search” was removed ▼ security
    • Tool “solana_transaction” was removed ▼ security
    • Tool “solana_wallet_balances” was removed ▼ security
    • Tool “tech_stack_lookup” was removed ▼ security
    • Tool “ted_notices_search” was removed ▼ security
    • Tool “tender_feed” was removed ▼ security
    • Tool “url_metadata” was removed ▼ security
    • Tool “url_to_markdown” was removed ▼ security
    • Tool “us_business_entities” was removed ▼ security
    • Tool “us_treasury_rates” was removed ▼ security
    • Tool “wikipedia_summary” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 158 → 205 ▼ functional
    • New tool “check_page_links” functional
  • 12 Oct 26 +1

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

  • 10 Oct 26 +1

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

  • 7 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
    • Schema quality: 111 → 159 ▼ functional
  • 3 Oct 26 +16
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “crossref_doi” was removed ▼ security
    • Authorization: unverified → partial ▲ security
    • Transport: fail → pass ▲ security
    • Tool “nordic_company_lookup” rewrote its description, which is the text the model reads security
    • Tool “us_treasury_rates” rewrote its description, which is the text the model reads security
    • Tool “ted_notices_search” rewrote its description, which is the text the model reads security
    • Tool “package_vulnerabilities” rewrote its description, which is the text the model reads security
    • Tool “lei_lookup” rewrote its description, which is the text the model reads security
    • Tool “dk_co2_intensity” rewrote its description, which is the text the model reads security
    • Tool “dk_electricity_prices” rewrote its description, which is the text the model reads security
    • Tool “ecb_key_rates” rewrote its description, which is the text the model reads security
    • Tool “eu_vat_validate” rewrote its description, which is the text the model reads security
    • Tool “fx_rate_ecb” rewrote its description, which is the text the model reads security
    • Schema quality: 2539 → 3298 ▼ functional
    • Schema quality: pass → fail ▼ functional
    • New tool “tender_feed” functional
    • New tool “domain_ssl_sweep” functional
    • New tool “entity_resolve” functional
    • New tool “tech_stack_lookup” functional
    • New tool “solana_wallet_balances” functional
    • New tool “url_metadata” functional
    • New tool “base_transaction” functional
    • New tool “base_token_facts” functional
    • New tool “doi_lookup” functional
    • New tool “rss_feed_normaliser” functional
    • New tool “sitemap_robots_doctor” functional
    • New tool “solana_transaction” functional
    • New tool “base_wallet_balances” functional
  • 2 Oct 26 50

    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 16 Oct 2026 · Probed https://api.ambolt.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ambolt.dev CN=YE1,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA384 6ad24f364029b812f4f627403653c114439
SANs: *.ambolt.dev, ambolt.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.ambolt.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
ambolt.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.ambolt.dev/mcp Verified 200
http (plaintext) http://api.ambolt.dev/mcp HTTPS enforced 301 https://api.ambolt.dev/mcp
MCP tools · 1 exposed · ~115 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
check_page_links ~115

Checks every link on one public web page (up to 60 unique links) and reports which are broken, which redirect and which sit behind bot protection. Bot walls (403, 429, Cloudflare and similar challenges) are reported as "blocked", never as broken. Each problem comes with a suggested fix. Read-only: returns data, nothing is changed or sent. Free over MCP (30 requests a minute).

NameTypeReqDescription
urlstringyesA public http(s) page address, for example https://example.com/blog.

No output schema declared.

No examples provided.

Install

How do I install the Ambolt MCP server?

Ambolt is a hosted endpoint at https://api.ambolt.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.ambolt.dev

# add to Claude Code
claude mcp add --transport http dev-ambolt-ambolt 'https://api.ambolt.dev/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 hosted endpoint (https://api.ambolt.dev/mcp).

Is the Ambolt MCP server safe to use?

Ambolt scores 70 out of 100 on VerifyMCP. 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 1 tool: check_page_links. Their descriptions and schemas cost roughly 115 tokens of context every time the server is loaded.

Does the Ambolt MCP server require authentication?

No. We connected to Ambolt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ambolt MCP server still maintained?

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