io.github.xie38388/looply

MCPcommunity
v1.0.1io.github.xie38388UnknownUpdated 7mo agonpmGitHub

Looply AI call center MCP Server - manage calls, leads, contacts, and analytics.

Expose your Looply AI call center data to external AI agents (Claude Desktop, Manus, Cursor, etc.) via the Model Context Protocol. Go to Settings → API Keys in your Looply dashboard at looplyauto.com and create a new key. Add Looply as an MCP server in Manus settings with the same environment variables. Add to in your project: Ask your AI agent: "Show me today's call summary from Looply"…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
7mo agoLast update
Package
Authorio.github.xie38388
LicenseUnknown
Version1.0.1
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface23 tools · none privileged
Security scan✓ Cleanv1.0.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

23 tools · none privileged
Statically extracted from the published packagev1.0.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_callsNo description published

This tool published no description. Forge does not invent one.

get_callNo description published

This tool published no description. Forge does not invent one.

search_callsNo description published

This tool published no description. Forge does not invent one.

list_contactsNo description published

This tool published no description. Forge does not invent one.

create_contactNo description published

This tool published no description. Forge does not invent one.

get_contactNo description published

This tool published no description. Forge does not invent one.

list_leadsNo description published

This tool published no description. Forge does not invent one.

create_leadNo description published

This tool published no description. Forge does not invent one.

update_leadNo description published

This tool published no description. Forge does not invent one.

get_dashboard_statsNo description published

This tool published no description. Forge does not invent one.

get_call_analyticsNo description published

This tool published no description. Forge does not invent one.

list_scriptsNo description published

This tool published no description. Forge does not invent one.

get_scriptNo description published

This tool published no description. Forge does not invent one.

update_scriptNo description published

This tool published no description. Forge does not invent one.

list_callbacksNo description published

This tool published no description. Forge does not invent one.

create_callbackNo description published

This tool published no description. Forge does not invent one.

complete_callbackNo description published

This tool published no description. Forge does not invent one.

get_business_hoursNo description published

This tool published no description. Forge does not invent one.

update_business_hoursNo description published

This tool published no description. Forge does not invent one.

list_routing_rulesNo description published

This tool published no description. Forge does not invent one.

list_qualification_rulesNo description published

This tool published no description. Forge does not invent one.

get_organizationNo description published

This tool published no description. Forge does not invent one.

get_usage_summaryNo description published

This tool published no description. Forge does not invent one.

0 of 23 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Expose your Looply AI call center data to external AI agents (Claude Desktop, Manus, Cursor, etc.) via the Model Context Protocol. Go to Settings → API Keys in your Looply dashboard at looplyauto.com and create a new key. Add Looply as an MCP server in Manus settings with the same environment variables. Add to in your project: Ask your AI agent: "Show me today's call summary from Looply" ------|-------------| | List recent calls with filters (status, direction, qualification) | | Get call…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.