# FIRMEN.directory (remote · mcp.firmen.directory)

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

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.firmen.directory`: 81/100 (this document), [markdown](https://verifymcp.io/servers/directory-firmen-firmen-directory/mcp.md), [page](https://verifymcp.io/servers/directory-firmen-firmen-directory/mcp)

## Channel facts

- Endpoint: `https://mcp.firmen.directory/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

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

### Claude

```bash
claude mcp add --transport http directory-firmen-firmen-directory 'https://mcp.firmen.directory/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "directory-firmen-firmen-directory": {
      "url": "https://mcp.firmen.directory/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "directory-firmen-firmen-directory": {
      "type": "http",
      "url": "https://mcp.firmen.directory/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.directory-firmen-firmen-directory]
url = "https://mcp.firmen.directory/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "directory-firmen-firmen-directory": {
      "type": "remote",
      "url": "https://mcp.firmen.directory/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add directory-firmen-firmen-directory --url 'https://mcp.firmen.directory/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  directory-firmen-firmen-directory:
    url: "https://mcp.firmen.directory/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "directory-firmen-firmen-directory": {
      "Transport": "http",
      "Url": "https://mcp.firmen.directory/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add directory-firmen-firmen-directory -t streamable-http -u 'https://mcp.firmen.directory/mcp'
```

### Other

```json
{
  "mcpServers": {
    "directory-firmen-firmen-directory": {
      "type": "http",
      "url": "https://mcp.firmen.directory/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 81, +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.

### 2026-11-18 (score 80, +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.

### 2026-11-16 (score 79, +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.

### 2026-11-13 (score 78, +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.

### 2026-11-11 (score 77, +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.

### 2026-11-09 (score 76, +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.

### 2026-11-08 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 75)

First indexed and scored.

## MCP tools (2)

### `search_companies` (~522 tokens)

Search companies

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.

Input parameters:

- `country` (string): Restrict to one country when the user names it.
- `limit` (integer): Number of results, 1–8. Default 5.
- `name` (string): Company name or part of it, at least 3 letters, e.g. "Muster Treuhand".
- `near_user` (boolean): 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.
- `page` (integer): Result page, 1–3. Default 1.
- `place` (string): 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…
- `region` (string): Swiss canton (name or code, e.g. "Thurgau", "TG"), Austrian Bundesland (e.g. "Tirol") or German Land, when the user names one.
- `trade` (string): 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".

Output parameters:

- `interpreted` (object)
- `lang` (string)
- `message` (string)
- `notice` (string)
- `ordering` (string)
- `ranking_url` (string)
- `rating_note` (string)
- `results` (array)
- `sources` (array)
- `trade_suggestions` (array)

### `get_company` (~255 tokens)

Show company

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.

Input parameters:

- `id` (string, required): The id of a result from search_companies, e.g. "ch:CHE123456789", "at:123456a" or "l:firmen-slug".

Output parameters:

- `company` (object)
- `lang` (string)
- `notice` (string)
- `rating_note` (string)
- `sources` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/directory-firmen-firmen-directory/mcp#diagnostics

## Score history

- 2026-11-21: 81
- 2026-11-20: 81
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 78
- 2026-11-14: 78
- 2026-11-13: 78
- 2026-11-12: 77
- 2026-11-11: 77
- 2026-11-10: 76
- 2026-11-09: 76
- 2026-11-08: 75
- 2026-11-07: 75

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

## Links

- Remote endpoint: https://mcp.firmen.directory/mcp
- Website: https://firmen.directory/
- Changelog RSS feed: https://verifymcp.io/servers/directory-firmen-firmen-directory/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/directory-firmen-firmen-directory/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/directory-firmen-firmen-directory/mcp.json
- HTML version of this page: https://verifymcp.io/servers/directory-firmen-firmen-directory/mcp
