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

+4 this week 77 Trust /100

Last scanned (14 hours ago)

Scores higher than 67% 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 Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1524 tokens (~381/item across 4 items; 4 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 Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
  • 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 4 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
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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1
    • Tool “describe_official_records_tool” rewrote its description, which is the text the model reads security
  • 16 Nov 26 +1
    • Tool “plan_official_records_query” rewrote its description, which is the text the model reads security
  • 14 Nov 26 +1

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

  • 12 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 9 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 8 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 100% → 95% ▼ functional
    • Schema quality: 315 → 351 ▼ functional
    • Tool coverage: 100% → 50% ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “plan_official_records_query” functional
    • New tool “describe_official_records_tool” functional
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/free

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/free Verified 200
http (plaintext) http://api.boscolabs.dev/mcp/free HTTPS enforced 308 https://api.boscolabs.dev/mcp/free
MCP tools · 4 exposed · ~1,365 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
describe_official_records_tool ~114

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. Takes the tool name (eu_tenders, or its HTTP slug eu-tenders); an unknown name returns the closest names.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

lei_lookup ~300

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: tool and arguments on the remote MCP server and HTTP API, stdio_tool in this package).

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
resultarrayyes–

No examples provided.

plan_official_records_query ~686

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_official_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
addresses––Dutch addresses as written, e.g. ["Damrak 1 Amsterdam"].
amount_min––A minimum amount in USD or EUR, e.g. 1000000 for "over $1M".
company_names––Companies, with legal form if given, e.g. ["Novo Nordisk A/S"]; also fund managers and hiring companies.
countries––ISO 3166 alpha-2 codes (or English names), e.g. ["DE", "NL"]: the registry country, buyer country, origin of goods or trial location.
date_from––YYYY-MM-DD, start of the asked period (resolve relative dates).
date_to––YYYY-MM-DD, end of the asked period.
entities––The same fields as one object (either form works).
identifiers––Identifiers by kind, each a list of strings: lei, isin, cik, figi, company_number, kvk, cvr, org_number, nct, cve, ecli, celex, cfr, hs_code, naics, postcode, bag_id, vat, iban, wallet, krs, nip, reg…
keywords––The topic or search phrase in the user's words, e.g. "cloud hosting", "huurrecht", "non-small cell lung cancer".
law––A law reference: {"act": "GDPR", "article": "6"} or {"act": "Companies Act 2006", "article": "172", "jurisdiction": "UK"}; jurisdiction EU, UK or NL.
package––A software package: {"ecosystem": "npm", "name": "lodash", "version": "4.17.15"}.
person_names––People, e.g. ["Nancy Pelosi"] (House members, sanctions targets).
products––Drugs, consumer products or goods, e.g. ["Ozempic"], ["2019 Honda Accord"], ["cotton t-shirt"].
questionstringyesThe user's question, verbatim (EN, NL, DE or FR).
tickers––US stock tickers, e.g. ["NVDA", "BRK-B"].

No output schema declared.

No examples provided.

sec_company_lookup ~265

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

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
resultarrayyes–

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/free, 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/free'
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/free).

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

Bosco Labs: official records for AI agents scores 77 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 4 tools: plan_official_records_query, describe_official_records_tool, lei_lookup, sec_company_lookup. Their descriptions and schemas cost roughly 1,365 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.