Regen Python MCP Server

regen-python-mcp PyPI v0.1.0

Published by regen-network — 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.

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

medium Hardcoded egress to an external endpoint (src/mcp_server/prompts/chain_config_setup_prompt.py)MTC-SRC-003

In the server's implementation (`src/mcp_server/prompts/chain_config_setup_prompt.py:421`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try: response = requests.get("https://rest.cosmos.directory/regen", timeout=5) print(f"REST API: ✅ Conne

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/mcp_server/prompts/chain_config_setup_prompt.py

Tools 56

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

  • _get_basketno sensitive capability
  • _get_basket_balanceno sensitive capability
  • _get_basket_feeno sensitive capability
  • _list_basket_balancesno sensitive capability
  • _list_basketsno sensitive capability
  • analyze_market_trendsno sensitive capability
  • analyze_market_trends_toolno sensitive capability
  • analyze_portfolio_impactno sensitive capability
  • analyze_portfolio_impact_toolno sensitive capability
  • clear_cache_toolno sensitive capability
Show 46 more tools ↓
  • compare_credit_methodologiesno sensitive capability
  • compare_credit_methodologies_toolno sensitive capability
  • get_accountno sensitive capability
  • get_all_balancesno sensitive capability
  • get_balanceno sensitive capability
  • get_bank_paramsno sensitive capability
  • get_basketno sensitive capability
  • get_basket_balanceno sensitive capability
  • get_basket_feeno sensitive capability
  • get_cache_stats_toolno sensitive capability
  • get_community_poolno sensitive capability
  • get_delegation_rewardsno sensitive capability
  • get_delegation_total_rewardsno sensitive capability
  • get_delegator_validatorsno sensitive capability
  • get_delegator_withdraw_addressno sensitive capability
  • get_denom_metadatano sensitive capability
  • get_denom_ownersno sensitive capability
  • get_denoms_metadatano sensitive capability
  • get_distribution_paramsno sensitive capability
  • get_governance_depositno sensitive capability
  • get_governance_paramsno sensitive capability
  • get_governance_proposalno sensitive capability
  • get_governance_tally_resultno sensitive capability
  • get_governance_voteno sensitive capability
  • get_sell_orderno sensitive capability
  • get_spendable_balancesno sensitive capability
  • get_supply_ofno sensitive capability
  • get_total_supplyno sensitive capability
  • get_validator_commissionno sensitive capability
  • get_validator_outstanding_rewardsno sensitive capability
  • get_validator_slashesno sensitive capability
  • invalidate_cache_key_toolno sensitive capability
  • list_accountsno sensitive capability
  • list_allowed_denomsno sensitive capability
  • list_basket_balancesno sensitive capability
  • list_basketsno sensitive capability
  • list_classesno sensitive capability
  • list_credit_batchesno sensitive capability
  • list_credit_typesno sensitive capability
  • list_governance_depositsno sensitive capability
  • list_governance_proposalsno sensitive capability
  • list_governance_votesno sensitive capability
  • list_projectsno sensitive capability
  • list_sell_ordersno sensitive capability
  • list_sell_orders_by_batchno sensitive capability
  • list_sell_orders_by_sellerno 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 96/100 1 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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/regen-python-mcp/badge.svg)](https://mcptrustchecker.com/registry/regen-python-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/regen-python-mcp"><img src="https://mcptrustchecker.com/registry/regen-python-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/regen-python-mcp/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 regen-python-mcp --online --registry pypi

Use the free API → How scoring works

More in Developer Tools