Ambolt
Server Details
Company registers, financials, funding rounds, tenders and industry codes. Sourced and dated.
- Status
- Healthy
- Uptime
- 100.0% over 27 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between tools. Its purpose (checking links on a single page) is stated unambiguously.
The single tool name check_page_links follows a clear snake_case verb_noun pattern that accurately describes the action and target. No inconsistencies are possible with one tool.
A single tool is thin for a server surface, though it is well-scoped and non-trivial for its narrow link-checking purpose. The rubric treats 1-2 tools as borderline regardless of quality.
The tool is internally complete (classifies broken/redirect/blocked links and suggests fixes), but the domain surface is limited: it only handles one page at a time with no site-wide crawl, sitemap, or batch operation. These are notable gaps an agent would hit when auditing more than one page.
Available Tools
1 toolcheck_page_linksAmbolt Link Checker: Check the Links on a PageARead-onlyIdempotentInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | A public http(s) page address, for example https://example.com/blog. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, open-world, idempotent, and non-destructive behavior, yet the description adds substantial operational detail beyond them: the 60-link limit, how bot walls are reported as blocked rather than broken, fix suggestions, and the 30-requests-per-minute rate limit. This is exactly the kind of extra context the annotations do not provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded, with the core action first, followed by important behavioral caveats and limits. Every sentence earns its place and none are redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description carries the return-value burden by naming the result categories (broken, redirect, blocked) and noting that each problem includes a suggested fix. For a simple read-only checker, this is complete enough to call correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single url parameter is already fully documented with an example. The description repeats that it is one public web page but adds no new syntax or format guidance, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a precise verb and resource: it checks every link on one public web page and reports broken, redirect, and blocked links. No siblings exist to differentiate from, but the scope and output categories are unmistakable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context for use: one public web page, up to 60 unique links, free over MCP at 30 requests per minute. It does not explicitly state when not to use it, but with no sibling tools the practical constraints are sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
44 tool updates
- Removed
base_erc20_balance - Removed
base_token_facts - Removed
base_token_info - Removed
base_transaction - Removed
base_wallet_balances - Removed
brazil_cnpj_lookup - Added
check_page_links - Removed
company_financials - Removed
disposable_email_check - Removed
dk_co2_intensity - Removed
dk_electricity_prices - Removed
dns_lookup - Removed
doi_lookup - Removed
domain_rdap - Removed
domain_ssl_sweep - Removed
ecb_key_rates - Removed
ens_resolve - Removed
entity_resolve - Removed
eu_vat_validate - Removed
funding_rounds_form_d - Removed
fx_rate_ecb - Removed
iban_validate - Removed
industry_code_lookup - Removed
lei_lookup - Removed
nordic_company_lookup - Removed
package_vulnerabilities - Removed
rss_feed_normaliser - Removed
sam_gov_opportunities - Removed
sitemap_robots_doctor - Removed
solana_swap_quote - Removed
solana_swap_transaction - Removed
solana_token_facts - Removed
solana_token_price - Removed
solana_token_search - Removed
solana_transaction - Removed
solana_wallet_balances - Removed
tech_stack_lookup - Removed
ted_notices_search - Removed
tender_feed - Removed
url_metadata - Removed
url_to_markdown - Removed
us_business_entities - Removed
us_treasury_rates - Removed
wikipedia_summary
1 tool update
- Added
sam_gov_opportunities
2 tool updates
- Changed
entity_resolve1 field changed- added
Input schema / properties / minScoreAdded value: +{ + "default": 0, + "description": "Only return candidates with a match score of at least this value (for example 90 for KYB checks that must not accept fuzzy matches). A query with no such candidate comes back as matched: false and is not billed.", + "maximum": 100, + "minimum": 0, + "type": "integer" +}
- Changed
funding_rounds_form_d2 fields changed- changed
Input schema / properties / limit / maximumPrevious value: -100New value: +500 - added
Input schema / properties / maxSecondsAdded value: +{ + "default": 25, + "description": "Time budget for reading filings. A weekly scheduled run over many filings should use 300 or more; the result says whether every filing in range was read (complete) and gives nextSince for the next run.", + "maximum": 800, + "minimum": 5, + "type": "integer" +}
3 tool updates
- Added
company_financials - Added
funding_rounds_form_d - Added
us_business_entities
1 tool update
- Added
industry_code_lookup
1 tool update
- Changed
entity_resolve1 field changed- changed
Input schema / properties / country / descriptionPrevious value: -"Optional ISO country code (NO, FI, CZ, SK, FR, GB, LV, EE, PL, BR, SG) to search one register only. Faster and more precise."New value: +"Optional ISO country code (NO, FI, CZ, SK, FR, GB, LV, EE, PL, BR, SG, CA) to search one register only. Faster and more precise."
2 tool updates
- Changed
brazil_cnpj_lookup1 field changed- changed
Input schema / properties / cnpj / descriptionPrevious value: -"One CNPJ, for example 33.000.167/0001-01 or 33000167000101."New value: +"One CNPJ, for example 33.000.167/0001-01, 33000167000101 or an alphanumeric CNPJ such as 12.ABC.345/01DE-35."
- Changed
entity_resolve1 field changed- changed
Input schema / properties / country / descriptionPrevious value: -"Optional ISO country code (NO, FI, CZ, SK, FR, GB, LV, EE, PL, BR) to search one register only. Faster and more precise."New value: +"Optional ISO country code (NO, FI, CZ, SK, FR, GB, LV, EE, PL, BR, SG) to search one register only. Faster and more precise."
1 tool update
- Added
brazil_cnpj_lookup
1 tool update
- Changed
entity_resolve1 field changed- changed
Input schema / properties / country / descriptionPrevious value: -"Optional ISO country code (NO, FI, CZ, SK, FR, GB, LV, PL) to search one register only. Faster and more precise."New value: +"Optional ISO country code (NO, FI, CZ, SK, FR, GB, LV, EE, PL, BR) to search one register only. Faster and more precise."
1 tool update
- Changed
entity_resolve1 field changed- changed
Input schema / properties / country / descriptionPrevious value: -"Optional ISO country code (NO, FI, CZ, SK, FR, GB, PL) to search one register only. Faster and more precise."New value: +"Optional ISO country code (NO, FI, CZ, SK, FR, GB, LV, PL) to search one register only. Faster and more precise."
2 tool updates
- Added
domain_ssl_sweep - Changed
entity_resolve1 field changed- changed
Input schema / properties / country / descriptionPrevious value: -"Optional ISO country code (NO, FI, CZ, FR, GB) to search one register only. Faster and more precise."New value: +"Optional ISO country code (NO, FI, CZ, SK, FR, GB, PL) to search one register only. Faster and more precise."
3 tool updates
- Added
entity_resolve - Added
tech_stack_lookup - Added
tender_feed
4 tool updates
- Added
base_token_facts - Added
rss_feed_normaliser - Added
sitemap_robots_doctor - Added
url_metadata
2 tool updates
- Removed
crossref_doi - Added
doi_lookup
4 tool updates
- Added
base_transaction - Added
base_wallet_balances - Added
solana_transaction - Added
solana_wallet_balances
1 tool update
- Changed
solana_swap_quote1 field changed- changed
Input schema / properties / slippageBps / descriptionPrevious value: -"Maximum slippage in basis points. Omit for Jupiter's automatic estimate."New value: +"Maximum slippage in basis points. Omit for the automatic estimate."
25 tool updates
- First observed
base_erc20_balance - First observed
base_token_info - First observed
crossref_doi - First observed
disposable_email_check - First observed
dk_co2_intensity - First observed
dk_electricity_prices - First observed
dns_lookup - First observed
domain_rdap - First observed
ecb_key_rates - First observed
ens_resolve - First observed
eu_vat_validate - First observed
fx_rate_ecb - First observed
iban_validate - First observed
lei_lookup - First observed
nordic_company_lookup - First observed
package_vulnerabilities - First observed
solana_swap_quote - First observed
solana_swap_transaction - First observed
solana_token_facts - First observed
solana_token_price - First observed
solana_token_search - First observed
ted_notices_search - First observed
url_to_markdown - First observed
us_treasury_rates - First observed
wikipedia_summary
Related MCP Connectors
Find open Australian and NZ tenders and grants, match them to a company, and see who holds the work.
Live data from 80+ official national company registries. Unmodified. For KYB and due diligence.
Verified company profiles, financials, ownership, registry records and business contacts.
UK company lookup & monitor, UK/EU tenders, awards, planning, charities, schools, NHS, trade marks.
Related MCP Servers
- AlicenseAqualityAmaintenanceOpenRegistry - the world's first MCP and API for live company filings directly from official government registries worldwide. 90+ countries.1022Apache 2.0
- FlicenseNot gradedqualityCmaintenanceThe most comprehensive signal intelligence on Swiss businesses — 800K+ companies with people, FINMA/SRO regulatory data, building permits, procurement tenders, and AI-enriched profiles from the official commercial register.-
- AlicenseNot gradedqualityBmaintenanceCompany data for Spain, France, the UK, Ireland and Poland — registry, KYB and sanctions.1,482 npmMIT
- AlicenseNot gradedqualityDmaintenanceSearch, verify and screen over 1 million African companies across 18 official government registries, along with the public contracts they have won and OFAC/UN sanctions screening. Every result carries its registry source, date and a confidence signal, and the server returns nulls rather than fabricating data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.