Callrail (pghdma) MCP Server

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.

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.
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 Untrusted input can drive an external actionMTC-FLOW-005

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

Tools 59

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

  • delete_notificationnetwork egress
  • get_call_recordingingests untrusted input
  • update_sms_threadnetwork egress
  • add_call_tagsno sensitive capability
  • bulk_update_callsno sensitive capability
  • call_eligibility_checkno sensitive capability
  • call_statsno sensitive capability
  • call_summaryno sensitive capability
  • call_timeseriesno sensitive capability
  • compare_periodsno sensitive capability
Show 49 more tools ↓
  • create_companyno sensitive capability
  • create_form_submissionno sensitive capability
  • create_notificationno sensitive capability
  • create_outbound_callno sensitive capability
  • create_tagno sensitive capability
  • create_trackerno sensitive capability
  • create_userno sensitive capability
  • delete_companyno sensitive capability
  • delete_tagno sensitive capability
  • delete_trackerno sensitive capability
  • delete_userno sensitive capability
  • form_statsno sensitive capability
  • get_callno sensitive capability
  • get_call_page_viewsno sensitive capability
  • get_call_transcriptno sensitive capability
  • get_companyno sensitive capability
  • get_form_submissionno sensitive capability
  • get_integrationno sensitive capability
  • get_lead_timelineno sensitive capability
  • get_sms_threadno sensitive capability
  • get_tagno sensitive capability
  • get_text_messageno sensitive capability
  • get_trackerno sensitive capability
  • get_userno sensitive capability
  • get_webhookno sensitive capability
  • list_accountsno sensitive capability
  • list_callsno sensitive capability
  • list_companiesno sensitive capability
  • list_form_submissionsno sensitive capability
  • list_integrationsno sensitive capability
  • list_leadsno sensitive capability
  • list_notificationsno sensitive capability
  • list_sms_threadsno sensitive capability
  • list_tagsno sensitive capability
  • list_text_messagesno sensitive capability
  • list_trackersno sensitive capability
  • list_usersno sensitive capability
  • list_webhooksno sensitive capability
  • remove_call_tagsno sensitive capability
  • search_calls_by_numberno sensitive capability
  • spam_detectorno sensitive capability
  • update_callno sensitive capability
  • update_companyno sensitive capability
  • update_form_submissionno sensitive capability
  • update_notificationno sensitive capability
  • update_tagno sensitive capability
  • update_trackerno sensitive capability
  • update_userno sensitive capability
  • usage_summaryno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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
v1.1.3 latest A 96/100 1 1.8.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/callrail-mcp/badge.svg)](https://mcptrustchecker.com/registry/callrail-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/callrail-mcp"><img src="https://mcptrustchecker.com/registry/callrail-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/callrail-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 callrail-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Callrail 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Business & CRM