io.github.CodeLogicIncEngineering/codelogic-mcp-server
PYPI · CODELOGIC-MCP-SERVER
An MCP Server to utilize Codelogic's rich software dependency data in your AI programming assistant.
Available components
Last scanned (2 months ago)
Scores higher than 0% of PyPI servers
Category Code Search and Documentation
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency3
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: the registry has no such package, so there's no artefact to verify. See how to fix → View diagnostics → Fail
- License check failed: the registry has no such package, so no license can be read. See how to fix → Fail
- Maintenance check failed: the registry has no such package, so there's no release history to read. See how to fix → Fail
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1057 tokens (~132/item across 8 items; 8 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
Tool Safety–
Not scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 14 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 −12
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Aug 26 0
- Known CVEs: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- The code this package runs automatically changed: its declared build backend security
- Dependency health: 0.97 → unverified ▼ functional
- 8 Aug 26 0
- Security disclosure: fail → pass ▲ functional
- 7 Aug 26 +26
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 42 functional
- First check of Schema quality: fail functional
- First check of Schema quality: good 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 14 Aug 2026 · Analysed pypi/codelogic-mcp-server@1.3.0
Provenance Package not found
The registry answered that no such package exists, so no provenance could be looked up.
| Result | Package not found |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
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 →
codelogic-database-impact ~157
Analyze impacts between code and database entities. Uses CODELOGIC_WORKSPACE_NAME environment variable to determine the target workspace. Recommended workflow: 1. Use this tool before implementing code or database changes 2. Search for the relevant database entity 3. Review the impact analysis to understand which code depends on this database object and vice versa Particularly crucial when AI-suggested modifications are being considered or when modifying SQL code.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | string | yes | Type of database entity to search for (column, table, or view) |
| name | string | yes | Name of the database entity to search for |
| table_or_view | string | – | Name of the table or view containing the column (required for columns only) |
No output schema declared.
No examples provided.
codelogic-graph-capabilities ~85
Fetch graph API capabilities/manifest from the CodeLogic server (GET). Returns label and relationship metadata when the graph tier is deployed; otherwise explains missing routes. Uses CODELOGIC_WORKSPACE_NAME for MV id unless `materialized_view_id` is set.
| Name | Type | Req | Description |
|---|---|---|---|
| materialized_view_id | string | – | Optional materialized view id; default from workspace name |
No output schema declared.
No examples provided.
codelogic-graph-impact ~100
Bounded graph impact from seed node ids (curated HTTP API). Optional `direction` (upstream|downstream|both), `depth`, `scan_space`, `materialized_view_id`.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| direction | string | – | – |
| materialized_view_id | string | – | – |
| scan_space | string | – | – |
| seed_node_ids | array | yes | Graph node ids to expand from |
No output schema declared.
No examples provided.
codelogic-graph-owners ~74
Look up owners/reviewers for a graph node (curated HTTP API). Provide `node_id` or `identity_prefix`.
| Name | Type | Req | Description |
|---|---|---|---|
| identity_prefix | string | – | – |
| materialized_view_id | string | – | – |
| node_id | string | – | – |
| scan_space | string | – | – |
No output schema declared.
No examples provided.
codelogic-graph-path-explain ~98
Explain bounded paths between two graph nodes (curated HTTP API). Requires `from_node_id`, `to_node_id`; optional `max_depth`, `scan_space`, `materialized_view_id`.
| Name | Type | Req | Description |
|---|---|---|---|
| from_node_id | string | yes | – |
| materialized_view_id | string | – | – |
| max_depth | integer | – | – |
| scan_space | string | – | – |
| to_node_id | string | yes | – |
No output schema declared.
No examples provided.
codelogic-graph-search ~155
Search the CodeLogic knowledge graph (curated HTTP API). Provide `query` or `identity_prefix`; optional `scan_space`, `materialized_view_id`, `limit`. Requires server route POST .../ai-retrieval/graph/search.
| Name | Type | Req | Description |
|---|---|---|---|
| identity_prefix | string | – | Prefix of stable graph identity |
| limit | integer | – | Suggested max hits (server may cap) |
| materialized_view_id | string | – | Override MV id; default from workspace name |
| prefer_latest_scan | boolean | – | – |
| q | string | – | Alias for query |
| query | string | – | Symbol or text query (alias: q) |
| scan_space | string | – | Optional scan-space / branch filter |
No output schema declared.
No examples provided.
codelogic-graph-validate-change-scope ~71
Validate whether a proposed change scope is safe given seed graph nodes (curated HTTP API).
| Name | Type | Req | Description |
|---|---|---|---|
| materialized_view_id | string | – | – |
| proposed_change_summary | string | yes | – |
| scan_space | string | – | – |
| seed_node_ids | array | yes | – |
No output schema declared.
No examples provided.
codelogic-method-impact ~122
Analyze impacts of modifying a specific method within a given class or type. Uses CODELOGIC_WORKSPACE_NAME environment variable to determine the target workspace. Recommended workflow: 1. Use this tool before implementing code changes 2. Run the tool against methods or functions that are being modified 3. Carefully review the impact analysis results to understand potential downstream effects Particularly crucial when AI-suggested modifications are being considered.
| Name | Type | Req | Description |
|---|---|---|---|
| class | string | yes | Name of the class containing the method |
| method | string | yes | Name of the method being analyzed |
No output schema declared.
No examples provided.
How do I install the io.github.CodeLogicIncEngineering/codelogic-mcp-server server?
io.github.CodeLogicIncEngineering/codelogic-mcp-server runs locally as a PyPI package, launched with uvx codelogic-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · codelogic-mcp-server
claude mcp add codelogicincengineering-codelogic-mcp-server -- uvx codelogic-mcp-server
What is the io.github.CodeLogicIncEngineering/codelogic-mcp-server server?
io.github.CodeLogicIncEngineering/codelogic-mcp-server is listed in the public MCP registry as io.github.CodeLogicIncEngineering/codelogic-mcp-server. An MCP Server to utilize Codelogic's rich software dependency data in your AI programming assistant. This page covers its PyPI package (codelogic-mcp-server).
Is the io.github.CodeLogicIncEngineering/codelogic-mcp-server server safe to use?
io.github.CodeLogicIncEngineering/codelogic-mcp-server scores 0 out of 100 on VerifyMCP. 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.CodeLogicIncEngineering/codelogic-mcp-server server expose?
io.github.CodeLogicIncEngineering/codelogic-mcp-server exposes 8 tools: codelogic-method-impact, codelogic-database-impact, codelogic-graph-capabilities, codelogic-graph-search, codelogic-graph-impact, and 3 more. Their descriptions and schemas cost roughly 862 tokens of context every time the server is loaded.
Is the io.github.CodeLogicIncEngineering/codelogic-mcp-server server still maintained?
io.github.CodeLogicIncEngineering/codelogic-mcp-server has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 7 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.