Euclid-MCP
PYPI · EUCLID-MCP · SCANNED SEP 21
Deterministic logical reasoning engine — facts in Euclid IR, solutions with proof trees
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 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 native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 651 tokens (~81/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 (63% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "unregister_kb" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 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 Euclid-MCP server?
Euclid-MCP runs locally as a PyPI package, launched with uvx euclid-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 · euclid-mcp
claude mcp add meob-euclid-mcp -- uvx euclid-mcp
{
"mcpServers": {
"meob-euclid-mcp": {
"command": "uvx",
"args": [
"euclid-mcp"
]
}
}
} {
"servers": {
"meob-euclid-mcp": {
"command": "uvx",
"args": [
"euclid-mcp"
]
}
}
} codex mcp add meob-euclid-mcp -- uvx euclid-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"meob-euclid-mcp": {
"type": "local",
"command": [
"uvx",
"euclid-mcp"
],
"enabled": true
}
}
} openclaw mcp add meob-euclid-mcp --command uvx --arg euclid-mcp
mcp_servers:
meob-euclid-mcp:
command: "uvx"
args: ["euclid-mcp"] {
"McpServers": {
"meob-euclid-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"euclid-mcp"
]
}
}
} assistant mcp add meob-euclid-mcp -t stdio -c uvx -a euclid-mcp
{
"mcpServers": {
"meob-euclid-mcp": {
"command": "uvx",
"args": [
"euclid-mcp"
]
}
}
} 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 Sept 26 −3
- Stability: pass → 0.80 functional
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 19 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Sept 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.93 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- Package version: 0.1.2 → 0.4.5 functional
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 2026 · Analysed pypi/euclid-mcp@0.4.5
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 | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| 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 →
check_kb ~45
Check a knowledge base for consistency: syntax errors, undefined predicates, circular rules, duplicates.
| Name | Type | Req | Description |
|---|---|---|---|
| delta_knowledge | – | – | – |
| kb_id | – | – | – |
| knowledge | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content_hash | – | – | – |
| elapsed_ms | number | – | – |
| error | – | – | – |
| errors | array | – | – |
| facts_count | integer | – | – |
| predicates | array | – | – |
| predicates_count | integer | – | – |
| rules_count | integer | – | – |
| valid | boolean | – | – |
| version | – | – | – |
| warnings | array | – | – |
No examples provided.
diagnose ~95
Diagnose why a query succeeds or fails. Modes: 'why' (explain success), 'why_not' (explain failure), 'what_needs' (what would make it succeed)
| Name | Type | Req | Description |
|---|---|---|---|
| delta_knowledge | – | – | – |
| kb_id | – | – | – |
| knowledge | – | – | – |
| max_depth | integer | – | – |
| max_solutions | integer | – | – |
| mode | string | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| conclusion | string | – | – |
| content_hash | – | – | – |
| elapsed_ms | number | – | – |
| error | – | – | – |
| findings | array | – | – |
| holds | boolean | – | – |
| mode | string | – | – |
| proof | – | – | – |
| query | string | – | – |
| solutions | array | – | – |
| version | – | – | – |
No examples provided.
explain ~79
Explain, in natural language, how a query is proven: walk the proof tree of each solution and return readable reasoning steps. Rule IDs are cited when present.
| Name | Type | Req | Description |
|---|---|---|---|
| delta_knowledge | – | – | – |
| kb_id | – | – | – |
| knowledge | – | – | – |
| max_depth | integer | – | – |
| max_solutions | integer | – | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content_hash | – | – | – |
| elapsed_ms | number | – | – |
| error | – | – | – |
| explanations | array | – | – |
| query | string | – | – |
| version | – | – | – |
No examples provided.
list_kbs ~29
List the registered named knowledge bases (metadata only: kb_id, content_hash, version, counts).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reason ~64
Perform logical deduction on a knowledge base and return solutions with proof trees for each result
| Name | Type | Req | Description |
|---|---|---|---|
| delta_knowledge | – | – | – |
| kb_id | – | – | – |
| knowledge | – | – | – |
| max_depth | integer | – | – |
| max_solutions | integer | – | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| content_hash | – | – | – |
| elapsed_ms | number | – | – |
| error | – | – | – |
| query | string | – | – |
| solutions | array | – | – |
| version | – | – | – |
No examples provided.
register_kb ~64
Register a named knowledge base under a kb_id so later calls can reference it instead of resending the KB text. Overwrites an existing kb_id. The KB is validated with check_kb first.
| Name | Type | Req | Description |
|---|---|---|---|
| kb_id | string | yes | – |
| knowledge | string | yes | – |
No output schema declared.
No examples provided.
unregister_kb ~39
Remove a named knowledge base from the registry. Returns 'removed': false when the kb_id is not registered.
| Name | Type | Req | Description |
|---|---|---|---|
| kb_id | string | yes | – |
No output schema declared.
No examples provided.
what_if ~90
What-if analysis: apply modifications to a knowledge base and see how they affect query results. Use + prefix to add facts, - prefix to remove facts.
| Name | Type | Req | Description |
|---|---|---|---|
| base_knowledge | – | – | – |
| delta_knowledge | – | – | – |
| kb_id | – | – | – |
| max_depth | integer | – | – |
| max_solutions | integer | – | – |
| modifications | string | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| after_count | integer | – | – |
| before_count | integer | – | – |
| conclusion | string | – | – |
| content_hash | – | – | – |
| delta | string | – | – |
| elapsed_ms | number | – | – |
| error | – | – | – |
| modifications | string | – | – |
| query | string | – | – |
| solutions_after | array | – | – |
| solutions_before | array | – | – |
| version | – | – | – |
No examples provided.
What is the Euclid-MCP server?
Euclid-MCP is listed in the public MCP registry as io.github.meob/euclid-mcp. Deterministic logical reasoning engine, facts in Euclid IR, solutions with proof trees. This page covers its PyPI package (euclid-mcp).
Is the Euclid-MCP server safe to use?
Euclid-MCP scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 Euclid-MCP server expose?
Euclid-MCP exposes 8 tools: reason, explain, diagnose, what_if, check_kb, and 3 more. Their descriptions and schemas cost roughly 505 tokens of context every time the server is loaded.
Is the Euclid-MCP server still maintained?
Euclid-MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.