Dke Forge MCP Server

dke-forge PyPI v0.25.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 63

Each tool and what it can reach — statically extracted from the published source.

  • forge_get_graphingests untrusted input
  • forge_abstractionsno sensitive capability
  • forge_amend_ruleno sensitive capability
  • forge_api_surfaceno sensitive capability
  • forge_architecture_mapno sensitive capability
  • forge_audit_changesno sensitive capability
  • forge_auth_verifyno sensitive capability
  • forge_breaking_changeno sensitive capability
  • forge_callees_ofno sensitive capability
  • forge_callers_ofno sensitive capability
Show 53 more tools ↓
  • forge_callgraph_reachableno sensitive capability
  • forge_check_rulesno sensitive capability
  • forge_circular_depsno sensitive capability
  • forge_classify_effectsno sensitive capability
  • forge_commit_impactno sensitive capability
  • forge_contract_checkno sensitive capability
  • forge_contradictionsno sensitive capability
  • forge_contradictions_hypotheticalno sensitive capability
  • forge_create_graphno sensitive capability
  • forge_dead_codeno sensitive capability
  • forge_declareno sensitive capability
  • forge_declare_ruleno sensitive capability
  • forge_delete_graphno sensitive capability
  • forge_depends_onno sensitive capability
  • forge_deprecation_pathno sensitive capability
  • forge_effect_behavioralno sensitive capability
  • forge_effectsno sensitive capability
  • forge_effects_classificationno sensitive capability
  • forge_envelopeno sensitive capability
  • forge_find_implementersno sensitive capability
  • forge_god_classesno sensitive capability
  • forge_graph_statsno sensitive capability
  • forge_healthno sensitive capability
  • forge_impact_analysisno sensitive capability
  • forge_invitation_previewno sensitive capability
  • forge_invitation_resendno sensitive capability
  • forge_last_modifiedno sensitive capability
  • forge_learn_patternsno sensitive capability
  • forge_list_graphsno sensitive capability
  • forge_live_varsno sensitive capability
  • forge_module_topologyno sensitive capability
  • forge_pattern_catalogno sensitive capability
  • forge_pattern_detailno sensitive capability
  • forge_patternsno sensitive capability
  • forge_promote_default_graphno sensitive capability
  • forge_provenanceno sensitive capability
  • forge_query_functionno sensitive capability
  • forge_reach_coneno sensitive capability
  • forge_reach_fromno sensitive capability
  • forge_reaching_defsno sensitive capability
  • forge_reason_chainno sensitive capability
  • forge_reasoning_traceno sensitive capability
  • forge_refactor_previewno sensitive capability
  • forge_refineno sensitive capability
  • forge_rename_graphno sensitive capability
  • forge_retire_ruleno sensitive capability
  • forge_reviewno sensitive capability
  • forge_risky_changeno sensitive capability
  • forge_rulesno sensitive capability
  • forge_subgraphno sensitive capability
  • forge_taintno sensitive capability
  • forge_type_flowno sensitive capability
  • forge_use_defno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.25.0 latest A 95/100 0 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/dke-forge/badge.svg)](https://mcptrustchecker.com/registry/dke-forge)
HTML
<a href="https://mcptrustchecker.com/registry/dke-forge"><img src="https://mcptrustchecker.com/registry/dke-forge/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/dke-forge/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan dke-forge --online --registry pypi

Use the free API → How scoring works

More in Developer Tools