Chuk Mcp Lazarus MCP Server

chuk-mcp-lazarus PyPI v0.14.6

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.

Mechanistic interpretability MCP server wrapping chuk-lazarus

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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
Minimal
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/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 − 2 = 98. 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
−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 64

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

  • ablate_layersno sensitive capability
  • add_experiment_resultno sensitive capability
  • analyze_neuronno sensitive capability
  • attention_headsno sensitive capability
  • attention_patternno sensitive capability
  • attribution_sweepno sensitive capability
  • branch_and_collapseno sensitive capability
  • build_dark_tableno sensitive capability
  • compare_activationsno sensitive capability
  • compare_attentionno sensitive capability
Show 54 more tools ↓
  • compare_generationsno sensitive capability
  • compare_representationsno sensitive capability
  • compare_weightsno sensitive capability
  • component_interventionno sensitive capability
  • computation_mapno sensitive capability
  • compute_steering_vectorno sensitive capability
  • compute_subspaceno sensitive capability
  • create_experimentno sensitive capability
  • decode_residualno sensitive capability
  • direction_anglesno sensitive capability
  • discover_neuronsno sensitive capability
  • embedding_neighborsno sensitive capability
  • evaluate_probeno sensitive capability
  • extract_activationsno sensitive capability
  • extract_directionno sensitive capability
  • feature_dimensionalityno sensitive capability
  • full_causal_traceno sensitive capability
  • generate_textno sensitive capability
  • get_experimentno sensitive capability
  • get_model_infono sensitive capability
  • head_attributionno sensitive capability
  • inject_residualno sensitive capability
  • layer_clusteringno sensitive capability
  • list_dark_tablesno sensitive capability
  • list_experimentsno sensitive capability
  • list_probesno sensitive capability
  • list_steering_vectorsno sensitive capability
  • list_subspacesno sensitive capability
  • load_comparison_modelno sensitive capability
  • load_modelno sensitive capability
  • logit_attributionno sensitive capability
  • logit_lensno sensitive capability
  • neuron_traceno sensitive capability
  • patch_activationsno sensitive capability
  • predict_next_tokenno sensitive capability
  • probe_at_inferenceno sensitive capability
  • residual_atlasno sensitive capability
  • residual_decompositionno sensitive capability
  • residual_mapno sensitive capability
  • residual_matchno sensitive capability
  • residual_trajectoryno sensitive capability
  • scan_probe_across_layersno sensitive capability
  • steer_and_generateno sensitive capability
  • subspace_decompositionno sensitive capability
  • subspace_surgeryno sensitive capability
  • token_spaceno sensitive capability
  • tokenizeno sensitive capability
  • top_neuronsno sensitive capability
  • trace_tokenno sensitive capability
  • track_raceno sensitive capability
  • track_tokenno sensitive capability
  • train_probeno sensitive capability
  • unload_comparison_modelno sensitive capability
  • weight_geometryno 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.14.6 latest A 98/100 0 1.13.0 2026-08-25

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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/chuk-mcp-lazarus/badge.svg)](https://mcptrustchecker.com/registry/chuk-mcp-lazarus)
HTML
<a href="https://mcptrustchecker.com/registry/chuk-mcp-lazarus"><img src="https://mcptrustchecker.com/registry/chuk-mcp-lazarus/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/chuk-mcp-lazarus/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 chuk-mcp-lazarus --online --registry pypi

Use the free API → How scoring works

More in AI & Agents