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.
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:
| Points | Adoption-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.
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
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 capabilityanalyze_market_trendsno sensitive capabilityanalyze_market_trends_toolno sensitive capabilityanalyze_portfolio_impactno sensitive capabilityanalyze_portfolio_impact_toolno sensitive capabilityclear_cache_toolno sensitive capabilitycompare_credit_methodologiesno sensitive capabilitycompare_credit_methodologies_toolno sensitive capabilityget_accountno sensitive capabilityget_all_balancesno sensitive capabilityget_balanceno sensitive capabilityget_bank_paramsno sensitive capabilityget_basketno sensitive capabilityget_basket_balanceno sensitive capabilityget_basket_feeno sensitive capabilityget_cache_stats_toolno sensitive capabilityget_community_poolno sensitive capabilityget_delegation_rewardsno sensitive capabilityget_delegation_total_rewardsno sensitive capabilityget_delegator_validatorsno sensitive capabilityget_delegator_withdraw_addressno sensitive capabilityget_denom_metadatano sensitive capabilityget_denom_ownersno sensitive capabilityget_denoms_metadatano sensitive capabilityget_distribution_paramsno sensitive capabilityget_governance_depositno sensitive capabilityget_governance_paramsno sensitive capabilityget_governance_proposalno sensitive capabilityget_governance_tally_resultno sensitive capabilityget_governance_voteno sensitive capabilityget_sell_orderno sensitive capabilityget_spendable_balancesno sensitive capabilityget_supply_ofno sensitive capabilityget_total_supplyno sensitive capabilityget_validator_commissionno sensitive capabilityget_validator_outstanding_rewardsno sensitive capabilityget_validator_slashesno sensitive capabilityinvalidate_cache_key_toolno sensitive capabilitylist_accountsno sensitive capabilitylist_allowed_denomsno sensitive capabilitylist_basket_balancesno sensitive capabilitylist_basketsno sensitive capabilitylist_classesno sensitive capabilitylist_credit_batchesno sensitive capabilitylist_credit_typesno sensitive capabilitylist_governance_depositsno sensitive capabilitylist_governance_proposalsno sensitive capabilitylist_governance_votesno sensitive capabilitylist_projectsno sensitive capabilitylist_sell_ordersno sensitive capabilitylist_sell_orders_by_batchno sensitive capabilitylist_sell_orders_by_sellerno sensitive capabilityScan 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.0 latest |
A 96/100 | 1 | 1.9.0 | 2026-07-23 |
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.
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
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.