// MCP SERVER RECORD

Pybme

Unverified
REPOwiesnerfriedman/pybme-mcp
DRisk gradehigh blast radius
Catalogue entry updated 6 days ago
Auth postureNot probedno remote endpoint probed yet
Tools72 Execute · 1 Write · 4 Read
Worst categoryExecutegrade tracks the peak, not the average
Capability mix
Execute 2Write 1Read 4
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 7
fit_uncertainty_modelExecuteMediumrun_uncertainty_updateExecuteMediumingest_external_scenario_evidenceWriteMediumcompare_operator_approachesReadLowdesign_next_observation_or_scenarioReadLow
View all 7 tools
explain_uncertainty_driversReadLowinspect_modeling_contextReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
fit_uncertainty_modelrequire approval
ingest_external_scenario_evidencerate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.