React Devtools Bridge MCP Server

react-devtools-bridge npm v0.1.0

Published by skylarbarrera — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server exposing React DevTools functionality to AI agents

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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 = 99/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 − 1 = 99. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 47

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

  • capture_screenshotno sensitive capability
  • clear_errors_and_warningsno sensitive capability
  • clear_highlightno sensitive capability
  • Component Treeno sensitive capability
  • connectno sensitive capability
  • Current Selectionno sensitive capability
  • delete_pathno sensitive capability
  • disconnectno sensitive capability
  • get_capabilitiesno sensitive capability
  • get_component_filtersno sensitive capability
Show 37 more tools ↓
  • get_component_treeno sensitive capability
  • get_connection_statusno sensitive capability
  • get_element_by_idno sensitive capability
  • get_element_sourceno sensitive capability
  • get_elements_by_rendererno sensitive capability
  • get_errors_and_warningsno sensitive capability
  • get_inspecting_native_statusno sensitive capability
  • get_native_styleno sensitive capability
  • get_owners_listno sensitive capability
  • get_profiling_datano sensitive capability
  • get_profiling_statusno sensitive capability
  • get_rendererno sensitive capability
  • get_renderersno sensitive capability
  • health_checkno sensitive capability
  • highlight_elementno sensitive capability
  • inspect_elementno sensitive capability
  • log_to_consoleno sensitive capability
  • override_contextno sensitive capability
  • override_hooksno sensitive capability
  • override_propsno sensitive capability
  • override_stateno sensitive capability
  • rename_pathno sensitive capability
  • save_to_clipboardno sensitive capability
  • scroll_to_elementno sensitive capability
  • search_componentsno sensitive capability
  • set_component_filtersno sensitive capability
  • set_native_styleno sensitive capability
  • set_trace_updates_enabledno sensitive capability
  • start_inspecting_nativeno sensitive capability
  • start_profilingno sensitive capability
  • stop_inspecting_nativeno sensitive capability
  • stop_profilingno sensitive capability
  • store_as_globalno sensitive capability
  • toggle_errorno sensitive capability
  • toggle_suspenseno sensitive capability
  • view_attribute_sourceno sensitive capability
  • view_sourceno 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.1.0 latest A 99/100 0 1.13.0 2026-09-08

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

Use the free API → How scoring works

More in Developer Tools