# @usercall/mcp Usercall MCP server for Agent API v1 - **Type:** MCP server - **Trust:** 60/100 (B), scored on the package rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 0.4.0 - **Author:** Unknown - **License:** MIT - **npm:** @usercall/mcp - **Endpoints:** streamable-http https://mcp.usercall.co - **Source:** https://github.com/junetic/usercall-mcp - **Endpoint health:** reachable (last checked 2026-10-07T05:52:38.220Z, 1 sample) — uptime is not a security property and is not part of the trust score - **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport) ## Trust 60/100 (B), scored on the package rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 0 days ## Security scan - **Status:** clean - **Scanned:** 2026-10-07T05:52:20.356Z - **Version scanned:** 0.4.0 - **CVEs:** none found by OSV at scan time ## Tools 17 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `create_study` — Create an interview study when you already know what happened and still need to learn why. Returns study_id and interview_link. Do not share the link yet. Call - `update_study` - `get_study_status` — Check whether a study is running, analyzing, or complete while interviews are in progress. running and analyzing mean wait and call this again. Do not treat tho - `get_study_results` — Read findings after get_study_status is complete. Use this when you need why, not another status check. Prefer format=summary for themes, insights, and risks. U - `simulate_interview` — Dry-run the interview after you create or edit a study, and before any real invite. Omit simulation_id to start. Pass that id on a later call to read the result - `review_study` — Check the interview guide before sharing it with a real participant. Use this when you want a read of the guide only. It does not read transcripts and it does n - `delete_study` — Permanently delete a study when it asks the wrong question or you must free the one active agent study. This removes the study and its interview calls and relea - `get_trigger_capabilities` — Check what Research Triggers can do before you design one. Use this when you are about to decide who gets invited. Supported: one event, an exact property or tr - `get_trigger_sdk_setup` — Get the SDK install snippet when list_trigger_events is empty and the product event must reach Usercall before a trigger can exist. Returns the install snippet, - `list_trigger_events` — List event names Usercall has received for this account in the last 30 days. Call this before create_research_trigger. Only an observed event can be used. If th - `get_trigger_event_schema` — Read observed properties and traits for one event, with types and sample values. Use this after list_trigger_events shows the event and you need a filter. Put e - `list_studies` — List studies before you create one. Use this to reuse a study_id and interview_link, or to pick a study for a trigger. Reuse a study that already asks the quest - `create_research_trigger` — Create a paused invite that asks people why after an event you have already observed. Use this only after a study exists and list_trigger_events has seen the ev - `list_research_triggers` — List research triggers with status and activation_url. Use this to recover a paused trigger's activation link for a human. The activation link is empty after a - `get_research_trigger` — Read one trigger when you already have trigger_id and need its status or activation_url while it is paused. Hand activation_url to a human. Agents cannot activa - `update_research_trigger` — Edit a trigger's targeting, sampling, cooldown, daily cap, intercept copy, or delivery. Use this to change who is invited or to pause a trigger. Never set statu - `delete_research_trigger` — Permanently delete a research trigger when the event or the study is wrong. Interviews already completed are kept. This cannot be undone. To pause without delet ## Install **Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for. **Cautions** (coverage gaps and advisories — never blocking) - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"mcp\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"@usercall/mcp\"\n ],\n \"env\": {\n \"USERCALL_API_KEY\": \"\"\n }\n }\n }\n}" ``` **Credentials it will ask for** (names only — Forge never holds a value): - `USERCALL_API_KEY` — Usercall API Key (required) Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one. - This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset. ## Blast radius Extensive blast radius — deletes data; runs locally and hosted. - Floor 57, ceiling 57 (tier: extensive) - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/%40usercall%2Fmcp - Install plan: https://forgeregistry.com/api/v1/packages/%40usercall%2Fmcp/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/%40usercall%2Fmcp - HTML page: https://forgeregistry.com/registry/%40usercall%2Fmcp - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.