io.github.daedalus/mcp-z3-prover
PYPI · MCP-Z3-PROVER · SCANNED SEP 20
MCP server exposing Z3 solver API
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 175 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 275 tokens (~25/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
How do I install the io.github.daedalus/mcp-z3-prover server?
io.github.daedalus/mcp-z3-prover runs locally as a PyPI package, launched with uvx mcp-z3-prover. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-z3-prover
claude mcp add daedalus-mcp-z3-prover -- uvx mcp-z3-prover
{
"mcpServers": {
"daedalus-mcp-z3-prover": {
"command": "uvx",
"args": [
"mcp-z3-prover"
]
}
}
} {
"servers": {
"daedalus-mcp-z3-prover": {
"command": "uvx",
"args": [
"mcp-z3-prover"
]
}
}
} codex mcp add daedalus-mcp-z3-prover -- uvx mcp-z3-prover
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"daedalus-mcp-z3-prover": {
"type": "local",
"command": [
"uvx",
"mcp-z3-prover"
],
"enabled": true
}
}
} openclaw mcp add daedalus-mcp-z3-prover --command uvx --arg mcp-z3-prover
mcp_servers:
daedalus-mcp-z3-prover:
command: "uvx"
args: ["mcp-z3-prover"] {
"McpServers": {
"daedalus-mcp-z3-prover": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-z3-prover"
]
}
}
} assistant mcp add daedalus-mcp-z3-prover -t stdio -c uvx -a mcp-z3-prover
{
"mcpServers": {
"daedalus-mcp-z3-prover": {
"command": "uvx",
"args": [
"mcp-z3-prover"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 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 20 Sept 2026 · Analysed pypi/mcp-z3-prover@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 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 →
add_constraint Add Constraint ~41
Add a constraint to the solver. Use variable references like 'bool:x', 'int:y', 'real:z' in expressions.
| Name | Type | Req | Description |
|---|---|---|---|
| constraint | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_bool_var Create Bool Var ~25
Create a Boolean variable with the given name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_int_constant Create Int Constant ~25
Create an integer constant with the given value.
| Name | Type | Req | Description |
|---|---|---|---|
| value | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_int_var Create Int Var ~25
Create an Integer variable with the given name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_real_constant Create Real Constant ~25
Create a real constant with the given value.
| Name | Type | Req | Description |
|---|---|---|---|
| value | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_real_var Create Real Var ~25
Create a Real variable with the given name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_model_value Get Model Value ~28
Get the value of a variable from the model after solving.
| Name | Type | Req | Description |
|---|---|---|---|
| variable | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_variables List Variables ~13
List all created variables.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
optimize Optimize ~30
Solve with optimization objective (maximize or minimize).
| Name | Type | Req | Description |
|---|---|---|---|
| maximize | boolean | – | – |
| objective | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
reset_solver Reset Solver ~22
Reset the solver state (clear all variables, constraints, and model).
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
solve Solve ~16
Solve the current problem and return the result.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.daedalus/mcp-z3-prover server?
io.github.daedalus/mcp-z3-prover is listed in the public MCP registry as io.github.daedalus/mcp-z3-prover. MCP server exposing Z3 solver API. This page covers its PyPI package (mcp-z3-prover).
Is the io.github.daedalus/mcp-z3-prover server safe to use?
io.github.daedalus/mcp-z3-prover scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.daedalus/mcp-z3-prover server expose?
io.github.daedalus/mcp-z3-prover exposes 11 tools: create_bool_var, create_int_var, create_real_var, create_int_constant, create_real_constant, and 6 more. Their descriptions and schemas cost roughly 275 tokens of context every time the server is loaded.
Is the io.github.daedalus/mcp-z3-prover server still maintained?
io.github.daedalus/mcp-z3-prover is still listed as active in the MCP registry. We last reached this channel on 20 September 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.daedalus/mcp-z3-prover server under?
io.github.daedalus/mcp-z3-prover declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.