callrail-mcp
PyPI
v1.1.3
Published by pghdma — 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.
Untrusted-input tools ([get_call_recording]) co-exist with external-action tools ([delete_notification, update_sms_thread]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [get_call_recording] → sinks [delete_notification, update_sms_thread]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow get_call_recording → delete_notification
Each tool and what it can reach — statically extracted from the published source.
delete_notificationnetwork egressget_call_recordingingests untrusted inputupdate_sms_threadnetwork egressadd_call_tagsno sensitive capabilitybulk_update_callsno sensitive capabilitycall_eligibility_checkno sensitive capabilitycall_statsno sensitive capabilitycall_summaryno sensitive capabilitycall_timeseriesno sensitive capabilitycompare_periodsno sensitive capabilitycreate_companyno sensitive capabilitycreate_form_submissionno sensitive capabilitycreate_notificationno sensitive capabilitycreate_outbound_callno sensitive capabilitycreate_tagno sensitive capabilitycreate_trackerno sensitive capabilitycreate_userno sensitive capabilitydelete_companyno sensitive capabilitydelete_tagno sensitive capabilitydelete_trackerno sensitive capabilitydelete_userno sensitive capabilityform_statsno sensitive capabilityget_callno sensitive capabilityget_call_page_viewsno sensitive capabilityget_call_transcriptno sensitive capabilityget_companyno sensitive capabilityget_form_submissionno sensitive capabilityget_integrationno sensitive capabilityget_lead_timelineno sensitive capabilityget_sms_threadno sensitive capabilityget_tagno sensitive capabilityget_text_messageno sensitive capabilityget_trackerno sensitive capabilityget_userno sensitive capabilityget_webhookno sensitive capabilitylist_accountsno sensitive capabilitylist_callsno sensitive capabilitylist_companiesno sensitive capabilitylist_form_submissionsno sensitive capabilitylist_integrationsno sensitive capabilitylist_leadsno sensitive capabilitylist_notificationsno sensitive capabilitylist_sms_threadsno sensitive capabilitylist_tagsno sensitive capabilitylist_text_messagesno sensitive capabilitylist_trackersno sensitive capabilitylist_usersno sensitive capabilitylist_webhooksno sensitive capabilityremove_call_tagsno sensitive capabilitysearch_calls_by_numberno sensitive capabilityspam_detectorno sensitive capabilityupdate_callno sensitive capabilityupdate_companyno sensitive capabilityupdate_form_submissionno sensitive capabilityupdate_notificationno sensitive capabilityupdate_tagno sensitive capabilityupdate_trackerno sensitive capabilityupdate_userno sensitive capabilityusage_summaryno sensitive capabilityCross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.3 latest |
A 96/100 | 1 | 1.8.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 callrail-mcp --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
Security scan results for the 21e14 MCP server.
Security scan results for the Agentgate Ucp MCP server.
Security scan results for the Autotask MCP server.
Security scan results for the B2c Dx MCP server.
Security scan results for the Brreg MCP server.
Security scan results for the Canlii MCP server.