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.

FIRMEN.directory

REMOTE · MCP.FIRMEN.DIRECTORY

Swiss and Austrian company register facts and owner-maintained listings, each with its source.

+3 this week 81 Trust /100

Last scanned (17 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 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
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 966 tokens (~322/item across 3 items; 2 tools + 1 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 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 (100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

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

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 13 Nov 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.

  • 11 Nov 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.

  • 9 Nov 26 +1

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

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 75

    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 21 Nov 2026 · Probed https://mcp.firmen.directory/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=firmen.directory CN=WE1,O=Google Trust Services,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA256 681c4836ac003ae7133984ae75faad63
SANs: firmen.directory, *.firmen.directory
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.firmen.directory. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
directory. DS published 5701 8 Verified
firmen.directory. DS published 2371 13 Verified
mcp.firmen.directory. 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=31536000; includeSubDomains; preload
content-security-policy default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.firmen.directory/mcp Verified 200
http (plaintext) http://mcp.firmen.directory/mcp HTTPS enforced 301 https://mcp.firmen.directory/mcp
MCP tools · 2 exposed · ~777 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
get_company ~255

Use this when the user wants the register facts of one company that search_companies returned: call it with that result's id. It returns legal form, UID (Switzerland) or Firmenbuch number (Austria), seat, status, founding or registration date and trade. For legal persons it adds the registered purpose, and for Swiss legal persons the capital and former names. For listings maintained by the owner it also returns the owner's short description, website and public phone number. An average star rating with the number of reviews is included when the company has reviews. When the registers list the company, it also gives the LEI, the latest register entries of a legal person (SHAB publications in Switzerland, Firmenbuch entries in Austria), supervision by FINMA, a SECO licence for staff leasing or placement, and a Swissmedic registration for medical devices; a register that does not list the company is not mentioned, and its absence says nothing. Do not guess an id: get it from search_companies first.

NameTypeReqDescription
idstringyesThe id of a result from search_companies, e.g. "ch:CHE123456789", "at:123456a" or "l:firmen-slug".
NameTypeReqDescription
companyobjectyes–
langstringyes–
noticestringyes–
rating_notestring––
sourcesarrayyes–

No examples provided.

search_companies ~522

Use this when the user asks about a company in Switzerland, Austria or Germany: whether it exists or is still registered, its legal form, UID or Firmenbuch number, seat or former name, or when they want companies of a trade in a town, postcode, canton or Bundesland they name. It searches the FIRMEN.directory company directory: commercial-register entries for Switzerland (Zefix) and Austria (Firmenbuch), plus listings maintained by business owners in Switzerland, Austria and Germany. Each result has company-level facts (legal form, UID or Firmenbuch number, seat, trade), a link to the profile and the id for get_company. Listings maintained by the owner also carry the owner's short description; results may carry an average star rating with the number of reviews, and the distance for searches near the user. Do not use it to find persons, owners or officers, for contact details of register entries, for insolvency or deletion lists, or for credit information: the directory has none of these.

NameTypeReqDescription
countrystring–Restrict to one country when the user names it.
limitinteger–Number of results, 1–8. Default 5.
namestring–Company name or part of it, at least 3 letters, e.g. "Muster Treuhand".
near_userboolean–True only when the user asks for companies near them and names no place. The coarse location the host provides is used; never ask the user for coordinates.
pageinteger–Result page, 1–3. Default 1.
placestring–Town or postcode of the company's seat, e.g. "Frauenfeld", "Zürich" or "8400": the town under its local name in Latin letters, whatever language the user writes in ("Zürich" for "Zurigo", "Genève" fo…
regionstring–Swiss canton (name or code, e.g. "Thurgau", "TG"), Austrian Bundesland (e.g. "Tirol") or German Land, when the user names one.
tradestring–Trade or line of business as a German word, e.g. "Elektriker", "Treuhand", "Restaurant". Translate it when the user writes in another language: "Sanitär" for "plumber", "plombier" or "idraulico".
NameTypeReqDescription
interpretedobjectyes–
langstringyes–
messagestring––
noticestringyes–
orderingstringyes–
ranking_urlstringyes–
rating_notestring––
resultsarrayyes–
sourcesarrayyes–
trade_suggestionsarray––

No examples provided.

Install

How do I install the FIRMEN.directory MCP server?

FIRMEN.directory is a hosted endpoint at https://mcp.firmen.directory/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 · mcp.firmen.directory

# add to Claude Code
claude mcp add --transport http directory-firmen-firmen-directory 'https://mcp.firmen.directory/mcp'
Common questions

What is the FIRMEN.directory MCP server?

FIRMEN.directory is an MCP server listed in the public MCP registry as directory.firmen/firmen-directory. Swiss and Austrian company register facts and owner-maintained listings, each with its source. This page covers its hosted endpoint (https://mcp.firmen.directory/mcp).

Is the FIRMEN.directory MCP server safe to use?

FIRMEN.directory scores 81 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 FIRMEN.directory MCP server expose?

FIRMEN.directory exposes 2 tools: search_companies, get_company. Their descriptions and schemas cost roughly 777 tokens of context every time the server is loaded.

Does the FIRMEN.directory MCP server require authentication?

No. We connected to FIRMEN.directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FIRMEN.directory MCP server still maintained?

FIRMEN.directory 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 FIRMEN.directory MCP server?

VerifyMCP ran 14 checks on FIRMEN.directory, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.