Skip to content

Bosco Labs: official records for AI agents MCP server

io.github.Bosco-Labs/bosco-labs-dataBosco-Labsstreamable-httpv0.4.0Scanned

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

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Bosco Labs: official records for AI agents MCP server can do

The Bosco Labs: official records for AI agents MCP server is published by the GitHub account Bosco-Labs. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools bring in text other people can write (lei_lookup and sec_company_lookup).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 0.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Only reads 4Show 4 read-only tools
  • describe_official_records_toolFree, no key needed.No findings

    Why it is in this group

    • The name "describe_official_records_tool" says "describe": a word for reading.
    Description, as the server wrote it
    Free, no key needed. One Bosco Labs tool's input schema, example input, example rows, output fields, price per row, caps and sources. Takes the tool name (eu_tenders, or its HTTP slug eu-tenders); an unknown name returns the closest names.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Describe an official-records tool
  • lei_lookupFree, no API token needed.Reads text others writeNo findings

    Why it is in this group

    • The name "lei_lookup" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: LEI lookup (GLEIF, free)
  • plan_official_records_queryFree, no key needed.No findings

    Why it is in this group

    • The name "plan_official_records_query" says "query": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Plan an official-records query
  • sec_company_lookupFree, no API token needed.Reads text others writeNo findings

    Why it is in this group

    • The name "sec_company_lookup" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • openWorldHint: true
    • readOnlyHint: true
    • title: SEC company lookup: ticker to CIK (free)

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.boscolabs.dev/.well-known/oauth-protected-resource/mcp/free
Authorization servers
https://api.boscolabs.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools2 added.+2 addedView diff

Install

Pinned to version 0.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bosco-labs-data https://api.boscolabs.dev/mcp/free
claude mcp add --transport http bosco-labs-data https://api.boscolabs.dev/mcp/free

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bosco-labs-data__plan_official_records_query",
      "mcp__bosco-labs-data__describe_official_records_tool",
      "mcp__bosco-labs-data__lei_lookup",
      "mcp__bosco-labs-data__sec_company_lookup"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bosco-labs-data. Review it before you use it.

Capability tags behind 2 rules
  • mcp__bosco-labs-data__lei_lookup untrusted-input
  • mcp__bosco-labs-data__sec_company_lookup untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Bosco-Labs/bosco-labs-data/verify?hash=57949ba96aee389c098b89e7669ffd5b6f76bf20892beb76c34c22d48917555b" | jq -e '.changed == false'

Pinned hash 57949ba96aee, from Nov 17, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Bosco-Labs/bosco-labs-data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Bosco-Labs/bosco-labs-data
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Bosco-Labs/bosco-labs-data.svg)](https://radar.anlyon.com/servers/io.github.Bosco-Labs/bosco-labs-data)

Source: MCP Registry · repository. Synced Nov 17, 2026, 21:17 UTC.

Bosco Labs: official records for AI agents MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Bosco Labs: official records for AI agents MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Bosco Labs: official records for AI agents MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Bosco Labs: official records for AI agents MCP server have?

4 tools: 4 read. plan_official_records_query, describe_official_records_tool, lei_lookup and sec_company_lookup.

Does the Bosco Labs: official records for AI agents MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Bosco Labs: official records for AI agents MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Bosco Labs: official records for AI agents MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.