🇨🇭 Part of the Swiss Public Data MCP Portfolio

💡 swiss-ip-mcp

MCP Server for Swiss Intellectual Property Data (IGE/IPI)

🇩🇪 Deutsche Version → README.de.md

Overview

swiss-ip-mcp is a Model Context Protocol (MCP) server that gives AI models structured, language-driven access to the Swiss intellectual property register Swissreg, operated by the Swiss Federal Institute of Intellectual Property (IGE/IPI).

It is the successor to patent-mcp and covers all available domains of the Swissreg Datadelivery API: trademarks, patents, patent publications, and supplementary protection certificates (SPC/ESZ).

This server is model-agnostic. It works with Claude, GPT-4, Llama, and any other MCP-compatible client – not just Claude Desktop.

Example Queries

The real power is natural language. Instead of manually searching the register, just ask a question:

"Which trademarks does the City of Zurich hold at the IGE?"

"Is the name 'Learning City Zurich' registered as a trademark in Switzerland?"

"Which pharmaceutical companies have filed Swiss patents in the last six months?"

"Show me all trademark applications in the education sector (Nice class 41) since January 2025."

"What supplementary protection certificates does Novartis hold in Switzerland?"

Covered Domains

Note: Design search is not yet available in the Swissreg Datadelivery API.

Tools (11)

Resources & Prompts

Beyond tools, the server exposes two more MCP primitives:

Resources (read-only metadata, swissip:// URI scheme):

Prompts (curated workflow templates):

Error semantics

Tool execution errors (API failures, timeouts, missing credentials) are returned with MCP isError: true and a masked, user-friendly message — internal details (stack traces, raw API bodies) go only to the server log. A specific number lookup that finds nothing is not an error: it returns a normal result with match_type: "none" and a message.

Project Phase

This server is in Phase 1 (read-only) of the MCP phased-rollout model: every tool is read-only and writes nothing. See ROADMAP.md for the phase plan and the prerequisites for any future write-capable phase.

Architecture

AI client (Claude Desktop, Cursor, VS Code + Continue, …)
         │
         │  MCP (stdio or SSE)
         ▼
   swiss-ip-mcp
         │
         │  HTTPS + OAuth2 (IGE IDP)
         ▼
  Swissreg Datadelivery API
  https://www.swissreg.ch/public/api/v1
         │
         ├── TrademarkSearch
         ├── PatentSearch
         ├── PatentPublicationSearch
         ├── SPCSearch
         └── UserQuota

Transport Modes

SSE is deprecated. Protocol revision 2026-07-28 reclassified the HTTP+SSE transport as Deprecated under the feature lifecycle policy (SEP-2596; it had been soft-deprecated since 2025-03-26). It stays available here for the twelve-month deprecation window — new deployments should use MCP_TRANSPORT=streamable-http.

Transport is selected at startup from the MCP_TRANSPORT environment variable (default stdio). The HTTP transports are served by uvicorn and honour:

The Mcp-Session-Id header is exposed via CORS so browser-based clients can read and echo it on follow-up requests.

Prerequisites

1. IGE credentials (free): Sign the terms of use and send the form by post to the IGE. Credentials are issued upon receipt.
2. Python 3.11 or later
3. uv (recommended) or pip

Installation

# Run directly with uv (recommended, no local installation needed)
uvx swiss-ip-mcp

# Local development installation
git clone https://github.com/malkreide/swiss-ip-mcp
cd swiss-ip-mcp
pip install -e ".[dev]"

Configuration

Environment Variables

export IGE_USERNAME="your_username"
export IGE_PASSWORD="your_password"

Claude Desktop

Open the config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "swiss-ip": {
      "command": "uvx",
      "args": ["swiss-ip-mcp"],
      "env": {
        "IGE_USERNAME": "your_username",
        "IGE_PASSWORD": "your_password"
      }
    }
  }
}

Other MCP Clients

swiss-ip-mcp is compatible with any MCP-capable client:

Cloud / Render.com (Streamable HTTP)

MCP_TRANSPORT=streamable-http \
  MCP_HOST=0.0.0.0 PORT=8000 \
  MCP_ALLOWED_ORIGINS="https://your-client.example" \
  MCP_ALLOWED_HOSTS="your-app.onrender.com" \
  IGE_USERNAME=... IGE_PASSWORD=... \
  swiss-ip-mcp

Security note: bind to 0.0.0.0 only inside a container or behind a reverse proxy. Always set MCP_ALLOWED_ORIGINS and MCP_ALLOWED_HOSTS for public deployments — this enables CORS scoping and DNS-rebinding protection. The endpoint is unauthenticated and serves only public IP-register data; do not place credentialed or non-public tools behind this transport without adding authentication first.

Docker / Kubernetes

A hardened multi-stage Dockerfile (non-root UID 10001, HEALTHCHECK on /health), a docker-compose.yml with resource limits, and Kubernetes manifests + an HAProxy sticky-session config under deploy/ are included.

docker compose up --build   # reads IGE_* from .env

See docs/deployment.md for hardening, resource limits and scaling (stateless vs. sticky-session) details.

Tests

# Unit tests (no credentials needed)
PYTHONPATH=src pytest tests/ -v

# Including live integration tests against the real API
IGE_USERNAME=... IGE_PASSWORD=... PYTHONPATH=src pytest tests/ -v

The CI workflow runs on Python 3.11, 3.12, and 3.13.

Observability (optional)

The server can emit OpenTelemetry traces — one span per tool call plus child spans for the backend Swissreg/IDP HTTP calls. Tracing is off by default and adds no overhead until enabled.

pip install 'swiss-ip-mcp[otel]'

