io.github.xie38388/looply
NPM · LOOPLY-MCP-SERVER · SCANNED SEP 20
Looply AI call center MCP Server - manage calls, leads, contacts, and analytics.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 34 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 195 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability43
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1184 tokens (~49/item across 24 items; 23 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.xie38388/looply MCP server?
io.github.xie38388/looply runs locally as an npm package, launched with npx -y looply-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · looply-mcp-server
claude mcp add xie38388-looply -- npx -y looply-mcp-server
{
"mcpServers": {
"xie38388-looply": {
"command": "npx",
"args": [
"-y",
"looply-mcp-server"
]
}
}
} {
"servers": {
"xie38388-looply": {
"command": "npx",
"args": [
"-y",
"looply-mcp-server"
]
}
}
} codex mcp add xie38388-looply -- npx -y looply-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xie38388-looply": {
"type": "local",
"command": [
"npx",
"-y",
"looply-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add xie38388-looply --command npx --arg -y --arg looply-mcp-server
mcp_servers:
xie38388-looply:
command: "npx"
args: ["-y", "looply-mcp-server"] {
"McpServers": {
"xie38388-looply": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"looply-mcp-server"
]
}
}
} assistant mcp add xie38388-looply -t stdio -c npx -a -y looply-mcp-server
{
"mcpServers": {
"xie38388-looply": {
"command": "npx",
"args": [
"-y",
"looply-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/looply-mcp-server@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 104 packages
| Packages resolved | 104 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
complete_callback ~43
Mark a callback as completed with optional outcome notes.
| Name | Type | Req | Description |
|---|---|---|---|
| callbackId | number | yes | The callback ID to complete |
| outcome | string | – | Outcome notes from the callback |
No output schema declared.
No examples provided.
create_callback ~77
Schedule a callback for a contact.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | number | yes | Contact ID to call back |
| notes | string | – | Notes for the callback |
| priority | string | – | Callback priority |
| reason | string | – | Reason for the callback |
| scheduledAt | string | yes | When to call back (ISO 8601 datetime) |
No output schema declared.
No examples provided.
create_contact ~118
Create a new contact in the CRM.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Contact's company |
| string | – | Contact's email | |
| firstName | string | yes | Contact's first name |
| lastName | string | – | Contact's last name |
| notes | string | – | Additional notes about the contact |
| phone | string | – | Contact's phone number |
| source | string | – | How the contact was acquired (e.g., 'inbound_call', 'referral') |
| title | string | – | Contact's job title |
No output schema declared.
No examples provided.
create_lead ~111
Create a new lead in the sales pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | number | – | Associated contact ID |
| description | string | – | Lead description |
| priority | string | – | Lead priority |
| source | string | – | Lead source (e.g., 'ai_call', 'website', 'referral') |
| stage | string | – | Pipeline stage |
| title | string | yes | Lead title (e.g., 'New HVAC Installation - John Smith') |
| value | number | – | Estimated deal value in dollars |
No output schema declared.
No examples provided.
get_business_hours ~16
Get the organization's business hours configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_call ~35
Get detailed information about a specific call, including transcript and AI summary.
| Name | Type | Req | Description |
|---|---|---|---|
| callId | number | yes | The call ID to retrieve |
No output schema declared.
No examples provided.
get_call_analytics ~57
Get call analytics for a date range: trends, sentiment breakdown, qualification breakdown, hourly distribution.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | End date (YYYY-MM-DD) |
| startDate | string | yes | Start date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_contact ~29
Get detailed information about a specific contact.
| Name | Type | Req | Description |
|---|---|---|---|
| contactId | number | yes | The contact ID to retrieve |
No output schema declared.
No examples provided.
get_dashboard_stats ~34
Get the main dashboard statistics: total calls, answer rate, total leads, pipeline value, conversion rate, avg call duration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_organization ~17
Get the current organization's profile and settings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_script ~32
Get a specific AI call script with all its steps.
| Name | Type | Req | Description |
|---|---|---|---|
| scriptId | number | yes | The script ID to retrieve |
No output schema declared.
No examples provided.
get_usage_summary ~27
Get the organization's usage summary for the current billing period (calls, minutes, AI processing).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_callbacks ~41
List pending callbacks that need to be made, sorted by priority.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results |
| status | string | – | Filter by callback status |
No output schema declared.
No examples provided.
list_calls ~90
List recent calls with optional filters. Returns call ID, caller info, status, duration, sentiment, and qualification.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Filter by call direction |
| limit | number | – | Number of calls to return (max 100) |
| offset | number | – | Offset for pagination |
| qualification | string | – | Filter by lead qualification |
| status | string | – | Filter by call status |
No output schema declared.
No examples provided.
list_contacts ~54
List contacts in the CRM with optional search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of contacts to return |
| offset | number | – | Offset for pagination |
| search | string | – | Search by name, email, or phone |
No output schema declared.
No examples provided.
list_leads ~74
List leads in the sales pipeline with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of leads to return |
| offset | number | – | Offset for pagination |
| priority | string | – | Filter by priority |
| search | string | – | Search by title or description |
| stage | string | – | Filter by pipeline stage |
No output schema declared.
No examples provided.
list_qualification_rules ~21
List all AI qualification rules used to score incoming callers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_routing_rules ~20
List all smart routing rules configured for the organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_scripts ~18
List all AI call scripts configured for the organization.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_calls ~46
Search calls by caller name, phone number, or intent keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results |
| query | string | yes | Search query (name, phone, or keyword) |
No output schema declared.
No examples provided.
update_business_hours ~76
Update the organization's business hours. Provide a schedule object with days and time ranges.
| Name | Type | Req | Description |
|---|---|---|---|
| afterHoursAction | string | – | What to do after hours |
| schedule | object | yes | Schedule per day (monday, tuesday, ... sunday) |
| timezone | string | yes | Timezone (e.g., 'America/New_York') |
No output schema declared.
No examples provided.
update_lead ~75
Update an existing lead's stage, priority, value, or other fields.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Updated description |
| leadId | number | yes | The lead ID to update |
| priority | string | – | New priority |
| stage | string | – | New pipeline stage |
| value | number | – | Updated deal value |
No output schema declared.
No examples provided.
update_script ~67
Update an AI call script's name, description, or active status.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description |
| isActive | boolean | – | Enable or disable the script |
| name | string | – | New script name |
| scriptId | number | yes | The script ID to update |
No output schema declared.
No examples provided.
What is the io.github.xie38388/looply MCP server?
io.github.xie38388/looply is an MCP server listed in the public MCP registry as io.github.xie38388/looply. Looply AI call center MCP Server - manage calls, leads, contacts, and analytics. This page covers its npm package (looply-mcp-server).
Is the io.github.xie38388/looply MCP server safe to use?
io.github.xie38388/looply scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.xie38388/looply MCP server expose?
io.github.xie38388/looply exposes 23 tools: list_calls, get_call, search_calls, list_contacts, create_contact, and 18 more. Their descriptions and schemas cost roughly 1,178 tokens of context every time the server is loaded.
Is the io.github.xie38388/looply MCP server still maintained?
io.github.xie38388/looply is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.xie38388/looply MCP server under?
io.github.xie38388/looply declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.