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.

io.github.malkreide/lindas-mcp

PYPI · LINDAS-MCP

MCP server for LINDAS — the Swiss administration's linked-data SPARQL knowledge graph (cube.link)

Available components

0 this week 92 Trust /100

Last scanned (1 day ago)

Scores higher than 95% of PyPI servers

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to malkreide/lindas-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 45 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1225 tokens (~175/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.1 → 0.3.0 functional
  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 0
    • Stability: pass → 0.97 functional
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → pass ▲ functional
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 4 Nov 2026 · Analysed pypi/lindas-mcp@0.3.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo malkreide/lindas-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/malkreide/lindas-mcp/.github/workflows/publish.yml@refs/tags/v0.3.0
Rekor log index 2892642245
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:719264487607448b6fb0eef663352c7349b134de84acc135181c47d6b08f5e78

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 32 packages
Packages resolved 32
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~980 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
api_status ~49

Check whether the LINDAS SPARQL endpoint is reachable. Returns an evaluable status even on failure, so an agent can tell "no data matched" apart from "the endpoint is down".

Input schema present but exposes no named parameters.

NameTypeReqDescription
cube_count–––
endpointstringyes–
last_successful_call–––
notestringyes–
provenancestring––
reachablebooleanyes–
retrieved_atstringyes–
sourcestring––

No examples provided.

get_cube_structure ~213

Read a cube's dimensions and measures — what the cube contains. Tells you which dimensions you can filter on (`KeyDimension`), which values are measured (`MeasureDimension`), and which dimensions carry code lists. It also returns the licence, which is frequently a Fedlex URI you can resolve with fedlex-mcp. Call this to understand a cube before reading it, and to write a `run_sparql` query against it. It is NOT a prerequisite for readable data: `query_cube_observations` fetches the structure itself and resolves labels on its own. Note that this result reports only *whether* a dimension has a code list (`has_codelist`), not the list's entries — so calling it first does not help you decode raw codes either. Args: cube_uri: A cube URI from `search_cubes`. language: Language for dimension names and description.

NameTypeReqDescription
cube_uristringyes–
languagestring––
NameTypeReqDescription
creator_name–––
cube_uristringyes–
description–––
dimensionsarrayyes–
licence––Often a Fedlex URI — joins to fedlex-mcp.
name–––
provenancestring––
retrieved_atstringyes–
sourcestring––
status–––
version–––

No examples provided.

list_publishers ~43

List the federal bodies that publish cubes, with cube counts. Returns creator URIs you can pass to `search_cubes` to restrict a search to one authority.

Input schema present but exposes no named parameters.

NameTypeReqDescription
provenancestring––
publishersarrayyes–
retrieved_atstringyes–
returnedintegeryes–
sourcestring––

No examples provided.

query_cube_observations ~198

Read the actual data points of a cube, with codes resolved to labels. This is phase 2. Values are returned keyed by human-readable dimension names, and coded dimension values (e.g. region "1805") are replaced by their labels (e.g. "Alpennordhang") unless you turn that off. For large cubes this reads only the first `limit` observations. LINDAS has no cheap way to filter observations server-side by arbitrary dimension value, so heavy analytical slicing belongs in `run_sparql`. Args: cube_uri: A cube URI from `search_cubes`. language: Language for labels. limit: Maximum observations to return (1-500). resolve_labels: Replace coded values with human labels.

NameTypeReqDescription
cube_uristringyes–
languagestring––
limitinteger––
resolve_labelsboolean––
NameTypeReqDescription
cube_name–––
cube_uristringyes–
labels_resolvedbooleanyes–
licence–––
observationsarrayyes–
provenancestring––
retrieved_atstringyes–
returnedintegeryes–
sourcestring––

No examples provided.

resolve_municipality ~134

Resolve a Swiss municipality to its LINDAS URI and BFS number. The BFS commune number is the join key across the whole portfolio: the same number identifies the municipality in swiss-statistics-mcp, zurich-opendata-mcp and any cube that references a place. In LINDAS the URI is literally ld.admin.ch/municipality/<BFS>. Args: name_or_bfs: A municipality name ("Zürich") or a BFS number ("261"). language: Language for the name.

NameTypeReqDescription
languagestring––
name_or_bfsstringyes–
NameTypeReqDescription
match_typestring–'none' when the name/BFS number resolved to nothing.
municipalitiesarrayyes–
provenancestring––
querystringyes–
retrieved_atstringyes–
returnedintegeryes–
sourcestring––
suggestion––Actionable next step when match_type is 'none'.

No examples provided.

run_sparql ~159

Run a raw SPARQL SELECT query. Advanced escape hatch — use sparingly. Prefer the structured tools. This exists for analytical queries the guarded tools cannot express (cross-cube joins, aggregations, custom filters). Guardrails, learned from probing: LINDAS times out on unanchored scans, so always anchor on a known class such as `?x a <https://cube.link/Cube>`. A bare `SELECT * WHERE { ?s ?p ?o }` will time out. This tool caps the result at 500 rows and the runtime at 30 seconds. Args: query: A complete SPARQL SELECT query, including its own PREFIX lines.

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
notestringyes–
provenancestring––
retrieved_atstringyes–
row_countintegeryes–
rowsarrayyes–
sourcestring––

No examples provided.

search_cubes ~184

Find statistical data cubes in LINDAS by topic. The entry point. Returns cube URIs you then pass to `get_cube_structure`. By default only the newest published version of each cube is returned; set `latest_only=False` to see every version. Args: query: Topic term, e.g. "Wald", "Abfluss", "Energie". Matched against cube names and descriptions in the chosen language. language: Language for names and descriptions. creator_uri: Restrict to one publishing body (from `list_publishers`). limit: Maximum cubes to return (1-100). latest_only: Collapse versions to the newest per cube.

NameTypeReqDescription
creator_uri–––
languagestring––
latest_onlyboolean––
limitinteger––
querystringyes–
NameTypeReqDescription
cubesarrayyes–
languagestringyes–
latest_onlybooleanyes–
match_typestring–'none' when nothing matched — distinguishes a real miss from an error.
provenancestring––
query–yes–
retrieved_atstringyes–
returnedintegeryes–
sourcestring––
suggestion––Actionable next step when match_type is 'none' (e.g. which tool to try).

No examples provided.

Install

How do I install the io.github.malkreide/lindas-mcp server?

io.github.malkreide/lindas-mcp runs locally as a PyPI package, launched with uvx lindas-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · lindas-mcp

# add to Claude Code
claude mcp add malkreide-lindas-mcp -- uvx lindas-mcp
Common questions

What is the io.github.malkreide/lindas-mcp server?

io.github.malkreide/lindas-mcp is listed in the public MCP registry as io.github.malkreide/lindas-mcp. MCP server for LINDAS, the Swiss administration's linked-data SPARQL knowledge graph (cube.link). This page covers its PyPI package (lindas-mcp).

Is the io.github.malkreide/lindas-mcp server safe to use?

io.github.malkreide/lindas-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 io.github.malkreide/lindas-mcp server expose?

io.github.malkreide/lindas-mcp exposes 7 tools: search_cubes, get_cube_structure, query_cube_observations, list_publishers, resolve_municipality, and 2 more. Their descriptions and schemas cost roughly 980 tokens of context every time the server is loaded.

Is the io.github.malkreide/lindas-mcp server still maintained?

io.github.malkreide/lindas-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.malkreide/lindas-mcp server under?

io.github.malkreide/lindas-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.