amtsblatt-mcp
Summary: This MCP server lets you search and read official Swiss gazette publications (SHAB + 27 cantonal gazettes) across released "green" rubrics only, with personal-data rubrics deliberately excluded.
Search publications (
gazette_search_publications) by keyword, rubric, sub-rubric, canton, and date range across all released rubrics — no person-name search exists.Search + fetch full texts in one call (
gazette_search_detailed) for the top 1–5 hits, fetched in parallel.Search public tenders (
gazette_search_procurement) in cantonalOB-*rubrics plus VS/OW/SH sub-rubrics; explains simap.ch routing for cantons like ZH instead of returning empty.Retrieve a publication's full official text (
gazette_get_publication) by UUID, with a post-fetch green-rubric re-check.Discover the taxonomy (
gazette_list_rubrics) to see which rubrics exist and which are servable, or all with reasons for blocked ones.Check source health (
gazette_source_status) for reachability, latency, cache age, and scope metrics.Filter and shape results via canton, date windows (Europe/Zurich), pagination, language preference,
only_language, andinclude_inactivefor archived procurement.Choose output format — Markdown (default) or JSON — with attribution and provenance on every response.
Rely on safety guarantees — fail-closed allow-list, explanatory refusals for blocked rubrics, no person-data entry points, and no persistence beyond the taxonomy cache.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@amtsblatt-mcp Search for public IT tenders in Basel-Stadt in the last 3 months"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🇨🇭 Part of the Swiss Public Data MCP Portfolio
📰 amtsblatt-mcp
MCP server for amtsblattportal.ch — the Swiss official gazette portal (SHAB + 27 cantonal gazettes). Public procurement and official notices, person-data rubrics excluded by design.
Overview
The Amtsblattportal publishes roughly 2.79 million official notices: public procurement, cantonal and communal announcements, enactments, spatial planning — and also bankruptcies, debt collection, inheritance calls and civil-status records naming natural persons.
This server exposes only the first group. Rubrics carrying systematic natural-person data are not queryable, and no tool accepts a person's name, birth date or address. That is a deliberate data-protection decision, explained in Data Protection & Scope.
Anchor demo query: "Which public tenders did canton Ticino publish this month?"
Demo
→
gazette_search_procurement(canton="TI", only_language=True, language="it") → gazette_get_publication(id=…)
For procurement in any other canton — including Zürich, Bern and Basel-Stadt —
use swiss-procurement-mcp;
see Boundary with swiss-procurement-mcp.
Related MCP server: ch-eli-mcp
Features
Fail-closed green allow-list — 49 released rubrics out of 152; everything else is blocked by default, including rubrics the upstream adds later
Explanatory refusals — a blocked rubric returns why, never a silent empty result and never a workaround hint
Procurement-aware — knows that only AR and TI still publish tenders here, that BS wound down during 2024 and BL/VS are historical archives, that
OB-ZGwas never filled after the simap switch, and that ZH routes everything through simap.ch — so it explains instead of returning nothing. Activity is measured, not read off the rubric labelDeadline arithmetic in Europe/Zurich, the legally relevant timezone
Honest multilingual counts — the portal publishes one record per language with a different publication number each; identical editions are collapsed, translated ones are reported via
language_mixrather than guessed at, andonly_language=Truegives a single-language viewDefensive XML parsing — the schema is per-sub-rubric; no rubric-specific path is hard-coded, and entity-escaped HTML bodies are unescaped and stripped
Egress allow-list, retry with backoff, structured JSON logging
Markdown or JSON output with per-response attribution +
provenance
Prerequisites
Python 3.11+
No API key. The read API of amtsblattportal.ch is freely accessible.
Installation
pip install amtsblatt-mcp
# or, without installing:
uvx amtsblatt-mcpFrom source:
git clone https://github.com/malkreide/amtsblatt-mcp
cd amtsblatt-mcp
pip install -e ".[dev]"Configuration
Claude Desktop
{
"mcpServers": {
"amtsblatt": {
"command": "uvx",
"args": ["amtsblatt-mcp"]
}
}
}Cloud deployment (streamable-http)
export MCP_TRANSPORT=streamable-http
export MCP_API_KEY="$(openssl rand -hex 32)" # mandatory — fails loud if unset
export PORT=8000
amtsblatt-mcpThe endpoint is /mcp.
Migrating from SSE. Until 0.18.0 this server spoke SSE only, on
/sse+/messages. MCP spec2026-07-28reclassifies HTTP+SSE as deprecated with a twelve-month removal window and removes protocol-level sessions, so streamable-http is now the default.MCP_TRANSPORT=ssestill works and still carries the full bearer-auth, rate-limit and CORS stack — it logs a warning at startup naming the deadline. Update the client URL when you switch: the path change is the part that breaks silently.
Variable | Default | Purpose |
|
|
|
|
| HTTP bind address. Defaults to loopback; set |
| (on) | streamable-http runs with no session tracking at all — the native mode of spec |
| (unset) | Comma-separated origins allowed to call the endpoint from a browser. Unset means no cross-origin browser access at all — stdio and non-browser clients are unaffected. |
| — | Bearer token; required on every HTTP transport |
|
| Sliding-window rate limit |
|
| Taxonomy cache TTL (seconds) |
|
|
|
Logging
Built on structlog. Every event emitted during a
tool call carries that call's correlation_id, bound via contextvars — so a
retry or an egress denial logged deep in the HTTP path can be joined to the
request that caused it, without threading context through every signature.
Level | Emitted when |
| a tool call was entered ( |
| a tool call finished cleanly, with latency |
| upstream retry, egress denied, auth failure, rate limit |
| a tool call raised |
Records carry the exception type only — never its message and never an upstream response body.
{"event":"tool_call_started","tool":"gazette_search_procurement","correlation_id":"23221af26ae640c7","level":"debug","timestamp":"2026-07-27T22:20:07.494276Z"}
{"status":"ok","latency_ms":312,"event":"tool_call","tool":"gazette_search_procurement","correlation_id":"23221af26ae640c7","level":"info","timestamp":"2026-07-27T22:20:07.806Z"}Ship these to your SIEM and alert on auth_failed, rate_limited,
egress_denied, green_gate_violation and blocked_publication_requested —
the last two mean something tried to reach a rubric this server does not serve.
Available Tools
Tool | Signature | Notes |
|
| Green rubrics enforced. Without |
| same filters + | Aggregated. Search and full text for the top |
|
|
|
|
| Full official text from XML. Re-checks the rubric after fetching; content from a blocked rubric is discarded. |
|
|
|
|
| Reachability, latency, cache age, scope metrics. |
All tools are readOnlyHint=True.
Example use cases
Question | Tool chain |
Tenders in Ticino this quarter |
|
Procurement simap.ch does not have |
|
Tenders in any other canton | → use |
What is even queryable here? |
|
Why can't I search bankruptcies? |
|
Zoning changes in Zurich |
|
Full text of a notice |
|
Everything published about one company | → use |
Data Protection & Scope
The Amtsblattportal systematically publishes personal data of natural persons. Those publications are public — but making them systematically queryable by name through an AI agent is a repurposing the publication never intended, and a profiling instrument under the revised Swiss FADP (revDSG).
Four rules follow, and they are enforced in code, not in documentation:
Allow-list, never block-list. Not explicitly green ⇒ not queryable. New upstream rubrics are closed by default.
No person-based search entry in any tool signature.
No persistence. Publications have statutory deletion periods; a cache outliving them would actively undermine them. Only the taxonomy is cached.
Blocked ⇒ explained. Never a silent empty result, never a hint at circumvention.
What is excluded
🔴 Konkurse (KK), Schuldbetreibungen (SB), Schuldenrufe (LS, SR),
Nachlass (NA), Erbschaft/Testament/Ableben (ES, TE-*, VA-*),
Familie & Zivilstand (FZ-*, BV-*, BU-*), gerichtliche Vorladungen
(UV, GB-*, GE-*, SJ-BE), Baugesuche (BP-*), Grundbuch (GR-*),
Meldungskatalog GR (AA-GR).
🟡 Deferred: Steuerwesen, Anzeigen, Bewilligungen, Bildungs- und Kirchenwesen and the general catch-all rubrics.
The full audit trail — including three documented extensions to the source
specification — is in docs/rubric-classification.md.
How much each decision covers is measured, not estimated.
docs/coverage-matrix.md enumerates the source's own
rubric axis and marks this server's reach into it: 84.2 % of 2 804 063
publications are reachable, 12.6 % blocked by decision, 3.3 % still
unclassified. The insolvency group alone is 321 704 publications — present in
the source, out of reach here on purpose. Without that figure, "out of scope"
and "not in the source" read the same in a review, and this repository made
exactly that mistake once (see ARCH-003 in SECURITY.md).
The boundary with register-mcp
For publications about a specific company, use
register-mcp. It keeps full
rubric access — including a firm's own bankruptcy — but only ever keyed on a
company UID. A firm's insolvency is corporate data, not natural-person
profiling, and UID scoping makes name-based enumeration impossible.
amtsblatt-mcp has the opposite shape: broad search, narrow rubrics. It does
not expose the upstream uids parameter at all.
Boundary with swiss-procurement-mcp
simap.ch is the primary source for Swiss public procurement — all 26 cantons
plus the Confederation, with CPV and BKP codes, awards and publication history.
Use swiss-procurement-mcp
for procurement questions.
amtsblattportal.ch is the primary source for official notices — commercial register, spatial planning, enactments, cantonal and communal announcements. That is what this server is for; procurement is 6 of its 49 released rubrics.
Procurement here is largely a second publication of the same tenders, and
that is now measured rather than assumed. A publication's XML carries
<simapPublicationNumber> when it originates on simap.ch, which joins the two
corpora exactly. Over the full 2026 OB-TI corpus, 503 of 546 records (92.1%)
carry one; three of the six OB-* rubrics say as much in their own labels
(OB-BL — "über Simap importiert (I N A K T I V)").
The exception is small and sharply bounded: AR-VS40 (Valais, 150 awards),
AR-OW40 (Obwalden, 7), BA-SH40 (Schaffhausen, 2) and the Ticino sub-rubric
OB-TI65 ("Avvisi di gara non CIAP") carry no simap reference at all.
That is the one part of this portal's procurement coverage swiss-procurement-mcp
cannot reach, and gazette_search_procurement serves it for cantons VS, OW and
SH even though they have no active OB-* rubric. Numbers and method in
docs/simap-overlap.md.
The two servers stay separate on purpose: different sources, different reuse
terms, and a fail-closed rubric gate that only means something while it covers
every tool in the server. See
docs/procurement-coverage.md for the numbers.
Maturity & phase
Phase 1 — read-only. All six tools are read-only; there is no write path and none is planned. See ROADMAP.md for the phase-specific backlog, what is deliberately not planned, and what a phase transition would require.
The scope restriction that matters most here is not the phase but the green allow-list — rubrics carrying systematic natural-person data are not queryable, enforced in code and re-checked after every fetch. That does not change with phase. See Data Protection & Scope.
SDK and dependency updates arrive as Dependabot PRs, so a breaking protocol or SDK change is reviewed deliberately rather than drifting in silently.
Architecture
Claude / MCP client
│
amtsblatt-mcp
│
┌────────┴────────┐
│ green gate │ ← rubrics.py: fail-closed allow-list
└────────┬────────┘ (checked at the tool AND at the query builder)
│
┌────────┴────────┐
│ param allow- │ ← Silent Ignore guard
│ list + quirks │ ← Silent Empty guard (taxonomy validation)
└────────┬────────┘ ← plausibility guard (corpus-size check)
│
┌────────┴────────┐
│ egress allow- │
│ list (httpx) │
└────────┬────────┘
│
amtsblattportal.ch/api/v1
/publications · /publications/{id}/xml · /rubrics · /tenantsArchitecture A (live-API-only). The endpoints answer stably without authentication, so no bulk dump is maintained.
Verified upstream quirks (live-checked 2026-07-20)
Quirk | Behaviour | Defence |
Silent Ignore | An unknown parameter name returns HTTP 200 and the full corpus. | Query params built exclusively from |
Silent Empty | An unknown rubric value returns HTTP 200 with | Every code validated against the taxonomy before the call. |
Metadata only | The list endpoint and | Full text only via |
Sorting ignored |
| Sorted client-side. |
Missing | Returns 401, not 400 — it does not mean credentials are required. | Always injected; the 401 message says so. |
No page-size cap |
| Client-side cap of 100. |
Inconsistent plurals |
| Exact spellings encoded, not a pluralisation rule. |
Known Limitations
Uneven cantonal coverage. Only 16 of 29 mandates expose their own rubric taxonomy; AG, FR, GE, GL, JU, LU, NE, UR are still incomplete.
Deletion periods. Publications drop out of the API over time — hence pass-through only.
Procurement boundary. Most cantons, including Zürich, route tenders through simap.ch, outside this portal. There is no
OB-ZH, and no CPV classification exists here. What this portal has and simap does not is listed indocs/simap-overlap.md;gazette_get_publicationreportssimap_publication_numberso a mirror is distinguishable from an original.Procurement coverage, measured (
publicationStates=PUBLISHED, 2026-07-27, records per calendar year — reproduce withpython scripts/measure_procurement_coverage.py):Rubric
2022
2023
2024
2025
2026
Latest
Status
OB-TI517
491
625
607
546
2026-07-27
active
OB-AR95
85
79
56
40
2026-05-22
active
OB-BS1 149
1 058
319
15
2
2026-05-20
wound down during 2024
OB-VS0
1 052
1
0
0
2024-01-05
archive — simap import until end of 2023
OB-BL0
74
0
0
0
2023-03-30
archive — labelled «I N A K T I V»
OB-ZG0
0
0
0
0
—
never filled
Only TI and AR still publish actively.
OB-BSis the instructive case: its label is a plain "Öffentliches Beschaffungswesen" with no inactive marker, so only the volume reveals the migration — which is whyactiveis measured, never read. Useinclude_inactive=Trueto reach the BS, BL and VS archives. Details indocs/procurement-coverage.md.No push. Polling only; no subscription or webhook mechanism.
Legally binding text is the signed PDF, not this API.
MCP Protocol Version
Served via the |
|
Served via the per-request envelope |
|
Who picks | Over HTTP, the |
| Name |
Pinned in |
|
SDK |
|
Cache hints |
|
The MCP Python SDK negotiates the protocol version in the session layer and offers no constructor parameter for it, so the version cannot be pinned by configuration. It is pinned as a declared constant and enforced by detection:
At runtime, a mismatch logs a
protocol_version_driftevent atWARNING. The server keeps working.In CI,
tests/test_protocol_version.pyfails.
An SDK bump should break our build, not the runtime of someone who upgraded
mcp in their own environment.
That both eras are actually served — through the bearer gate, rate limit and
CORS, not just named in a constant — is measured in
tests/test_modern_era.py: raw 2026-07-28 requests with routing headers, an
mcp.Client in auto mode over HTTP and over stdio, and the legacy handshake
as the negative control.
Update policy
Dependabot opens SDK update PRs monthly (
.github/dependabot.yml).When an update moves the protocol version, the CI test fails. The fix is not to edit the constant blindly: read the spec changelog, verify the server still behaves — especially the green allow-list invariants — then bump the constant, this section and
CHANGELOG.mdin one commit.Protocol-version bumps are called out explicitly in
CHANGELOG.md, not folded into a dependency-bump line.
Cache hints
Spec 2026-07-28 gives every cacheable result a ttlMs and a cacheScope.
The SDK defaults both to «immediately stale, never shared», so a server that
passes no cache_hints is not neutral — it asks every client to re-list on
every connection. This server's tool list is registered at import and identical
for every caller, so it is announced as cacheable for five minutes and
shareable across authorization contexts (CACHE_HINTS in _app.py).
public rests on that second property, not on convenience: the green
allow-list is enforced per request inside the tools, never by hiding a tool from
a caller. The day a tool list becomes caller-dependent, the scope has to become
private in the same commit.
Primitives: tools only
This server exposes tools and neither resources nor prompts. A decision, not an omission (ARCH-008).
Why not resources. Resources address identifiable, listable content the client can enumerate and cache. This corpus is 2.79 million publications that grows daily, and — more importantly — not all of it is servable. Rubrics carrying systematic personal data are excluded by design, and that exclusion is enforced at two points: a pre-request green gate on the filters, and a post-fetch gate on the returned document.
A resource URI would put a publication id in the client's hands as an enumerable address. Since ids are opaque, the rubric behind one cannot be known until the document is fetched — which is exactly why the post-fetch gate exists. Exposing publications as resources would mean either enumerating ids we have not gated yet, or gating at fetch time anyway, at which point the resource abstraction buys nothing and costs a second content path to keep the guarantee on. This repo has already learned that lesson once: the aggregated tool needed the gate extracted into a shared helper precisely because a second path to content is where such guarantees quietly stop holding.
One candidate was checked concretely:
Candidate | Why it stays a tool |
| Genuinely resource-shaped — a finite, slow-changing taxonomy, already cached with a TTL. But its whole purpose is to communicate that listed ≠ queryable: it renders traffic-light classes and the reason each blocked rubric is blocked. As a resource that framing would be a document the model may or may not read; as a tool it is an answer to a question the model asked. |
Why not prompts. Question templates would duplicate guidance the tool docstrings already carry, in a second place that can drift out of sync with the allow-list. Given that the docstrings are what tell the model which rubrics are reachable, one source is safer than two.
Return shapes: rendered text, not models
Tools return str — Markdown by default, JSON via response_format='json' —
rather than Pydantic models. This is a documented deviation from SDK-002,
made deliberately rather than by neglect.
The rendered output is not a serialisation of an internal object; it is composed
for the reader. It carries the provenance line, the scope statement
(green_rubrics_only), the deduplication warning when language variants were
merged, and the explanation a blocked rubric returns instead of data. Those
are the parts that keep the model from drawing wrong conclusions, and they are
prose, not fields.
Returning a model would either drop them or smuggle them back in as string
fields, which is the same thing with more ceremony. The json format already
covers the machine-readable case for callers that want it.
What would change this: a caller that needs to compute over results rather than read them. At that point the right move is typed models on the JSON path specifically, not a wholesale change of what every tool returns.
Testing
pip install -e ".[dev]"
PYTHONPATH=src pytest tests/ -m "not live" # 75 tests, no network
PYTHONPATH=src pytest tests/ -m live # hits the real API
ruff check src/ tests/ scripts/
ruff format --check src/ tests/ scripts/
python scripts/check_version_sync.pyThese are the same gates CI runs, over the same directories. The dev extra
pins ruff to the version CI installs, so a local run and a CI run agree.
The suite covers the mandatory portfolio set: green-rubric search with source URL, blocked rubric → explanation with zero HTTP calls, canton filtering, Europe/Zurich deadline arithmetic against a fixed "today", pagination across a page boundary, language deduplication, boolean normalisation, and API-unreachable handling. Fixtures are shortened real responses, consistently anonymised — no real personal data.
Project Structure
amtsblatt-mcp/
├── src/amtsblatt_mcp/
│ ├── rubrics.py # Fail-closed green allow-list — the scope decision
│ ├── server.py # MCPServer, 5 tools, quirk guards, XML parsing
│ ├── _log.py # Structured JSON logging + per-tool call events
│ ├── _middleware.py # Bearer auth + sliding-window rate limit (SSE only)
│ └── _otel.py # Optional OpenTelemetry wiring
├── tests/
│ ├── test_allowlist.py # Data-protection invariants (own CI job)
│ ├── test_search.py # Search, procurement, pagination, dedup, errors
│ ├── test_publication.py # XML parsing, deadlines, egress allow-list
│ └── fixtures.py # Anonymised real responses
├── docs/
│ ├── rubric-classification.md # Why each of the 152 rubrics is open/closed
│ ├── procurement-coverage.md # Measured OB-* volume; why `active` is measured
│ ├── coverage-matrix.md # Measured reach: which part of the corpus the tools cover
│ └── simap-overlap.md # Mirror vs. original, joined on simapPublicationNumber
├── scripts/
│ ├── measure_procurement_coverage.py
│ └── measure_coverage_matrix.py
├── Dockerfile · compose.yaml # Hardened, non-root, read-only container
└── server.json # MCP registry manifestChangelog
See CHANGELOG.md.
Contributing
See CONTRIBUTING.md. Changes to
src/amtsblatt_mcp/rubrics.py require an
explicit rationale in the PR description: releasing a rubric is a
data-protection decision, not a feature.
Security
See SECURITY.md for reporting and operator hardening notes.
License
MIT — see LICENSE. Data-source notice: NOTICE.md.
Data source: amtsblattportal.ch, operated by SECO / State Secretariat for Economic Affairs on behalf of the Swiss Confederation. Freely usable, but without warranty of completeness or accuracy. Only the signed PDF of a publication is legally binding.
Author
Hayal Oezkan · malkreide
Credits & Related Projects
Part of the Swiss Public Data MCP Portfolio:
register-mcp— Zefix commercial register with a company-UID join to the gazettes
Available Tools
6 toolsgazette_get_publicationARead-onlyIdempotent
<use_case>Retrieve the full text of one publication once you have its id from a search. Refuses ids whose rubric is not released, after fetching — the rubric is not knowable from the id alone.</use_case>
Einzelne Publikation inkl. amtlichem Volltext (aus dem XML, defensiv geparst).
Die Listen-API liefert nur Metadaten — der eigentliche Inhalt steht
ausschliesslich im rubrikspezifischen XML unter /publications/{id}/xml.
Das Schema ist pro Subrubrik verschieden; Pflichtfelder sind meta und der
Publikationstext, bei HR-Rubriken zusätzlich die Firmenangaben. Alles
Übrige landet best-effort in additional_fields.
Nach dem Abruf wird die Rubrik der Publikation erneut gegen die Freigabe-Liste geprüft: eine ID aus einer gesperrten Rubrik liefert die Scope-Erklärung statt des Inhalts.
Args: params (PublicationInput): - id (str): Publikations-ID (UUID) - response_format (str): 'markdown' oder 'json'
Returns: str: Volltext, Metadaten, allfällige Eingabefrist und Zusatzfelder.
Inputs: params (required). Returns: result
gazette_list_rubricsARead-onlyIdempotent
<use_case>Discover which rubrics exist and which this server serves, before searching. Call this when a search returns nothing to tell "no such publications" apart from "that rubric is deliberately not served".</use_case>
Rubrik-Taxonomie des Amtsblattportals mit Ampel-Klassierung.
Voraussetzung für gültige Filter: Rubrik-Codes werden in den Such-Tools gegen diese Taxonomie UND gegen die Freigabe-Liste validiert. Standardmässig werden nur die erschlossenen («grünen») Rubriken gezeigt.
Mit rubric_class='all' erscheint die vollständige Taxonomie inklusive der
gesperrten Rubriken mit Begründung — zur Transparenz über den Scope-Entscheid.
Aufgeführt zu sein bedeutet nicht durchsuchbar zu sein; nur 🟢 ist abfragbar.
Args: params (RubricsInput): - language (str): 'de', 'fr', 'it', 'en' - rubric_class (str): 'green' (Standard) oder 'all' - response_format (str): 'markdown' oder 'json'
Returns: str: Rubriken mit Code, Name, Ampel-Klasse und Subrubriken.
Inputs: params (required). Returns: result
gazette_search_detailedARead-onlyIdempotent
<use_case>Answer a question needing both the hit list and each hit's full text in one step. Prefer this over a search followed by N gazette_get_publication calls.</use_case>
Sucht Publikationen UND liefert den Volltext der obersten Treffer — ein Aufruf.
Aggregierter Einstieg für den häufigen Fall «finde Bekanntmachungen und zeig
mir, was drinsteht». Ohne dieses Tool braucht dieselbe Frage 1 + N Aufrufe:
einmal gazette_search_publications, dann gazette_get_publication je
Treffer. Hier laufen die Detailabrufe parallel, die Wartezeit ist also
die des langsamsten Einzelabrufs statt ihrer Summe.
Filter und Semantik sind identisch mit gazette_search_publications —
einschliesslich der Freigabeliste: ohne rubric werden alle freigegebenen
Rubriken injiziert, und jeder abgerufene Volltext durchläuft dasselbe
Post-Fetch-Green-Gate. Eine Publikation aus gesperrter Rubrik wird auch hier
verworfen und nie gerendert.
Für Ausschreibungen mit Volltext in einem Aufruf: rubric='OB-<Kanton>'
setzen, z.B. rubric='OB-TI'. gazette_search_procurement bleibt der
bequemere Einstieg, wenn nur die Trefferliste gebraucht wird — es kennt die
Kanton-zu-Rubrik-Auflösung und die inaktiven Kantone.
Wann stattdessen die Einzeltools:
Nur die Trefferliste gewünscht →
gazette_search_publications(billiger).Volltext zu einer bekannten ID →
gazette_get_publication.Mehr als 5 Volltexte → suchen und die gewünschten gezielt einzeln holen.
Args:
params (DetailedSearchInput):
- top_n (int): Anzahl Volltexte (1–5, Standard 3)
- übrige Felder: identisch zu gazette_search_publications
Returns:
str: Trefferliste plus Volltext der obersten top_n Publikationen.
Inputs: params (required). Returns: result
gazette_search_procurementARead-onlyIdempotent
<use_case>Find public tenders published in the gazette (Submissionen) — the procurement-specific entry point. Note only AR, BS, TI, ZG, BL and VS mirror tenders here; for full Swiss coverage including Zurich use swiss-procurement-mcp.</use_case>
Sucht öffentliche Ausschreibungen (Beschaffungswesen/Submissionen).
Beschaffung ist ausschliesslich eine KANTONALE Rubrik (OB-<Kanton>), nicht
föderal. Nur wenige Kantone publizieren sie hier: AR und TI (aktiv) sowie
BS, BL, VS, ZG (inaktiv — BS/BL/VS nur Archiv, ZG leer).
WICHTIG — Spiegel vs. Original: Die OB-*-Rubriken sind praktisch
vollständig Zweitpublikationen von simap.ch-Ausschreibungen (gemessen über
den OB-TI-Jahrgang 2026: 92,1 % tragen eine simap-Publikationsnummer). Wer
Beschaffung sucht, ist mit swiss-procurement-mcp an der Primärquelle
besser bedient — alle 26 Kantone plus Bund, mit CPV- und BKP-Codes,
Zuschlägen und Publikationsverlauf.
Was es NUR hier gibt, sind die Beschaffungs-Subrubriken AR-VS40 (Wallis,
Zuschläge), AR-OW40 (Obwalden) und BA-SH40 (Schaffhausen) sowie die
Ticiner Subrubrik OB-TI65 («Avvisi di gara non CIAP»): keine davon trägt
eine simap-Nummer. Kanton VS, OW und SH liefern deshalb Treffer, obwohl sie
keine aktive OB-*-Rubrik haben. Die meisten Kantone —
inklusive Zürich —
publizieren Ausschreibungen über simap.ch, das NICHT Teil dieser Quelle ist;
eine Abfrage für einen solchen Kanton liefert eine Erklärung statt eines
leeren Ergebnisses. Die Quelle kennt keine CPV-Codes.
Args: params (ProcurementInput): - keyword (Optional[str]): Freitext (kein CPV-Code) - canton (Optional[str]): Kantonskürzel; ohne Angabe alle aktiven - date_start / date_end (Optional[str]): Zeitraum YYYY-MM-DD - include_inactive (bool): inaktive Rubriken (BL/BS/VS/ZG) einbeziehen - limit (int): 1–100 (Standard 20), page (int): 0-basiert - language (str), only_language (bool), response_format (str)
Hinweis zur Trefferzahl: Ticino publiziert überwiegend it/fr, Appenzell A.Rh.
de/fr — je Sprache ein eigener Datensatz mit eigener Publikationsnummer.
Identische Titel werden zusammengefasst, übersetzte bleiben getrennt; die
Trefferzahl kann daher über der Zahl verschiedener Ausschreibungen liegen.
only_language=True erzwingt eine einzelne Sprachfassung.
Returns: str: Ausschreibungen (neueste zuerst) mit Datum, Kanton, Titel, Sprache, ID.
Inputs: params (required). Returns: result
gazette_search_publicationsARead-onlyIdempotent
<use_case>Search the released gazette rubrics by keyword, rubric, canton and date — the general entry point when the question is "what was officially published about X?". Combine rubric with canton: a bare rubric filter is silently ignored upstream.</use_case>
Sucht amtliche Publikationen im Amtsblattportal (SHAB + kantonale Amtsblätter).
Durchsucht ausschliesslich die freigegebenen («grünen») Rubriken: Handels- register, öffentliche Beschaffung, kantonale und kommunale Bekanntmachungen, Beschlüsse und Rechtsetzung, politische Rechte, Raumplanung sowie Umwelt/ Verkehr/Energie. Rubriken mit systematischen Personendaten — Konkurse, Schuldbetreibungen, Erbschaft, Zivilstand, gerichtliche Vorladungen, Baugesuche — sind bewusst nicht erschlossen und liefern eine Erklärung statt Daten. Ein Personennamen-Sucheinstieg existiert nicht.
Ohne rubric werden alle freigegebenen Rubriken injiziert, sodass eine
reine Stichwortsuche niemals eine gesperrte Rubrik erreichen kann.
Args: params (SearchInput): - keyword (Optional[str]): Volltext-Suchbegriff - rubric / sub_rubric (Optional[str]): freigegebene Codes - canton (Optional[str]): Kantonskürzel - date_start / date_end (Optional[str]): Zeitraum YYYY-MM-DD - limit (int): 1–100 (Standard 20), page (int): 0-basiert - language (str): bevorzugte Sprache - only_language (bool): nur diese Sprachfassung - response_format (str): 'markdown' oder 'json'
Hinweis zur Trefferzahl: Das Portal publiziert eine Bekanntmachung je Sprache
als eigenen Datensatz mit eigener Publikationsnummer. Sprachfassungen mit
identischem Titel werden zusammengefasst, übersetzte bleiben getrennt — die
Trefferzahl kann daher über der Zahl verschiedener Bekanntmachungen liegen.
language_mix weist die Verteilung aus, only_language=True erzwingt eine
einzelne Sprachfassung.
Returns: str: Trefferliste mit Datum, Kanton, Rubrik, Titel, Sprache, ID und URL.
Inputs: params (required). Returns: result
gazette_source_statusARead-onlyIdempotent
<use_case>Check whether amtsblattportal.ch is reachable and what the released scope is. Call this when a search returns nothing and you need to distinguish an empty result from a source that could not be asked — the two are not the same answer.</use_case>
Status des Amtsblattportals, Cache-Alter und Umfang der Freigabe-Liste.
Prüft die Erreichbarkeit des Upstreams, meldet das Alter des Taxonomie-Caches und wie viele Rubriken erschlossen sind.
Args: params (StatusInput): - response_format (str): 'markdown' oder 'json'
Returns: str: Erreichbarkeit, Latenz, Cache-Alter und Scope-Kennzahlen.
Inputs: params (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool serves a distinct purpose: general search, detailed search with full text, procurement-specific search, single publication retrieval, rubric listing, and source status. No two tools overlap in functionality, making agent selection unambiguous.
All tools follow a consistent 'gazette_verb_noun' pattern (e.g., gazette_search_publications, gazette_list_rubrics). The naming is predictable and uniform, with clear verb-noun pairs.
With 6 tools, the server is well-scoped for interacting with the Swiss official gazette. Each tool is justified, covering search, retrieval, status, and metadata, without unnecessary extras.
The tool set covers all essential operations: searching (list and detailed), single publication retrieval, rubric discovery, and status checks. Minor gaps include lack of bulk retrieval beyond 5 items, but the domain is well-served.
Maintenance
Related MCP Connectors
simap MCP — Swiss public procurement tenders and awards (keyless).
opendata.swiss MCP — Switzerland's federal open-data portal (CKAN catalogue).
TED MCP Server: Real-time EU public tenders access. https://www.lexsocket.ai/
Poland public procurement MCP — official e-Zamówienia notice feed (keyless).
Related MCP Servers
- AlicenseBqualityBmaintenanceSwiss open data MCP server — transport, weather, geodata, companies, etc,. Zero API keys.94431 npm28MIT
- AlicenseAqualityBmaintenanceMCP server for Swiss federal legislation metadata via Fedlex, enabling search and retrieval of act details with ELI URIs, SR numbers, and multilingual support.3Apache 2.0

entscheidsuche-mcpofficial
AlicenseNot gradedqualityCmaintenanceMCP server for Swiss court decisions, enabling full-text search and retrieval of published decisions from all Swiss federal and cantonal courts in German, French, and Italian.4MIT- AlicenseAqualityBmaintenanceMCP Server for Canton Zurich legislation (ZH-Lex) — full-text search, article extraction, and education law tools for ~970 cantonal laws.8MIT