MCP tool reference · #254 of 563 by publishers
report_issue
Exposed by 13 servers from 12 publishers, read from the live servers by the Serverdex check; most of them sit in Communication; 46.2% of them take a category parameter; the most-starred is ProductClank (12 stars).
report_issue(category: string, contact?: any, expected?: string, message: string, summary: string, …)Parameters
share = % of the 13 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| category | string | 46.2% | 50% | What part of the product this issue relates to. |
| contact | — | 30.8% | 0% | Optional email address for a reply; nothing is mailed to it automatically. |
| expected | string | 30.8% | 25% | 사용자가 맞다고 본 값이 있으면 |
| message | string | 30.8% | 100% | The report, in plain words: what is missing or wrong. |
| summary | string | 30.8% | 100% | One-line summary of the problem (max 200 characters). |
| description | string | 23.1% | 100% | Full details: what happened, what you expected, and any relevant call or time. |
| severity | string | 23.1% | 0% | How badly this is affecting the business. |
| business_id | string | 15.4% | 0% | Business ID (optional only when the token can access exactly one business). |
| context | object | 15.4% | 0% | Arguments you passed, the error text, what you already tried. Never include secrets. |
| detail | string | 15.4% | 0% | Optional short note (no secrets or personal data) |
| error_code | string | 15.4% | 0% | Error code returned by the tool, e.g. UPSTREAM_ERROR |
| kind | string | 15.4% | 0% | '결함'=사용자가 답이 틀렸다고 제보해 달라고 한 경우(기본). '질문기록'=기능요청 — 사용자가 '이런 질문에도 답하게 해 달라'·'이 데이터도 넣어 달라'처럼 **개선 요청을 전해 달라고 한 경우** — 그 질문과 무엇이 없었는지를 넘긴다(응답에 그 질문이 어느 도구 축에 해당하는지 |
Source: the input schema each server returns for report_issue, aggregated over the 13 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with report_issue
13 of 13 · 12 publishers · 13 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes report_issue |
|---|---|---|---|---|---|---|
| 1 | ProductClankcovariance-network · Health & Science | covariance-network | Health & Science | 12 | yes | Tell the ProductClank team a tool failed, returned something that doesn't make sense, or that you're stuck and can't finish the user's task. Free. A human is alerted and replies (read it with get_support_status). Use this INSTEAD of retrying a failing call in a loop — but not for expected guards the error already explains (insufficient credits, a confirmation prompt, a spend cap): relay those to t |
| 2 | Warp Agent MCPwarpfreight · E-commerce & Retail | warpfreight | E-commerce & Retail | 8 | yes | Report a problem with Warp's tools to the Warp team. Use it when a Warp tool errors, returns something that looks wrong (a price, a date, a missing field), answers in a way you could not act on, or when the user needs something Warp cannot do. Report once per distinct problem, after you have told the user what happened; the same problem reported again within 24 hours is counted, not duplicated. It |
| 3 | Toolradarnadeus · Developer Tools | nadeus | Developer Tools | 4 | yes | Report a data problem you spotted (wrong price, dead tool, missing feature). Files it to the Toolradar verification queue. Use this when our data looks wrong so we can fix it: what Toolradar shows, what the vendor's own page says, and that page as evidence. A report on a tool and field that already has an open ticket is added to it; a pricing report also queues the tool's pricing page for a fresh |
| 4 | EchoPai (回声投研)echopai · AI & Agents | echopai | AI & Agents | 1 | yes | 当实际结果与工具声明明显矛盾,或使用返回的游标、偏移量仍无法推进时,免费调用 report_issue 一次。正常空结果、预期权限限制无需提交;无需为复现再次执行付费查询。只写脱敏摘要,省略对话、原文与凭据。 |
| 5 | CallMCP — Phone Call MCP Servercallmcp · Communication | callmcp | Communication | 1 | yes | Report a problem with your KaiCalls agent, phone number, billing, or account. Saves the report to your change history and notifies KaiCalls support so a person can follow up on anything broken or not working as expected. |
| 6 | KaiCallskaicalls · Communication | kaicalls | Communication | 1 | yes | Report a problem with your KaiCalls agent, phone number, billing, or account. Saves the report to your change history and notifies KaiCalls support so a person can follow up on anything broken or not working as expected. |
| 7 | Contract Compasssallim-app · Legal & Government | sallim-app | Legal & Government | — | yes | 사용자가 **오류 제보·개선 요청·문의를 운영자에게 전해 달라고 했을 때만** 쓴다. 쓰는 때: 사용자가 "이 조문 인용이 틀렸으니 신고해 줘", "운영자에게 알려 줘", "이런 질문도 답하게 해 달라고 전해 줘"처럼 제보·요청을 부탁했을 때. 보내기 전에 무엇이 전달되는지 사용자에게 알린다. 사용자가 오류·불만·개선 희망·기관 도입 같은 이용 문의·후원 의사를 말했지만 전달을 부탁하지는 않았다면, 부르지 말고 "운영자에게 전해 드릴까요?"를 한 줄로 물어 동의할 때만 부른다(거절·무반응이면 다시 묻지 않는다). 응답의 접수번호(ref)와 회신 방법(reply_path)을 사용자에게 알린다. 쓰지 않는 때: 사용자가 요청하지 않았는데 질문을 남기려고 부르 |
| 8 | Korea Realtysallim-app · Finance | sallim-app | Finance | — | yes | 사용자가 **답변 오류 제보나 개선 요청을 전해 달라고 했을 때만** 운영자에게 보낸다. 쓰는 때: 사용자가 "이거 틀렸으니 신고해 줘", "운영자에게 알려 줘", "이런 데이터도 넣어 달라고 전해 줘"처럼 제보·요청을 부탁했을 때. 보내기 전에 무엇이 전달되는지 사용자에게 알린다. kind='결함'은 틀린 답 제보, kind='질문기록'은 기능·개선 요청, kind='유료이용문의'· '후원문의'는 사용자가 유료 이용 희망·후원 의사를 운영자에게 전해 달라고 한 경우다. 사용자가 오류·불만·개선 희망·유료 이용 희망·후원 의사를 말했지만 전달을 부탁하지는 않았다면, 부르지 말고 "운영자에게 전해 드릴까요?"를 한 줄로 물어 동의할 때만 부른다(거절·무반응이면 |
| 9 | WhatsDownNowjacobpmiller · APIs & Integrations | jacobpmiller | APIs & Integrations | — | yes | Tell WhatsDownNow that your agent or app hit an error talking to a tracked service. Use this when you see 5xx, timeouts, or rate limits, even if our status page still says up — reports from 6+ independent networks within 30 minutes are flagged as an 'Unverified agent-report spike' (it never changes the official/probe verdict). Fields: service (slug or name), error_type (5xx, timeout, rate_limit, a |
| 10 | BotKelpbotkelp · Developer Tools | botkelp | Developer Tools | — | yes | Report a catalog/code bug or request a component (files an issue on botkelp/components). Signed-in account, 10/day. No secrets. |
| 11 | Leadgen ONRC Romaniadarksider4all · Business & CRM | darksider4all | Business & CRM | — | yes | Report to the person who runs Leadgen what is missing or wrong: a missing field, company or source (kind 'gap'), a wrong company record ('wrong_record', pass its cui), a bug, an idea. Free, never counted as a lookup. contact is optional (an address for a reply); nothing is mailed to it automatically. Registry records are corrected at the source (ONRC) and arrive with the next snapshot. |
| 12 | Contract Compasskwenhwang · Legal & Government | kwenhwang | Legal & Government | — | yes | 사용자가 **오류 제보·개선 요청·문의를 운영자에게 전해 달라고 했을 때만** 쓴다. 쓰는 때: 사용자가 "이 조문 인용이 틀렸으니 신고해 줘", "운영자에게 알려 줘", "이런 질문도 답하게 해 달라고 전해 줘"처럼 제보·요청을 부탁했을 때. 보내기 전에 무엇이 전달되는지 사용자에게 알린다. 사용자가 오류·불만·개선 희망·기관 도입 같은 이용 문의·후원 의사를 말했지만 전달을 부탁하지는 않았다면, 부르지 말고 "운영자에게 전해 드릴까요?"를 한 줄로 물어 동의할 때만 부른다(거절·무반응이면 다시 묻지 않는다). 응답의 접수번호(ref)와 회신 방법(reply_path)을 사용자에게 알린다. 쓰지 않는 때: 사용자가 요청하지 않았는데 질문을 남기려고 부르 |
| 13 | Agents Get Paid Kit — x402 MCP + Unlock ($49)agentsgetpaidmore · Crypto & Web3 | agentsgetpaidmore | Crypto & Web3 | — | yes | Report a product or policy issue (logged server-side). Free. |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.