MCP_OTEL_ENABLED=1 \
  OTEL_EXPORTER_OTLP_ENDPOINT=http://your-collector:4318 \
  MCP_ENV=production \
  swiss-ip-mcp

Tool spans carry only mcp.tool.name and mcp.tool.result.is_error — no query arguments, credentials or response bodies are recorded.

Logging

The server logs structured JSON to stderr (stdout is reserved for the stdio protocol). Every tool call binds a tool name and a correlation_id, so all log lines for one call are correlated. Set the level with LOG_LEVEL (DEBUG / INFO / WARNING / ERROR, default INFO):

{"event": "tool.call.start", "tool": "swiss_ip_search_trademarks", "correlation_id": "da55…", "level": "info", "timestamp": "…Z"}

MCP Protocol Version

This server speaks two protocol eras over the same endpoint. The client's first request on a connection decides which one applies; a later claim from the other era is refused.

Both revisions are pinned in tests/test_protocol_version.py and asserted against the installed SDK, so a Dependabot bump of mcp cannot move either one silently.

On top of that, tests/test_modern_era.py measures both eras: it sends real requests — a 2026-07-28 _meta envelope with the Mcp-Method / Mcp-Protocol-Version routing headers, and a legacy initialize — through the assembled ASGI app and asserts what comes back. Earlier revisions of this section claimed the opposite ("this server builds no ASGI app to send an initialize through"), and that was never true: _build_http_app() builds one, and tests/test_cors.py had been sending requests through it all along. The gate rested on SDK constants for a reason that did not hold.

Note that the SDK's LATEST_PROTOCOL_VERSION is an alias for the modern era, not for the handshake era — pinning against it alone would leave the era that current clients actually negotiate free to drift.

Server identity

Under 2026-07-28 the server identifies itself in every result's _meta (io.modelcontextprotocol/serverInfo, SEP-2575), not once in an initialize response. This server reports its package version and websiteUrl there; it carried the SDK default of an empty version string until that was measured and fixed. icons is deliberately unset — the repo ships no icon asset.

Update policy. When the gate fails, do not edit the constant blindly: read the spec changelog between the two revisions, verify the server still behaves, then move the constant, this section, README.de.md and CHANGELOG.md together.

Data Source

All data is provided by the IGE/IPI Swissreg Datadelivery API. The API is free after signing the usage terms, subject to a monthly data transfer quota. Check your remaining quota at any time using the swiss_ip_get_quota tool.

Provenance: every tool response carries a source block (provider, source URL, license) so downstream consumers retain attribution. The result envelope is { source, total, count, match_type, results, next_page_token }.

Safety & Limits

• Read-only: All tools perform authenticated POST requests to the Swissreg API — no data is written, modified, or deleted on any system.
• No personal data: The API returns public IP register entries (trademark names, patent titles, applicant organisations). No personally identifiable information (PII) is processed or stored by this server beyond what the IGE API returns in its public records.
• Rate limits & quota: The IGE Swissreg API enforces a monthly data transfer quota per account. Use the swiss_ip_get_quota tool to monitor remaining quota. The server enforces a 60s timeout per request. Avoid large page_size values (>20) for exploratory queries.
• Authentication: Credentials (IGE_USERNAME, IGE_PASSWORD) are read from environment variables at runtime and never logged or persisted.
• Terms of service: Data is subject to the IGE Swissreg Datadelivery API terms of use. A signed usage agreement with IGE/IPI is required before API access is granted.
• Address list verified without credentials (2026-08-08). Every address, the Keycloak realm and the client_id this server builds are the ones the source publishes. A null result — and recorded as one, because a null result nobody wrote down is not one on the next pass. Three independent proofs, because one would not have carried:
  • The IDP discriminates: realms/egov with wrong credentials → invalid_grant ("Invalid user credentials"); an invented realm → 404 "Realm does not exist"; an invented client_id → invalid_client. So realm and client exist and only the credentials are missing.
  • The realm declares its own token endpoint under .well-known/openid-configuration — identical to the URL built here.
  • The official API documentation states both addresses verbatim, including the client_id as a "constant string".
• Why the third proof is needed: the Swissreg API itself does not discriminate. A POST without a token returns 403, with an invented token 401 — and a freely invented path under /public/api/ returns exactly the same. A status code proves nothing there. scripts/record_fixtures.py re-measures this on every run and aborts if a control stops discriminating.
• Response payloads are not recorded. They need credentials; PROVENANCE.md lists them as NOT RECORDED with the measured status rather than giving them a date they never had. What stays unproven is the shape of the responses — whether the XML fields are named as the parser reads them.
• No guarantees: This server is a community project, not affiliated with the Swiss Federal Institute of Intellectual Property (IGE/IPI). Availability depends on upstream API uptime.

Related Servers

Contributing

See CONTRIBUTING.md (Deutsch) for how to report bugs and submit changes.

Security

See SECURITY.md for the security posture, hardening summary, and how to report a vulnerability.

License

MIT License — see LICENSE

Author

Hayal Oezkan · github.com/malkreide

Installation

Run via uv's uvx — no clone or manual install needed. Add to your MCP client config (mcpServers for Claude Desktop, Cursor and Windsurf; use a top-level servers key for VS Code in .vscode/mcp.json):

{
  "mcpServers": {
    "swiss-ip-mcp": {
      "command": "uvx",
      "args": [
        "swiss-ip-mcp"
      ],
      "env": {
        "IGE_USERNAME": "<your IGE_USERNAME>",
        "IGE_PASSWORD": "<your IGE_PASSWORD>"
      }
    }
  }
}

Requires credentials: set IGE_USERNAME, IGE_PASSWORD (replace the placeholder values above).