Devrev Python Sdk MCP Server

devrev-python-sdk PyPI v3.2.0

Published by mgmonteleone — 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

low Dynamic module load from a non-literal in packaging/dev tooling (tests/integration/utils/data_manager.py)MTC-SRC-005

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/integration/utils/data_manager.py:176`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: delete( __import__( "devrev.models.articles", fromlist=["ArticlesDeleteRequest"]

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 tests/integration/utils/data_manager.py

Tools 98

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

  • devrev_webhooks_deletenetwork egress
  • devrev_webhooks_getnetwork egress
  • devrev_accounts_createno sensitive capability
  • devrev_accounts_deleteno sensitive capability
  • devrev_accounts_getno sensitive capability
  • devrev_accounts_listno sensitive capability
  • devrev_accounts_mergeno sensitive capability
  • devrev_accounts_updateno sensitive capability
  • devrev_articles_countno sensitive capability
  • devrev_articles_createno sensitive capability
Show 88 more tools ↓
  • devrev_articles_deleteno sensitive capability
  • devrev_articles_getno sensitive capability
  • devrev_articles_listno sensitive capability
  • devrev_articles_updateno sensitive capability
  • devrev_conversations_createno sensitive capability
  • devrev_conversations_deleteno sensitive capability
  • devrev_conversations_exportno sensitive capability
  • devrev_conversations_getno sensitive capability
  • devrev_conversations_listno sensitive capability
  • devrev_conversations_list_modified_sinceno sensitive capability
  • devrev_conversations_updateno sensitive capability
  • devrev_dev_users_getno sensitive capability
  • devrev_dev_users_listno sensitive capability
  • devrev_engagements_countno sensitive capability
  • devrev_engagements_createno sensitive capability
  • devrev_engagements_deleteno sensitive capability
  • devrev_engagements_getno sensitive capability
  • devrev_engagements_listno sensitive capability
  • devrev_engagements_updateno sensitive capability
  • devrev_groups_add_memberno sensitive capability
  • devrev_groups_createno sensitive capability
  • devrev_groups_getno sensitive capability
  • devrev_groups_listno sensitive capability
  • devrev_groups_list_membersno sensitive capability
  • devrev_groups_members_countno sensitive capability
  • devrev_groups_remove_memberno sensitive capability
  • devrev_groups_updateno sensitive capability
  • devrev_incidents_createno sensitive capability
  • devrev_incidents_deleteno sensitive capability
  • devrev_incidents_getno sensitive capability
  • devrev_incidents_groupno sensitive capability
  • devrev_incidents_listno sensitive capability
  • devrev_incidents_updateno sensitive capability
  • devrev_links_createno sensitive capability
  • devrev_links_deleteno sensitive capability
  • devrev_links_getno sensitive capability
  • devrev_links_listno sensitive capability
  • devrev_parts_createno sensitive capability
  • devrev_parts_deleteno sensitive capability
  • devrev_parts_getno sensitive capability
  • devrev_parts_listno sensitive capability
  • devrev_parts_moveno sensitive capability
  • devrev_parts_updateno sensitive capability
  • devrev_question_answers_createno sensitive capability
  • devrev_question_answers_deleteno sensitive capability
  • devrev_question_answers_getno sensitive capability
  • devrev_question_answers_listno sensitive capability
  • devrev_question_answers_updateno sensitive capability
  • devrev_recommendations_chatno sensitive capability
  • devrev_recommendations_replyno sensitive capability
  • devrev_rev_orgs_createno sensitive capability
  • devrev_rev_orgs_deleteno sensitive capability
  • devrev_rev_orgs_getno sensitive capability
  • devrev_rev_orgs_listno sensitive capability
  • devrev_rev_orgs_updateno sensitive capability
  • devrev_rev_users_createno sensitive capability
  • devrev_rev_users_getno sensitive capability
  • devrev_rev_users_listno sensitive capability
  • devrev_search_coreno sensitive capability
  • devrev_search_hybridno sensitive capability
  • devrev_server_infono sensitive capability
  • devrev_slas_createno sensitive capability
  • devrev_slas_getno sensitive capability
  • devrev_slas_listno sensitive capability
  • devrev_slas_transitionno sensitive capability
  • devrev_slas_updateno sensitive capability
  • devrev_tags_createno sensitive capability
  • devrev_tags_deleteno sensitive capability
  • devrev_tags_getno sensitive capability
  • devrev_tags_listno sensitive capability
  • devrev_tags_updateno sensitive capability
  • devrev_timeline_createno sensitive capability
  • devrev_timeline_deleteno sensitive capability
  • devrev_timeline_getno sensitive capability
  • devrev_timeline_listno sensitive capability
  • devrev_timeline_updateno sensitive capability
  • devrev_webhooks_createno sensitive capability
  • devrev_webhooks_listno sensitive capability
  • devrev_webhooks_updateno sensitive capability
  • devrev_works_countno sensitive capability
  • devrev_works_createno sensitive capability
  • devrev_works_deleteno sensitive capability
  • devrev_works_exportno sensitive capability
  • devrev_works_getno sensitive capability
  • devrev_works_listno sensitive capability
  • devrev_works_list_created_sinceno sensitive capability
  • devrev_works_list_modified_sinceno sensitive capability
  • devrev_works_updateno 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
v3.2.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/devrev-python-sdk/badge.svg)](https://mcptrustchecker.com/registry/devrev-python-sdk)
HTML
<a href="https://mcptrustchecker.com/registry/devrev-python-sdk"><img src="https://mcptrustchecker.com/registry/devrev-python-sdk/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/devrev-python-sdk/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 devrev-python-sdk --online --registry pypi

Use the free API → How scoring works

More in Developer Tools