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.

Bosco Labs: official records for AI agents

REMOTE · API.BOSCOLABS.DEV · 3 COMPONENTS

Sanctions, KYB company checks, SEC EDGAR, EU law and more from official sources, each row sourced

+2 this week 71 Trust /100

Last scanned (22 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2040 tokens (~340/item across 6 items; 6 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: 27 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 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
  • Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 18 Nov 26 +1
    • Tool “check_counterparty” rewrote its description, which is the text the model reads security
    • Schema quality: 379 → 340 ▲ functional
    • Tool “check_counterparty” now declares an output schema ▲ functional
    • First check of Tool coverage: 50 functional
    • Schema quality: good → excellent functional
    • New tool “describe_records_tool” functional
    • New tool “find_sec_company” functional
    • New tool “get_lei_record” functional
  • 17 Nov 26 0
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “counterparty_check” was removed ▼ security
    • Tool “plan_official_records_query” was removed ▼ security
    • Tool “run_official_records_plan” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “counterparty_check” rewrote its description, which is the text the model reads security
    • New tool “run_records_plan” functional
    • New tool “plan_records_query” functional
    • New tool “check_counterparty” functional
    • “counterparty_check” reworded the description of “country” cosmetic
  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “run_official_records_plan” rewrote its description, which is the text the model reads security
    • Tool “plan_official_records_query” rewrote its description, which is the text the model reads security
    • Tool “counterparty_check” changed its title: Counterparty Check API: KYB checklist from official registers → Counterparty Check API: KYB, sanctions screening, insolvency cosmetic
  • 13 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 12 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 10 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • “counterparty_check” reworded the description of “country” cosmetic
  • 9 Nov 26 0
    • Stability: 0.03 → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “sec_ownership” was removed ▼ security
    • Tool “us_federal_awards” was removed ▼ security
    • Tool “us_federal_rules” was removed ▼ security
    • Tool “us_house_trades” was removed ▼ security
    • Tool “vat_iban_check” was removed ▼ security
    • Tool “describe_official_records_tool” was removed ▼ security
    • Tool “company_hiring_signals” was removed ▼ security
    • Tool “drug_safety” was removed ▼ security
    • Tool “company_accounts” was removed ▼ security
    • Tool “clinical_trials” was removed ▼ security
    • Tool “uk_new_companies” was removed ▼ security
    • Tool “tariff_lookup” was removed ▼ security
    • Tool “company_check” was removed ▼ security
    • Tool “dutch_address_lookup” was removed ▼ security
    • Tool “dutch_case_law” was removed ▼ security
    • Tool “esef_annual_reports” was removed ▼ security
    • Tool “eu_law_lookup” was removed ▼ security
    • Tool “eu_rates_inflation” was removed ▼ security
    • Tool “eu_tenders” was removed ▼ security
    • Tool “identifier_resolver” was removed ▼ security
    • Tool “national_law_lookup” was removed ▼ security
    • Tool “package_vulns” was removed ▼ security
    • Tool “product_recalls” was removed ▼ security
    • Tool “sanctions_screening” was removed ▼ security
    • Tool “sec_company_financials” was removed ▼ security
    • Tool “sec_company_screen” was removed ▼ security
    • Tool “sec_filings_feed” was removed ▼ security
    • Tool “sec_insider_trades” was removed ▼ security
    • Tool “dod_contract_awards” was removed ▼ security
    • Tool “plan_official_records_query” rewrote its description, which is the text the model reads security
    • Tool “run_official_records_plan” rewrote its description, which is the text the model reads security
    • Schema quality: 379 → 321 ▲ functional
    • Destructive annotations: 0 → pass functional
    • New tool “counterparty_check” functional
  • 8 Nov 26 0
    • Tool “sanctions_screening” rewrote its description, which is the text the model reads security
    • Tool “company_check” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • New tool “vat_iban_check” functional
    • New tool “run_official_records_plan” functional
    • New tool “plan_official_records_query” functional
    • New tool “describe_official_records_tool” functional
    • “sanctions_screening” added an optional parameter “addresses” cosmetic
    • “company_check” reworded the description of “include” cosmetic
    • “sanctions_screening” made “names” optional cosmetic
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 21 Nov 2026 · Probed https://api.boscolabs.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.boscolabs.dev CN=YR2,O=Let's Encrypt,C=US 6 Nov 2026 4 Feb 2027 RSA 2048 SHA256-RSA 6bf6bfb80557ba04d475c922e603399695c
SANs: *.boscolabs.dev, boscolabs.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.boscolabs.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
boscolabs.dev. No DS 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
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.boscolabs.dev/mcp Verified 200
http (plaintext) http://api.boscolabs.dev/mcp HTTPS enforced 308 https://api.boscolabs.dev/mcp
MCP tools · 6 exposed · ~1,824 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_counterparty ~531

Can I do business with this company? One call checks a supplier, customer or partner against official sources and returns a checklist: pass, fail, review or unverified per check, each with its source link and time. To screen a vendor list, pass up to 10 companies in `companies`: one checklist per company, same price each. Inputs: `query` for one company, or `companies` for up to 10 (a name or number each, or an object with these same fields). `country` narrows a name search to one register. `vatNumber`, `iban` and `walletAddresses` are the details the counterparty gave you: each adds a check (VAT registered to this company, IBAN valid and in its country, wallets not sanctioned); leave out what you do not have. Read-only, no side effects. Charged per row returned, at the price below; a call that fails or runs out of time (55 s) is free. If one source does not answer, the rest still comes back and `warnings` names the gap. Limit: 60 calls a minute per key (10 on a new free key); past it the call is refused (rate_limited, free): retry after about 10 seconds. Price: $0.05 per `counterparty-check`.

NameTypeReqDescription
companiesarray–Check a list of companies in one run instead of `query`: up to 10 companies, each a name or number ("Tesco PLC") or an object with the fields above
countrystring–ISO 3166 alpha-2 country code to disambiguate, e.g. "DK", "GB", "NO", "FR", "FI", "EE", "IE", "CZ", "LV", "LT", "SK", "SE", "BE", "NL", "US"
ibanstring–The bank account the counterparty wants to be paid on, e.g. "DK5000400440116243"
querystring–The counterparty to check: a name (e.g. "Novo Nordisk") or an identifier: LEI
vatNumberstring–The VAT number the counterparty gave you, with its country prefix, e.g. "DK24256790"
walletAddressesarray–Wallet addresses the counterparty wants to be paid on, e.g. ["0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9"]
NameTypeReqDescription
balance_usdnumber|null––
charged_usdnumber|null––
countnumber|nullyes–
duration_secondsnumber|null––
messagestring|null––
rowsarrayyes–
toolstring|null––
warningsarray|null––

No examples provided.

describe_records_tool ~106

Free, no key needed. One Bosco Labs tool's full input schema, example input, example rows, output fields, price per row, caps and sources. Use it before calling a tool whose input you are unsure of: the tool list shortens each input field to one sentence, and this shows every field, its allowed values and a working example. An unknown name returns the closest names.

NameTypeReqDescription
namestringyesTool name, e.g. search_eu_tenders.

No output schema declared.

No examples provided.

find_sec_company ~308

Free, no API token needed. Identify a US-listed (SEC-registered) company: CIK, official name, ticker(s), exchange(s), industry (SIC code) and state of incorporation (source: SEC EDGAR company tickers file and submissions API). Use it to turn a ticker or name into the CIK that SEC tools take, or to check which exchange a stock trades on. Pass a ticker, a CIK or part of the name (best matches first, then by company size; check `name`). A name search covers companies with a listed ticker (about 10,000); a CIK also finds filers without one. Returns one row per company: cik, name, tickers, exchanges, sic, sic_description, state_of_incorporation, fiscal_year_end (MMDD), source_url (the EDGAR company page; cite it) and next_steps (the paid Bosco Labs calls for its filings and insider trades). Inputs: `query` is a ticker, a CIK or part of the name; `max_results` (1-5, default 3) applies to a name search only. Read-only, no key, no charge; at most 30 free lookups a minute per caller.

NameTypeReqDescription
max_resultsinteger–Max companies for a name search (1-5).
querystringyesA ticker (AAPL), a CIK (320193) or part of the company name ("apple")
NameTypeReqDescription
balance_usdnumber|null––
charged_usdnumber|null––
countnumber|nullyes–
duration_secondsnumber|null––
messagestring|null––
rowsarrayyes–
toolstring|null––
warningsarray|null––

No examples provided.

get_lei_record ~355

Free, no API token needed. Legal Entity Identifier (LEI) lookup in the official GLEIF register: about 2.9 million companies, funds and other legal entities worldwide (source: GLEIF API, CC0 open data). Use it to identify a company: its exact legal name, LEI, whether it is active, its jurisdiction and country, its local registration number and its ultimate parent company. Pass an LEI (exact record) or a company name (best matches first; check `legal_name`). Returns one row per entity: lei, legal_name, entity_status (ACTIVE/INACTIVE), registration_status (ISSUED, LAPSED, ...), jurisdiction, legal_address_country, legal_address_city, headquarters_country, registered_as (local registry number), ultimate_parent (lei, legal_name; when reported), source_url (the GLEIF record; cite it) and next_steps (the paid Bosco Labs call for this company's financials: the tool and arguments to call next). Inputs: `query` is either a 20-character LEI (one exact record) or a company name (best matches first); `max_results` (1-5, default 3) applies to a name search only. Read-only, no key, no charge; at most 30 free lookups a minute per caller. Nothing found: an error that says what to try.

NameTypeReqDescription
max_resultsinteger–Max companies for a name search (1-5).
querystringyesA 20-character LEI, e.g. 724500Y6DUVHQD6OXN27, or a company name, e.g. "Heineken"
NameTypeReqDescription
balance_usdnumber|null––
charged_usdnumber|null––
countnumber|nullyes–
duration_secondsnumber|null––
messagestring|null––
rowsarrayyes–
toolstring|null––
warningsarray|null––

No examples provided.

plan_records_query ~316

Free, no key needed. Turns a question in plain words into the exact typed Bosco Labs calls that answer it: tool, input, why, and the maximum price of each step, plus what is not covered. Pass the user's question verbatim AND the entities you extracted from it (company_names, tickers, identifiers, countries, dates, law references...): the planner trusts your entities over its own parsing and puts them in the right input fields. The plan echoes them in entities_used and lists in `missing` what to pass for a better plan. Rules and examples first; only when they are unsure and you passed no entities does a small AI step extract the entities (budget-capped, marked `assisted`). Same steps, same plan_id. Run it with run_records_plan (paid, max_usd) or call the listed tools directly. Low confidence returns the top 3 candidate tools instead. Questions are kept 30 days in a cut-down form; leave out personal details.

NameTypeReqDescription
entitiesobject–What you (the calling agent) already extracted from the user's question. Extract these from the question yourself; the planner trusts them over its own parsing and puts them in the right input fields…
questionstringyesThe user's question, verbatim, e.g. "Is Rosneft on the EU sanctions list?" (English, Dutch, German or French).

No output schema declared.

No examples provided.

run_records_plan ~208

Runs a plan from plan_records_query (its plan_id) or explicit steps, all steps in parallel, under a hard max_usd: if the worst case could exceed it, nothing runs. Each step is charged to the caller's key exactly like a direct tool call (failed steps are free). Returns one section per step (via_tool, via_input, rows with source_url), a receipt and the citations. Reaches all 30 tools; to list them as MCP tools, add ?tools=all to the MCP URL.

NameTypeReqDescription
max_usdnumberyesHard cap in USD: refused, nothing run, if the steps' worst case could cost more.
plan_idstring–The plan_id plan_records_query returned (or pass steps).
stepsarray–Explicit steps instead of a plan_id: [{tool, input}], tool a name from GET /v1/tools (eu-tenders or search_eu_tenders), input that tool's input.

No output schema declared.

No examples provided.

Install

How do I install the Bosco Labs: official records for AI agents MCP server?

Bosco Labs: official records for AI agents is a hosted endpoint at https://api.boscolabs.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.boscolabs.dev

# add to Claude Code
claude mcp add --transport http bosco-labs-bosco-labs-data 'https://api.boscolabs.dev/mcp'
Common questions

What is the Bosco Labs: official records for AI agents MCP server?

Bosco Labs: official records for AI agents is an MCP server listed in the public MCP registry as io.github.Bosco-Labs/bosco-labs-data. Sanctions, KYB company checks, SEC EDGAR, EU law and more from official sources, each row sourced. This page covers its hosted endpoint (https://api.boscolabs.dev/mcp).

Is the Bosco Labs: official records for AI agents MCP server safe to use?

Bosco Labs: official records for AI agents scores 71 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 Bosco Labs: official records for AI agents MCP server expose?

Bosco Labs: official records for AI agents exposes 6 tools: check_counterparty, plan_records_query, run_records_plan, describe_records_tool, get_lei_record, find_sec_company. Their descriptions and schemas cost roughly 1,824 tokens of context every time the server is loaded.

Does the Bosco Labs: official records for AI agents MCP server require authentication?

No. We connected to Bosco Labs: official records for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bosco Labs: official records for AI agents MCP server still maintained?

Bosco Labs: official records for AI agents is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Bosco Labs: official records for AI agents MCP server?

VerifyMCP ran 13 checks on Bosco Labs: official records for AI agents, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.