io.github.xie38388/looply
NPM · LOOPLY-MCP-SERVER · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree. 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 147 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability45
- 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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · looply-mcp-server
claude mcp add xie38388-looply -- npx -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": {
"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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +24
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 0 ▲ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −66
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- License: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Licence: MIT functional
- 27 Jul 26 +47
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → 0 ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- Licence: MIT functional
- 26 Jul 26 19
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 104 packages
104 packages in the resolved dependency tree · 104 deprecated · 32 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.