AI_Calling Retell HubSpot MCP Server (tech4lifeatepisode/AI_Calling) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 4 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
58/100

AI_Calling Retell HubSpot MCP Server

Enables AI assistants to check tour availability, book tours via HubSpot Scheduler, and log call sessions to Supabase.

→ tech4lifeatepisode/AI_Calling· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

tech4lifeatepisode

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: HUBSPOT_ACCESS_TOKEN, MCP_SERVER_SECRET, RETELL_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes4 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

get_tour_availability

Checks HubSpot availability for either a virtual or in-person tour.

book_tour

Books a HubSpot tour after the guest explicitly confirms the selected slot.

log_retell_session

Saves Retell call/session metadata into Supabase.

log_tour_preference

Logs tour interest even if the guest does not complete booking.

// known CVEs in dependencies3 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretHUBSPOT_ACCESS_TOKENHubSpot Private App Retell Connection token only
🔐 secretMCP_SERVER_SECRETRandom secret; Retell sends Authorization: Bearer <this>
🔐 secretRETELL_API_KEYRetell API key (required for call sync)
configRUN_BOOKING_TESTtrue TEST_BOOKING_EMAIL=you@example.com npx tsx scripts/testBookTour.ts
configTEST_BOOKING_EMAILRUN_BOOKING_TEST=true =you@example.com npx tsx scripts/testBookTour.ts
configTEST_BOOKING_FIRST_NAME
configTEST_BOOKING_LAST_NAME
configTEST_BOOKING_PHONE
configTEST_TOUR_TYPE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySUPABASE_SERVICE_ROLE_KEY
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — get_tour_availability (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); book_tour (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); log_retell_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 0/4 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/tech4lifeatepisode/ai_calling?variant=verified)](https://m8ven.ai/mcp/tech4lifeatepisode/ai_calling)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 38dc279a4756e3873f64cce503f1e614ccbd41bc
code hash: a1398b140beaa813cee4dbb609af9a03c22a41f2ec5e8eea9d5eb278fda5fa94
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client