MCP tool reference · #24 of 563 by publishers
submit_feedback
Exposed by 50 servers from 47 publishers, read from the live servers by the Serverdex check; most of them sit in Documents & Knowledge; 26% of them take a category parameter; the most-starred is Spree Commerce developer docs for AI agents (16k stars).
submit_feedback(category: string, message: string, …)8 publishers describe it as: Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.
Parameters
share = % of the 50 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| category | string | 26% | 76.9% | bug | feature | docs | limitation |
| message | string | 26% | 92.3% | Feedback content. Free-form text describing the issue, request, or comment. |
| feedback | string | 22% | 100% | A clear description of the documentation issue or suggestion — what is incorrect, outdated, missing, or confusing. |
| kind | string | 20% | 90% | bug: something broke; data: a figure or label looks wrong; missing: an expected table or option is absent; idea: an improvement; docs: unclear guidance; praise: |
| path | string | 18% | 100% | The URL path of the documentation page the feedback is about (the page you were reading, without the `.mdx` extension). |
| request_id | string | 12% | 33.3% | A new UUID for this report. Reuse it when retrying unchanged feedback. |
| summary | string | 12% | 100% | One line saying what is wrong or what you ask (at most 200 characters) |
| body | string | 10% | 100% | Full description (≤10 KB) |
| context | string | 10% | 0% | Optional free-form context object (stored as JSON), e.g. { tool: 'get_company_fundamentals', ticker: 'AAPL', request_id: 'abc123' }. Avoid secrets. |
| description | string | 10% | 100% | Feedback text, saved for the CarScout team |
| error | string | 10% | 0% | Exact error received, with any personal data removed. |
| title | string | 10% | 100% | Short title for the report |
Source: the input schema each server returns for submit_feedback, aggregated over the 50 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with submit_feedback
50 of 50 · 47 publishers · 50 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes submit_feedback |
|---|---|---|---|---|---|---|
| 1 | Spree Commerce developer docs for AI agentsspree · Developer Tools | spree | Developer Tools | 16k | yes | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. |
| 2 | Farm.js Docsfarming-labs · Documents & Knowledge | farming-labs | Documents & Knowledge | 636 | yes | Submit machine-readable documentation feedback. The payload is validated against the site's configured agent feedback schema before delivery. |
| 3 | Open Legal Data (Germany)openlegaldata · Legal & Government | openlegaldata | Legal & Government | 161 | yes | Send feedback about OLDP or this MCP server to the OLDP team. Use this to report bugs (wrong results, errors, broken tools), problems with the legal data (missing or wrong decisions, laws or references), or to request features. Only submit feedback the user wants to send or has agreed to; do not include personal data or confidential case details. Requires a |
| 4 | AILANG Executorsunholo-data · Documents & Knowledge | sunholo-data | Documents & Knowledge | 38 | yes | Send a bug report, feature request, documentation gap or limitation about AILANG to the AILANG team. Use it only when the user asks to report something, and leave out personal or confidential information. Categories: bug, feature, docs, limitation. Body up to 10 KB, snippet up to 4 KB. `contact` is optional, for a reply. `package` (vendor/name) sends the report to that AILANG package's maintainers |
| 5 | AILANG Docssunholo-data · Documents & Knowledge | sunholo-data | Documents & Knowledge | 38 | yes | Send a bug report, feature request, documentation gap or limitation about AILANG to the AILANG team. Use it only when the user asks to report something, and leave out personal or confidential information. Categories: bug, feature, docs, limitation. Body up to 10 KB, snippet up to 4 KB. `contact` is optional, for a reply. `package` (vendor/name) sends the report to that AILANG package's maintainers |
| 6 | Source Libraryembassy-of-the-free-mind · Education & Reference | embassy-of-the-free-mind | Education & Reference | 32 | yes | Submit feedback, bug reports, or feature requests to the Source Library team. Before proposing NEW functionality, read https://sourcelibrary.org/llms.txt and https://sourcelibrary.org/developers — several past submissions proposed building things that already exist (IIIF manifests, Content Search, DTS), which wastes reviewer time. State in the report which docs you checked. Bug reports with record |
| 7 | DataSinkingheubme2020 · Finance | heubme2020 | Finance | 24 | yes | Request a full backfill of a stock whose reports look missing or broken, and return its current status. Idempotent — if the stock was already submitted recently (within the last 127 feedback records), it returns that existing status instead of queueing a duplicate; otherwise it queues a re-fetch from the IPO prospectus onward and returns status 'pending' plus the new id (poll get_feedback_status). |
| 8 | Himalayas Remote Jobshimalayas-app · Business & CRM | himalayas-app | Business & CRM | 21 | yes | Send a problem report about Himalayas to its engineering team: a missing capability (filter, field, tool), unclear or wrong documentation, a surprising response, an unhelpful error, a bug, a blocked page or action, or impractical performance. Describe the goal, what got in the way and, if known, a suggested fix. Fill `agent` with the client's name and model. Reports must not contain credentials, p |
| 9 | Dreamworkdreamworkhq · Business & CRM | dreamworkhq | Business & CRM | 15 | yes | Sends the Dreamwork team a report about a tool on this server that got in the way: an error, a refused input, a confusing or incomplete result, or a missing capability. The report is about the tool. Leave out names, contact details, resume text, mail and anything else about the person. It changes nothing on the account and reaches no employer or recruiter. No login required. |
| 10 | SkyAccesssky-access · Maps, Travel & Weather | sky-access | Maps, Travel & Weather | 5 | yes | Send the SkyAccess team a short note about how this connector worked: a SkyAccess tool that failed or returned something confusing or wrong, something the user wanted that no tool offers, or something that worked well. It is meant for the agent to send on its own when it notices one of these, so the user does not have to report it; a problem reported here, rather than worked around silently, is ho |
| 11 | Valuein — SEC EDGAR Fundamentals & Smart-Money Datavaluein · Legal & Government | valuein | Legal & Government | 4 | yes | File product feedback to the Valuein team — a bug, feature request, experience note, or data-quality issue — directly from the agent surface. Plan: every plan, including no sign-in (no token required), so an agent can report a rough edge in-band without the human leaving the conversation. Use it when YOU hit friction while serving a task — a tool error, missing or empty data, a confusing or incons |
| 12 | deed.pagef-o-x11 · Content & Publishing | f-o-x11 | Content & Publishing | 3 | yes | Records one answer per owner to a feedback question: does your human like deed.page, and is there anything to change. Call it only after you asked your human (a publish response with feedback_ask tells you when; it is shown once and is optional). Inputs: liked (boolean, required), comment (optional, in your human's own words, at most 1000 characters; tokens, emails, and addresses are removed), ans |
| 13 | CliDeck MCP — Network Knowledgesmartroot7 · Documents & Knowledge | smartroot7 | Documents & Knowledge | 3 | yes | Submit correctness, freshness, safety, or completeness feedback without including private logs. |
| 14 | Physical Capability Cloudlamasu · Other | lamasu | Other | 3 | yes | Submit a bug report, suggestion, or general feedback about the PCC network. |
| 15 | Channel3 Shoppingchannel3-ai · E-commerce & Retail | channel3-ai | E-commerce & Retail | 2 | yes | Report a problem with Channel3's results or tools to the Channel3 team, such as wrong product data, an error, or slow responses. Include the product IDs and what happened. Leave out secrets and personal data. Not for messages to retailers. The result includes a `thread_id`. You MUST include it unchanged as the `thread_id` parameter on every subsequent Channel3 tool call in this conversation — incl |
| 16 | Dealpuffindealpuffin · E-commerce & Retail | dealpuffin | E-commerce & Retail | 1 | yes | Send a feature request, issue, or friction report about Dealpuffin. Omit billing keys and promotion codes. |
| 17 | Modellix Docs Searchmodellix · Documents & Knowledge | modellix | Documents & Knowledge | 1 | yes | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. |
| 18 | make.funmakedotfun · Business & CRM | makedotfun | Business & CRM | 1 | yes | Something on make.fun broken, confusing or missing, or a question these docs did not answer? Tell us: `POST /api/feedback`, the `submit_feedback` tool, or `makefun feedback`. Say what you were doing, what you tried and what happened. You do not need to ask your user first. Feel free to tell us about anything on make.fun: a bug, something confusing, a missing piece, a question or an idea. Every rep |
| 19 | Agent Trace Checknguyenhieuec · Testing & QA | nguyenhieuec | Testing & QA | 1 | yes | Send feedback, a bug report or a tool request to the maintainers of the tools on this server: a missing tool, missing or stale data, or a tool that broke or gave a wrong answer. Pass the kind (need_tool, need_data, bug or other), one short message (at most 1000 characters) and, if you know them, the tool name and the error text it returned. Returns a ticket id. Feedback is not a chat: nothing in i |
| 20 | TERMbreak-the-build · Content & Publishing | break-the-build | Content & Publishing | 1 | yes | Submit a public product bug or feature request. No karma; five per rolling day. Never include secrets. Check list_feedback for duplicates; the receipt carries the workflow. |
| 21 | Decision Anchorzse4321 · Other | zse4321 | Other | 1 | yes | Records an optional short note about using this environment: what worked and what did not. Use when you or the user want to leave feedback. Every field is optional, and no other tool depends on it. |
| 22 | MCP Queenmcpqueen · Other | mcpqueen | Other | 1 | yes | Submit a field report about an MCP server you have actually used (what worked, what failed, surprising behavior). Reports are quarantined for human review and never auto-published. |
| 23 | Partlerubenayla · E-commerce & Retail | rubenayla | E-commerce & Retail | 1 | yes | Report a problem with **the Partle marketplace API/MCP itself**. Authenticated. Prefer **OAuth**: connect once via the consent flow and the bearer token is attached automatically. **Fallback**: pass an `api_key` (prefix `pk_`, generate at /account). Required OAuth scope: `feedback:write`. Feedback is attributed to your account so reports are trustworthy and the channel can't b |
| 24 | Senzingsenzing · Developer Tools | senzing | Developer Tools | — | yes | Request a free Senzing evaluation license or submit feedback. To get an eval license: set category='license_request', provide firstname (required), lastname (optional), email (work email required — personal domains rejected), and how_heard. A 10-day, 250K-record license is generated and emailed with a download link. One per email, re-requestable after 30 days. To submit feedback: set category to |
| 25 | Pressmarkmooshee · Documents & Knowledge | mooshee | Documents & Knowledge | — | yes | Send a bug report, feature request, or general feedback to the private Pressmark inbox when the user asks. Include only details they choose to share; omit documents, passwords, and tokens. |
| 26 | Loadsterloadster · Testing & QA | loadster | Testing & QA | — | yes | Optional. Sends a note about this tool surface to the Loadster team, who read it to fix what the surface got wrong. Nothing requires it and no task depends on it. A note is about the tools themselves: what worked, what was missing or confusing, what needed a workaround. It should not carry conversation data: the user's prompts, their credentials, or anything from their account. Feedback is at most |
| 27 | Awesome Toolsillyism · Marketing & SEO | illyism | Marketing & SEO | — | yes | Send feedback to the Awesome Tools team, optionally about a tool slug. |
| 28 | Ankra Docsankraio · Documents & Knowledge | ankraio | Documents & Knowledge | — | yes | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. |
| 29 | AHOOKahook-app · APIs & Integrations | ahook-app | APIs & Integrations | — | yes | File feedback for the AHOOK team as a support ticket: a feature request, a bug, something confusing, or anything else. A human reviews every filing; nothing is auto-built from it. Limited to 6 filings per day. Returns the ticket id and a public status URL. |
| 30 | AILANG Parsesunholo-data · Documents & Knowledge | sunholo-data | Documents & Knowledge | — | yes | Send a bug report, feature request, documentation gap or limitation about AILANG to the AILANG team. Use it only when the user asks to report something, and leave out personal or confidential information. Categories: bug, feature, docs, limitation. Body up to 10 KB, snippet up to 4 KB. `contact` is optional, for a reply. `package` (vendor/name) sends the report to that AILANG package's maintainers |
| 31 | Goldskygoldsky-io · Documents & Knowledge | goldsky-io | Documents & Knowledge | — | yes | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. |
| 32 | workspaceAlbertawarreandvavasour · Business & CRM | warreandvavasour | Business & CRM | — | yes | File a report when workspaceAlberta blocked the task: a bug, a missing capability, a confusing tool description, or a wrong result. Say what you were trying to do, which tool you used, what went wrong, and a proposed fix. A person reviews the report. This tool does not open a pull request, change the server, submit a bid, or contact a buyer. Do not use it for procurement search, tender questions, |
| 33 | Pressmarkmooshee · Documents & Knowledge | mooshee | Documents & Knowledge | — | yes | Send a bug report, feature request, or general feedback to the private Pressmark inbox when the user asks. Include only details they choose to share; omit documents, passwords, and tokens. |
| 34 | Atlyatlyai · Maps, Travel & Weather | atlyai | Maps, Travel & Weather | — | yes | Tell us how a call went Reference the `call_id` of any earlier response and say whether it helped, and optionally why, in a sentence about the result — what was right, missing or wrong. Do not include the user's words, the conversation, or anything about the person. Nothing is overwritten: sending again for the same call adds a new version and keeps the earlier ones (up to 50 per call). Lightly r |
| 35 | Norwegian Company Dataskaidigital · Business & CRM | skaidigital | Business & CRM | — | yes | Send private feedback to the Skai team about this product or MCP: ideas, missing functionality, errors, confusing behavior, praise, or anything else. Only message is required; category, toolName and context are optional. Report once per distinct observation and continue your task. Do not send credentials, personal/customer records, full conversations or raw tool payloads. Use generic placeholders. |
| 36 | Kourierkourierai · AI & Agents | kourierai | AI & Agents | — | yes | Send feedback or report a Kourier error, attributed to your account. Requires your Kourier API key in the MCP connection's Authorization: Bearer header, never in tool arguments. Submit only what the user wants to share; exclude API keys, tokens, passwords, personal data, and private code or logs. Include a request_id when available to help investigation. |
| 37 | Snapbackra1labsworkx-wq · Other | ra1labsworkx-wq | Other | — | yes | Tell Snapback whether a verdict was correct (correct=true/false), with an optional free-text note (did the fix work? what was wrong?). ONE rating per verdict — call it AFTER you act on a verdict and see the outcome. Your correction updates the SHARED pattern library (fix patterns are shared anonymized so every agent benefits; your trace content is never shared) — a right verdict comes back faster |
| 38 | NYCfoodietireniajilore · Food, Home & Lifestyle | tireniajilore | Food, Home & Lifestyle | — | yes | Record feedback on a tool result: a 1–5 rating, a comment, or both (at least one is required). Use after showing the user a recommendation to log what was good or wrong. Each call stores a new feedback entry; it changes nothing the user sees. |
| 39 | TheRundown Documentation MCPtherundown · Documents & Knowledge | therundown | Documents & Knowledge | — | yes | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. |
| 40 | ABS Data (observed)ai-colab · Data & Analytics | ai-colab | Data & Analytics | — | yes | Send feedback about this ABS connector (or a report about ABS's own data) to its maintainers. Only call this after the person has seen the exact text and said to send it — prefer feedback_form, which lets them edit it first. Use about='abs' for wrong figures or broken behaviour in ABS's own data or API; set shareWithAbs only if the person agreed it may be passed on to ABS. Never include personal i |
| 41 | DarkFunnels documentationdarkfunnels-ai · Documents & Knowledge | darkfunnels-ai | Documents & Knowledge | — | yes | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. |
| 42 | Cerebrium Docscerebriumai · Documents & Knowledge | cerebriumai | Documents & Knowledge | — | yes | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. |
| 43 | SiteGPT Docssitegpt · Documents & Knowledge | sitegpt | Documents & Knowledge | — | yes | Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant. |
| 44 | Crashtestyourstrategyfnobbe · Finance | fnobbe | Finance | — | yes | USE WHEN something in a response was wrong, unclear or missing and you want to tell the operator. Persists structured feedback on a previous response: your agent identity, the request_id, and items {category, severity, observation, suggested_action?, agent_confidence 0..1}. Aggregates are readable at feedback://insights. |
| 45 | Mercantry Registrymercantry · Food, Home & Lifestyle | mercantry | Food, Home & Lifestyle | — | yes | Report how a confirmed reservation actually went. Accepted only against a confirmed booking_id, once per booking, within 14 days of confirmation. Structured fields first; optional free text ≤ 500 chars. This corpus is served raw to all agents via get_merchant — it is never editorialized or turned into a score. |
| 46 | InsideOut (Riley)luthersystems · Cloud & DevOps | luthersystems | Cloud & DevOps | — | yes | FEEDBACK: Submit feedback, bug reports, or feature requests to Luther Systems Use this tool to forward user feedback directly to the Luther Systems team. This includes bug reports, feature requests, questions, or general feedback about InsideOut. The agent itself can also use this tool to report issues it encounters during operation. REQUIRES: session_id, category, message OPTIONAL: user_email (f |
| 47 | Narev LLM Pricingnarevai · AI & Agents | narevai | AI & Agents | — | yes | Send a documentation issue to the Narev docs team. Provide the page path and explain what is wrong or missing. Use this only when the user wants to report a documentation issue. For product support, direct the user to support. |
| 48 | ServiceBuddy Auto Repair Savings & Quote Auditorpiers-fawkes · Finance | piers-fawkes | Finance | — | yes | Report a gap or problem after attempting a task for the driver — for example, when get_evaluated_savings does not yet support a requested repair category or metro, when no active coupon was matched for a major chain, or when audit_repair_quote encountered an unparseable estimate. If the driver has a written quote, estimate, or line-item price for a repair category not listed in get_evaluated_savin |
| 49 | Pet Data Stationlongjourneycai · Food, Home & Lifestyle | longjourneycai | Food, Home & Lifestyle | — | yes | Leave feedback for the station's human maintainers (2026-08-16). type: 'data_request' (data you could not find — the most valuable signal), 'error_report' (a claim that mismatches its cited source; include topic_id), 'knowledge_lead' (a fact worth adding; source_url REQUIRED — first-hand sources only: statutes, government datasets, peer-reviewed papers). One-way mailbox: stored for human review, |
| 50 | CarScoutbrunoamorim39 · E-commerce & Retail | brunoamorim39 | E-commerce & Retail | — | yes | Send a bug report, feature request, or feedback to the CarScout team. This saves the report and can send an email notification to CarScout support that cannot be recalled. |
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.