semlayer
PYPI · SEMLAYER
Infers a semantic layer from your data warehouse and serves it to agents over MCP.
Available components
Last scanned (21 hours ago)
Scores higher than 85% of PyPI servers
Category Data and Analytics
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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to semlayer-dev/semlayer). View diagnostics → Pass
- License check failed: the license (FSL-1.1-ALv2) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2886 tokens (~137/item across 21 items; 21 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- Package version: 0.7.0b7 → 0.7.0b8 functional
- 17 Nov 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.7.0b6 → 0.7.0b7 functional
- 16 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 +1
- Malware scan: unverified → pass ▲ security
- Package version: 0.7.0b3 → 0.7.0b6 functional
- Package version: 0.7.0b3 → 0.7.0b5 functional
- 13 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.7.0b2 → 0.7.0b3 functional
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 · Analysed pypi/semlayer@0.7.0b8
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 | semlayer-dev/semlayer |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/semlayer-dev/semlayer/.github/workflows/release.yml@refs/tags/v0.7.0-beta.8 |
| Rekor log index | 3987941308 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f864c5280426c7fe5d2379a52ab0e918386f578dbe9fa540d444e66496bb8128 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
cancel_infer ~23
Stop the inference that is running. Takes effect at the next stage.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_sql ~144
Lint SQL against the semantic layer BEFORE it runs ANYWHERE. Including SQL you intend to execute with a tool that is not semlayer's. Deterministic checks: unknown tables/columns, correlated references, deprecated tables, missing required filters, fan-out aggregates, SCD2 joins without a validity window. These are the mistakes that return a NUMBER rather than an error, so an unchecked statement can be confidently wrong. Fix every error and warning (each finding carries a fix hint), then re-check. Cheap, deterministic, and it never touches the warehouse.
| Name | Type | Req | Description |
|---|---|---|---|
| dialect | string | – | – |
| sql | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
compile_metric ~181
Compile a metric to correct SQL (joins, filters, time bucketing). group_by: comma-separated columns. On refusal the response lists legal alternatives — retry with those or ask the user; do NOT hand-assemble SQL for a refused request. scd: "current" or "asof", required when the join path crosses a history table. These are different questions — a customer's segment now, or their segment when they ordered — so ask the user which they meant rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | string | – | – |
| dialect | string | – | – |
| filter | string | – | – |
| group_by | string | – | – |
| name | string | yes | – |
| scd | string | – | – |
| time_end | string | – | – |
| time_grain | string | – | – |
| time_start | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
context_for_question ~176
START EVERY QUESTION ABOUT THE USER'S DATA HERE. Including when you are not sure a layer is loaded: if none is, this answers with `status` instead of failing, so there is no reason to decide for yourself that there is nothing to query. Deciding that without calling anything is how a user with a 36-table layer loaded was told the server had no data. Returns the part of the layer that bears on this question -- the tables it selected, their columns, keys, required filters and metrics, the routing knowledge for choosing between them -- plus `open_questions`: the claims underneath that nobody has confirmed. Write your SQL from this, `check_sql` it, then `run_sql`. Put the open questions under your answer as assumptions.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
discover_connections ~213
Which warehouses are reachable from this machine, by name. Reads DuckDB files in the working directory, warehouse environment variables, `$SEMLAYER_HOME/.env`, dbt's profiles.yml and Snowflake's connections.toml. Names only: no credential is read, no value that could be one is reported, and no connection is opened. Each entry says whether semlayer can open it (`supported`) and what it would need if not (`note`). requested: the warehouse the user NAMED, in their words, when it is not in the list -- "databricks", "our iceberg tables in s3", "redshift". The answer says whether semlayer opens it after all (Redshift is the postgres connection), and if not, the nearest route and what to tell them. Pass it rather than guessing: a wrong guess here is either a promise we cannot keep or a user sent away who did not need to be.
| Name | Type | Req | Description |
|---|---|---|---|
| requested | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
export_layer ~86
Write a snapshot of the layer in another tool's format. target: `dbt` today. On request only, and lossy -- the result says what the format could not carry. Nothing keeps it in step with the layer afterwards and you must keep answering from the layer, never from the export.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| target | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_domains ~19
List warehouse domains (table groupings) for navigation.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_metrics ~20
List defined metrics (name, measure, aggregation, filter).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_tables ~24
List table summaries, optionally within a domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
infer ~329
Build the semantic layer for a warehouse. Ask the user first. This READS THEIR WAREHOUSE -- metadata and sample values -- under the connection given, and on a real warehouse it takes minutes and uses their own LLM key, which costs them money. Ask before calling it, and say which warehouse you are about to model. connection: a uri from `status.connections`, or one the user gave. Omit it to use the session's. question: what the user actually asked. Keep it here: when the layer is ready, `status` reminds you to answer it, so a run that outlives this turn does not lose the point of itself. scope: schema names, comma-separated, to model only those. The way to make a big warehouse finish quickly. wait_seconds: how long to hold this call open (capped at 60). A DuckDB file finishes inside it and comes back `ready`, so you can answer in the same turn. Anything larger comes back `inferring`. use_llm: false for a statistics-only layer -- no descriptions, no decode validation, no cost, and much faster. While this call is open it streams progress notifications, so a client that renders them shows a bar. Nothing will wake you AFTER it returns. Tell the user that, and call `status` when they next speak.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | – | – |
| question | string | – | – |
| scope | string | – | – |
| use_llm | boolean | – | – |
| wait_seconds | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
load_layer ~89
Load one of the layers `status` listed under `layers`. ref: the `ref` from that list, the connection it is for, or a path to a layer file. Returns the new status. Use it when several layers are on this machine and the user has said which warehouse they mean -- and after it, tell them which one you loaded.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
review_answer ~293
Record a verdict. Takes effect immediately, and says who decided. verdict: `accept`, `reject`, or `set:<value>` -- `review_question` gives the shape `set` takes. decided_by: `agent` if this is YOUR call, `person` if the user said it. Never guess this. You may accept a claim whose accept changes no behaviour; rejecting, setting, and accepting anything that unlocks behaviour are the person's, and you will be told which this is. by: the name to record. For a person, what they told you -- ask once if you do not know, never invent it, and never use your own client's name. For yourself, something recognisable like `claude-code/opus`. exclude: comma-separated object locations the verdict should skip. note: your reasoning, kept on the question whether or not the verdict was recorded. This is how you PROPOSE one you may not decide. If the layer is a set (a hub with members) this is refused and tells the user which terminal command records it, so do not promise them it is kept until you have the result.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | – |
| decided_by | string | yes | – |
| exclude | string | – | – |
| key | string | yes | – |
| note | string | – | – |
| verdict | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
review_decisions ~44
Every verdict in this layer and who stands behind each one. Read `signal`: `agent` means nobody has confirmed it. Say so when an answer rests on one.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
review_question ~29
One question in full: every object it covers, and the evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
review_questions ~103
What is uncertain in this layer, as questions you can answer. Pull this when the user asks what is unreviewed or unreliable. Do NOT walk the user through it after inference: the questions that matter are the ones an answer rested on, and `run_sql` hands you those as `assumptions`. tables: comma-separated, to scope it to what you are looking at.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| tables | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
route_intent ~29
Which tables to use (and avoid) for an analytical intent.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
run_sql ~216
Run ONE read-only SELECT against the session's warehouse. `check_sql` runs first and an error means the SQL is NOT executed -- a query that sums cancelled orders runs perfectly well, so "it ran" was never the standard. Warnings do not block, and come back with the rows because they are about whether the number means what the user thinks. Rows are capped and there is a ten-minute time limit; the cap, the limit and whether rows were truncated are all stated in the result, so you can tell the user what actually applied. Nothing is written, nothing is persisted, and your SQL is never rewritten: a required filter is reported, never silently applied. Refused while an inference is running -- one connection is not shared between the two. Ask again when `status` says `ready`. The result carries `assumptions` -- the unconfirmed claims the answer rests on. Answer the user in words first, then render those under it.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
save_layer ~99
Write the layer into the user's project so their team has it. The cache is per-machine; a file in the repository is what a colleague reads. From then on this session's verdicts land there. Ask where they want it rather than choosing for them. Refused on a set: a hub and its members are several files the user already chose the paths for, and one file cannot hold them.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
semantic_search ~29
Search tables, columns, and metrics by keywords. The starting point.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
status ~104
What this server has, what it can see, and what to do next. Call this first -- and always before telling a user you have no data about their warehouse. It answers with the loaded layer (its size, age, and how many claims nobody has reviewed yet), the warehouse connections visible from this machine, and a `next` field saying what to do -- including when there is no layer at all, which is the state a fresh install is in.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
table_detail ~31
Full detail for one table: columns, keys, relationships, REQUIRED FILTERS.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the semlayer MCP server?
semlayer runs locally as a PyPI package, launched with uvx --with 'semlayer[warehouses]' semlayer mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
pypi · semlayer
claude mcp add dev-semlayer-mcp -- uvx --with 'semlayer[warehouses]' semlayer mcp
What is the semlayer MCP server?
semlayer is an MCP server listed in the public MCP registry as dev.semlayer/mcp. Infers a semantic layer from your data warehouse and serves it to agents over MCP. This page covers its PyPI package (semlayer).
Is the semlayer MCP server safe to use?
semlayer scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 semlayer MCP server expose?
semlayer exposes 21 tools: status, discover_connections, load_layer, infer, cancel_infer, and 16 more. Their descriptions and schemas cost roughly 2,281 tokens of context every time the server is loaded.
Is the semlayer MCP server still maintained?
semlayer 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 licence is the semlayer MCP server under?
semlayer declares the FSL-1.1-ALv2 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the semlayer MCP server?
VerifyMCP ran 16 checks on semlayer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.