Callrail (kanopi) MCP Server

@kanopi/callrail-mcp npm v1.0.1

Published by @kanopi — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Model Context Protocol (MCP) server for the CallRail API v3

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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 = 95/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 − 5 = 95. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 Unconstrained URL/host parameter "media_url" on "send_text_message"MTC-CAP-007

Tool "send_text_message" takes a URL/host parameter "media_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool send_text_message · inputSchema.properties.media_url

Tools 34

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

  • send_text_messagenetwork egress
  • create_companyno sensitive capability
  • create_outbound_callno sensitive capability
  • create_outbound_caller_idno sensitive capability
  • create_tagno sensitive capability
  • create_trackerno sensitive capability
  • delete_companyno sensitive capability
  • delete_tagno sensitive capability
  • delete_trackerno sensitive capability
  • get_accountno sensitive capability
Show 24 more tools ↓
  • get_callno sensitive capability
  • get_calls_summaryno sensitive capability
  • get_calls_timeseriesno sensitive capability
  • get_companyno sensitive capability
  • get_conversationno sensitive capability
  • get_form_submissionno sensitive capability
  • get_trackerno sensitive capability
  • get_userno sensitive capability
  • list_accountsno sensitive capability
  • list_callsno sensitive capability
  • list_companiesno sensitive capability
  • list_conversationsno sensitive capability
  • list_form_submissionsno sensitive capability
  • list_integrationsno sensitive capability
  • list_notificationsno sensitive capability
  • list_outbound_caller_idsno sensitive capability
  • list_tagsno sensitive capability
  • list_trackersno sensitive capability
  • list_usersno sensitive capability
  • update_callno sensitive capability
  • update_companyno sensitive capability
  • update_form_submissionno sensitive capability
  • update_tagno sensitive capability
  • update_trackerno 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
v1.0.1 latest A 95/100 1 1.13.0 2026-09-07

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/kanopi-callrail-mcp/badge.svg)](https://mcptrustchecker.com/registry/kanopi-callrail-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/kanopi-callrail-mcp"><img src="https://mcptrustchecker.com/registry/kanopi-callrail-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/kanopi-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 @kanopi/callrail-mcp --online

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