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.

MIL — Machine Intelligence Layer

REMOTE · WWW.MILQUERY.COM

Swedish company data (Bolagsverket, SCB) for AI agents, verified, with history and annual reports

Available components

+3 this week 76 Trust /100

Last scanned (18 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 23 Oct 2026.

Category CRM and Sales

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 Security83
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1602 tokens (~178/item across 9 items; 9 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 (22% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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.

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

  • 16 Oct 26 0
    • Tool “search” rewrote its description, which is the text the model reads security
    • Schema quality: 160 → 178 ▼ functional
    • “search” reworded the description of “query” cosmetic
    • “search_companies” reworded the description of “industry_code” cosmetic
  • 15 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Oct 26 72

    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 23 Oct 2026 · Probed https://www.milquery.com/api/mcp?src=registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.milquery.com CN=YR2,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 RSA 2048 SHA256-RSA 66beb4071b295131ae78eb4da9a5f6115fb
SANs: www.milquery.com
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 secure

Validation of www.milquery.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
milquery.com. present 6805 13 Verified
www.milquery.com. Verified address RRset verified with the apex keys
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://www.milquery.com/api/mcp?src=registry Verified 200
http (plaintext) http://www.milquery.com/api/mcp?src=registry HTTPS enforced 308 https://www.milquery.com/api/mcp?src=registry
MCP tools · 9 exposed · ~1,481 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
batch_get_companies ~187

Resolve up to 50 companies in one call. Every requested identifier appears in the result with an explicit status (resolved, not_found or invalid_organisation_number), so absence is never signalled by omission.

NameTypeReqDescription
organisation_numbersarrayyesSwedish organisation numbers (10 or 12 digits), max 50
tierstring–Product tier. basic (free, fair-use limited): identity. verified (0.02 USDC/company): current state with per-value verification and provenance. intelligence (0.08 USDC/company): verified plus history…

No output schema declared.

No examples provided.

fetch ~87

Fetch the register identity of one Swedish company by the id that search returned (its organisationsnummer): name, legal form, industry (SNI), registration date, municipality, status, sources and freshness. Free (Basic). Verified and Intelligence (VAT/F-tax, history, annual reports, signals) are paid via get_company.

NameTypeReqDescription
idstringyesAn id from search: the organisationsnummer
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

find_distress_signals ~137

Find active warning signals for a company. Signals are deterministic rules over register facts and filed annual reports — no AI scores. Examples: vat_registration_lost, f_tax_lost, employee_band_decline, liquidation_in_progress, bankruptcy_proceeding, revenue_decline_yoy, negative_equity. Each signal includes its rule, severity (low, medium, high), supporting facts and detected_at.

NameTypeReqDescription
organisation_numberstringyesSwedish organisation number (10 or 12 digits)
severitystring–Optional: filter by severity level
signal_typestring–Optional: filter to a specific signal type

No output schema declared.

No examples provided.

find_related_companies ~141

Find companies related to the given company by evidence MIL holds: industry_cluster (same SNI classification) and address_cluster (same registered postal code). Relation types MIL has no source data for, such as board_member and ownership, are reported as unavailable with a reason rather than as an empty result.

NameTypeReqDescription
limitinteger–Maximum results (default 10, max 50)
organisation_numberstringyesSwedish organisation number (10 or 12 digits)
relation_typestring–Relation to search for. industry_cluster and address_cluster are supported; board_member and ownership return an explicit unavailable status because MIL does not yet ingest that data.

No output schema declared.

No examples provided.

get_company ~205

Retrieve machine-readable intelligence for a Swedish company by organisation number. Returns current attribute values, resolved knowledge, signals, events, provenance, and data freshness. All values include confidence and source evidence. Unknown or missing data is returned explicitly — never invented.

NameTypeReqDescription
organisation_numberstringyesSwedish organisation number (10 or 12 digits, e.g. '5560000000' or '165560000000')
tierstring–Product tier. basic (free, fair-use limited): identity. verified (0.02 USDC/company): current state with per-value verification and provenance. intelligence (0.08 USDC/company): verified plus history…

No output schema declared.

No examples provided.

get_company_history ~117

Retrieve the change history for a Swedish company — attribute_changed events showing when values were first observed and what changed. Optionally filter by attribute key. Returns temporal bounds (effective_from) and evidence for each event.

NameTypeReqDescription
attribute_keystring–Optional: filter to events for a specific attribute (e.g. 'employee_count', 'legal_form')
limitinteger–Maximum number of events to return (default 50, max 200)
organisation_numberstringyesSwedish organisation number (10 or 12 digits)

No output schema declared.

No examples provided.

search ~231

Search Swedish companies by name or organisationsnummer (10 or 12 digits, dashes allowed). Also accepts simple discovery such as 'restaurants in Trelleborg', 'construction companies in Malmö', 'IT companies in Lund', or 'companies in Trelleborg' (also Swedish 'restauranger i Malmö'). Industries resolve through official English/Swedish SNI descriptions and business aliases, e.g. 'computer repair'/'datorreparation' and 'dining'/'restaurangverksamhet'. Known counties such as Skåne and explicit municipality names use registered administrative geography. Unrecognized or ambiguous wording falls back to name search. Locality is the registered locality, not nearby workplaces. Signal-filtered discovery is refused in free search; use paid find_distress_signals for a known company. Returns up to 10 results, each with an id to pass to fetch and a citable URL. Free (Basic identity only).

NameTypeReqDescription
querystringyesCompany name, organisationsnummer such as 556012-5790, or simple discovery such as restaurants in Trelleborg
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_companies ~247

Search and discover Swedish companies without knowing their organisation number. Filter by company name (partial match), industry code, or presence of active distress signals. Returns compact summary cards — each card includes the organisation_number needed to call get_company for full intelligence. All parameters are optional; omit all to browse all companies in the dataset. Discovery flow: (1) call search_companies to find a company, (2) use the returned organisation_number to call get_company for full intelligence.

NameTypeReqDescription
has_signalsboolean–If true, return only companies with active distress signals. If false, return only companies without. Omit to return all.
industry_codestring–Swedish SNI numeric prefix (2–5 digits), matching any registered activity; e.g. '62' for IT
limitinteger–Maximum number of companies to return (default 20, max 100)
localitystring–Registered locality, combined with ANY matching SNI
namestring–Partial company name to search (case-insensitive substring match on legal name)
organisation_numberstring–Canonical 10-digit or source 12-digit company identity

No output schema declared.

No examples provided.

search_company_events ~129

Search for company attribute change events across companies. Use this to find companies where a specific attribute recently changed, or to monitor for changes in a particular dimension (e.g. employee count drops). Returns events with company identifiers, previous/new values, and temporal bounds.

NameTypeReqDescription
attribute_keystring–Attribute to filter by (e.g. 'employee_count', 'legal_form', 'industry_code')
event_typestring–Event type filter (currently only 'attribute_changed' is supported)
limitinteger–Maximum number of events to return (default 50, max 200)

No output schema declared.

No examples provided.

Install

How do I install the MIL — Machine Intelligence Layer MCP server?

MIL — Machine Intelligence Layer is a hosted endpoint at https://www.milquery.com/api/mcp?src=registry, 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 · www.milquery.com

# add to Claude Code
claude mcp add --transport http lordfreez-ship-it-mil 'https://www.milquery.com/api/mcp?src=registry'
Common questions

What is the MIL — Machine Intelligence Layer MCP server?

MIL — Machine Intelligence Layer is an MCP server listed in the public MCP registry as io.github.lordfreez-ship-it/mil. Swedish company data (Bolagsverket, SCB) for AI agents, verified, with history and annual reports. This page covers its hosted endpoint (https://www.milquery.com/api/mcp?src=registry).

Is the MIL — Machine Intelligence Layer MCP server safe to use?

MIL — Machine Intelligence Layer scores 76 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 MIL — Machine Intelligence Layer MCP server expose?

MIL — Machine Intelligence Layer exposes 9 tools: get_company, get_company_history, find_distress_signals, search_company_events, search_companies, and 4 more. Their descriptions and schemas cost roughly 1,481 tokens of context every time the server is loaded.

Does the MIL — Machine Intelligence Layer MCP server require authentication?

No. We connected to MIL — Machine Intelligence Layer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MIL — Machine Intelligence Layer MCP server still maintained?

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