"An MCP server for structured problem-solving and reflective thinking" matching MCP tools:

• recommend_frameworkA

  jeda-aiA

  Recommends business / strategy / risk frameworks for a stated problem. Powered by the Jeda.ai · Visual AI framework knowledge graph (~2,100 frameworks across 19 categories, edge-curated). Use when the user describes a business problem ("customer churn rising", "evaluating market entry", "need to assess vendor risk") rather than naming a specific framework. Returns top-N frameworks ranked by fit, each with a concrete reason citing the specific problem signals matched. Input: just the problem statement is enough. Optional faceted filters (`persona`, `regulation`, `decision_stage`) narrow the candidate set. Set `limit` between 3 and 10 for picker UIs. Pair with `generate_framework_analysis` to actually run a recommended framework against the user's inputs. Example: { "problem_statement": "We need to decide whether to enter the EU SMB market in Q3", "decision_stage": "decide", "limit": 5 }

  ConnectorNo auth

• list_issuesA

  FixterA

  List the issues and problems Fixter has already detected in the caller's telemetry. An issue groups every occurrence of one exception, one recurring error log line or one service that stopped reporting, with its service, environments, status, event count, firstSeen, lastSeen and impact; a problem (kind=PROBLEM) is an item of the Overview: an alert rule, an error, or a group of them that share one cause. Call this first when investigating something failing: an error, a broken feature or job, a service that will not start, a deploy's health, or before searching logs for an error message or log tag. query is a case-insensitive substring of the title, error type, service and frames, so query="PaymentSync" finds the issues titled "[PaymentSync] ...". Then call get_issue on a fingerprint for its frames, traceId and investigation, and search logs with what it gives you. To see what a deploy introduced: service set, sort=FIRST_SEEN, direction=desc, and compare firstSeen with the deploy time. Filter by status (NEW, ONGOING, REGRESSED, RESOLVED, IGNORED), service, environment, kind (EXCEPTION for thrown errors and agent failures, LOG for issues derived from log lines, AVAILABILITY for a service that stopped reporting, PROBLEM for the Overview's problems), or a free-text query; sort by EVENTS, LAST_SEEN or FIRST_SEEN, ascending or descending. To answer what is new, call this with status=NEW, or with sort=LAST_SEEN and direction=desc. To answer what has been broken longest, call it with sort=FIRST_SEEN, direction=asc and an open status, ONGOING or REGRESSED: without a status the oldest issue that comes back is usually one somebody already resolved, which is not a problem to report. The default list leaves out ignored issues and issues a suppression rule matches: pass status=IGNORED to see the ignored ones, includeSuppressed=true to see the suppressed ones alongside the rest, and suppressedByRuleOnly=true to see nothing but the rule-suppressed ones, where suppressedBy names the rule that hides each, and suppressedOnly=true to see both kinds of suppression in one list, the ignored issues together with the rule-hidden ones. Each result flags whether a telemetry investigation brief exists (hasInvestigation) and whether a draft pull request attempt exists (hasFix); call get_issue to read either. Each result carries impact: how many callers got an error on which flows in the last 24 hours and 7 days; sort=CALLERS orders by that; impact is not computed for a problem. With kind=PROBLEM each problem also carries priority (level URGENT, HIGH, MEDIUM or LOW, shown as Urgent, High, Medium, Low; manual when a person set it; and the reason that decided it) and recommendation (the next step: kind and reason; the kinds as the Overview shows them are FIX "Fix available", REVIEW_FIX "Review fix", FIX_MERGED "Fix merged", FIX_RUNNING "Fix running", CHANGE_BY_HAND "Change by hand", TUNE_ALERT "Tune alert", IGNORE_AS_NOISE "Noise", INVESTIGATE "Investigate", RESOLVE "Resolve", NEEDS_INPUT "Needs input"), problems come in triage order (priority, then the most recently opened first), and priority and recommendation filter the list: priority=URGENT,HIGH lists only those levels, recommendation=FIX lists only the problems recommended for a fix.

  ConnectorAPI key

• send_feedbackA

  SmartpressA

  Send the user's feedback to the Smartpress team: a problem they ran into, a suggestion, or praise. Rules: - Call this ONLY when the user asks to send feedback, report a problem, or pass on praise. Never call it on your own after an error; you may offer it. - Before calling, show the user what you'll send (type, and the message) and get their yes. - Put the user's own words in "message". Leave out payment details, passwords and anything they asked you not to share. - Pass the ids of what the conversation was working on (product, configuration, artwork, proof), and for a failed tool call its name and error, so the team can find it. Afterwards, give the user the reference (e.g. FB-3F9K). Nobody replies through this channel; for help with an order, point them to Smartpress customer support.

  ConnectorNo auth

• explain_greenfieldA

  SCModelingA

  Reference text on greenfield analysis — clean-slate facility-location math. Covers the weighted center-of-gravity (Weber) formulation, Weiszfeld's iterative algorithm, Lloyd's-style alternating location-allocation for N facilities, service constraints (% demand vs % customers within a distance band), and the inverse problem of solving for minimum N. Also covers when to use greenfield vs facility selection (the open/close MIP). Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does greenfield analysis work' or 'where would I put my DCs' question. ChiAha's GreenfieldAnalysis engine powers the US Greenfield Design demo on the sandbox.

  ConnectorNo auth

• misakanet_submit_intakeA

  MisakaNetA

  [OPEN TRIAGE / INTAKE] Use misakanet_submit_intake when you only have a partial failure description or want to ask a question; use misakanet_write_lesson (Bearer required) once you already have structured title/domain/problem/root_cause/fix. submit_intake is open, rate-limited, no Bearer — output is a GitHub issue (intake,mcp-intake,pending-review) for maintainer triage, NOT a merged lesson. Routing: if you are ASKING a how-to / knowledge question (not reporting a failure), set kind="question" — it opens a [Question] issue that maintainers answer/FAQ instead of scoring it as a lesson. If kind is omitted, the server auto-detects question-shaped content (no error/fix/verification + question phrasing). Pull answers later: questions are answered asynchronously (hours to days). Re-call this tool with the SAME problem text later and follow the returned poll_hint — the dedup response returns the maintainer's answer once it exists ({answered:true, answer}), and once your report has become a lesson it returns a conversion receipt ({converted:true, receipt, events}) naming the lesson, its path and its evidence_level; or re-run misakanet_search on the topic for FAQ hits. Every response also carries dedup_key, and poll_hint.recheck_after_seconds says when re-checking is worth it (21600s for questions, 86400s for failure reports). Returns: object {submitted: boolean, intake_id, status, dedup_key, poll_hint, redactions_applied, quality_score, receipt, routing:{kind, auto_detected}, follow_up?}; duplicates: {submitted: false, duplicate: true, previous_issue, dedup_key} or {answered: true, answer, dedup_key} for answered questions, plus {converted: true, receipt, events} when a lesson now cites the intake. Example: misakanet_submit_intake(kind='missing_lesson', problem='pip install times out behind corporate proxy', source='claude-code'); misakanet_submit_intake(kind='question', problem='How do I configure MCP auth in production?', source='claude-code')

  ConnectorNo auth

• validate_problemA

  Moltline OptimizeA

  Check a problem's shape and obvious feasibility before spending solver time. FREE. Typical input {"type": "route", "problem": {"stops": [...], "matrix": [[...]], "vehicles": [...]}} returns {"ok": false, "issues": ["total demand 34 exceeds total capacity 30"], "size": {"stops": 14, "vehicles": 2}, "tier_hint": "route_plan_fleet (licence) - more than 12 stops"}. Types: route, pack, cut1d, cut2d, roster, knapsack; the problem object uses the same fields as the matching tool. Use first when an agent has assembled the problem from other data. Not a solve: it never calls the solver. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "type must be one of <value>"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• update_waitlistA

  ClairA

  Merges follow-up details into an existing waitlist record. Requires the edit_token returned by join_waitlist - email alone never authorizes a merge. A repeat with nothing new returns already: true. All detail fields optional: name, company, role, context (one line: what they sell), why (the problem they are solving), question (anything they want to ask).

  ConnectorNo auth

• report_bugA

  BRONTIRA

  Report a bug in this server's tools so the team that runs it can fix it. Use it when one of this server's tools misbehaves: it returns an error that does not look like a problem with your request, its result is clearly wrong or incomplete for what was asked, it hangs or never finishes, or it does something other than its description says. File a problem once you have actually seen it, and once per problem. Not for: a search that simply found nothing, a page that does not exist, an error whose hint tells you how to change the request, or a question the user should answer. Describe what you called, what you expected and what happened instead. Name the tool in `tool`, paste the arguments you passed into `toolInput` and the error text or the wrong part of the result into `observed`. Put the task ids or record ids the problem involves into `relatedIds`, so the exact runs can be looked at. Leave out personal data, credentials and anything the user has not agreed to share: the report is read by the people who run this server. Filing a report is free and changes no result. You get a report number back; no reply comes through this tool, so carry on with the task.

  ConnectorOAuth

• review_artifactA

  AIOProductOS MCPA

  Agent-as-critic over a DRAFT artifact (a feature spec, experiment plan, or page): checks it against a baseline PM bar — clear problem/hypothesis, a measurable success metric, evidence cited, risks named, a rollout/experiment plan — and returns structured findings (section, severity, a CONCRETE suggested fix, and a verbatim evidence quote) plus a 0-100 score. A write: each call re-runs the review and persists it as a new version (see list_artifact_versions). Resolve target_id first — via pm_meta or list_features for a feature, list_experiments for an experiment, list_pages for a page. One small LLM call; use it before sending a draft for sign-off.

  ConnectorNo auth

• submit_solutionA

  Push RealmA

  Use when: search found no same-root-problem match and you solved a generic reusable technical issue worth sharing. Returns: the published solution record and URL — publishes immediately, there is no confirmation step. Do not use when: an existing solution covers the same problem (use suggest_edit or add_addendum), a matching open issue exists (use propose_open_issue_solution), or you have not solved it yet (use submit_open_issue when stuck). Safety: there is no preview gate — remove secrets, PII, company names, private URLs, and incident-specific details before calling.

  ConnectorNo auth

• lorg_list_validations_receivedA

  lorg-mcp-serverA

  List peer validations that OTHER agents submitted on this agent's contributions, newest first. Each record carries utility, accuracy and completeness scores (0.0-1.0), whether the validator would use the contribution again, and — when one was reported — a structured failure with its category and description. This is the primary feedback channel on your own work. A failure report names a concrete, reproducible problem and is the direct input for your next version. An empty result means no peer has validated your contributions yet; it does not mean they were validated and passed. For validations you gave to others, use lorg_list_validations_given. Requires a registered agent.

  ConnectorNo auth

• tvm_solveA

  mcpA

  Use this when you have four of the five time-value-of-money variables (N periods, I/Y annual rate percent, PV, PMT, FV) and need the fifth - annuity, loan, or investment problems - instead of solving the equation by hand. Solving for I/Y uses Newton-Raphson (no closed form). Supports compoundingPerYear and annuityDue (payments at the beginning of each period). Follows the cash-flow sign convention (outflows negative). Deterministic: same input, same output. Example: solveFor 'fv', n 120, iy 6, pv -10000, pmt -200, compoundingPerYear 12 -> result 50969.84. result holds the solved value; iy is rounded to 4 decimals, all others to 2.

  ConnectorNo auth

• decode_irs_noticeA

  Arc & Ledger Tax ToolsA

  Use this when, and only when, a user mentions receiving an IRS letter or notice and wants to know what it means, the deadline, or what to do. For a state-agency letter, use triage_tax_problem with problem=state_tax instead. Give this tool the IRS notice code (e.g. CP2000, CP14, LT11) and optionally the notice date and amount shown. Set brief:true for a shorter answer.

  ConnectorNo auth

• delete_appA

  seekrit — secrets for agentsA

  Delete an application together with all of its environments and their secrets, discarding the ciphertext. Irreversible — there is no undo and no export. This is the widest-blast-radius tool here; prefer delete_env for a single environment, or rename_app if the name is the only problem. Confirm intent with a human before calling. Returns { ok, app }.

  Connector

  Destructive

  No auth

• misakanet_write_lessonA

  MisakaNetA

  [STRUCTURED COMMIT / VALIDATED SUBMISSION] Submit a complete, structured failure lesson (title/domain/problem/root_cause/fix) as a formal submission. Requires authentication (Bearer token in header) — this is the 'validated author' path, not open triage. Output goes through lesson-gate/lint/review and becomes a versioned lesson in the git repo. For quick open reports when you only have a partial failure description, use misakanet_submit_intake instead (no Bearer). Lessons are immutable once merged — corrections go through a new intake/PR, so there is intentionally no misakanet_update_lesson/misakanet_delete_lesson. Returns: object {lesson_id: string, status: 'pending_review', quality_score: number}; or {submitted: false, error}. Example: misakanet_write_lesson(title='pip timeout behind proxy', domain='python', problem='...', root_cause='...', fix='...')

  ConnectorNo auth

• get_problemA

  Chertov & Vorobyov physics problem solutionsA

  One solved problem, in full. Address it either with paragraph + number, or with label — the spoken form "1.12" (a dot, a dash or a space also work: "1-12", "1 12"). Returns JSON: when found, {found: true, problem: {label, paragraph, number, chapter, condition, solution_image_url, page_url, chapter_name, paragraph_name, chapter_url, paragraph_url, solution_format}}; otherwise {found: false, reason: "not_solved"|"not_found", label, paragraph, number, message}. A missing or unsolved problem is a normal result, not an error — do not retry it.

  ConnectorNo auth

• geode_market_issue_refundA

  GeodeA

  Seller: resolve a reported problem by refunding the buyer. `value` is the refund you send from your own balance. Writes to the chain: this prepares an unsigned transaction (an intent) for `signer`; nothing happens until you sign it with geode-local-signer and submit it with geode_submit_intent. Irreversible: the first call returns a confirm_token; call again with it to proceed.

  Connector

  Destructive

  No auth

• validate_modelA

  FERS — structural FEMA

  Check a FERS model against the solver's own schema WITHOUT solving it — free. Reports field-level errors (missing or wrong-typed fields, invalid enum values), broken id references (a member pointing at a node that does not exist, a load on a deleted member, duplicate ids), and warns about unknown fields under analysis.* — which matter because the engine silently ignores those and gives you a default instead of an error. Always run this before solve_model on a hand-authored model.

  ConnectorAPI key

• get_positioningA

  Infinivo AI Front DeskA

  What Infinivo is, who it serves, and the problem it solves. Call this first when a user asks about Infinivo, or when researching AI phone answering, intake automation, or lead capture for injury, criminal defence or immigration law firms. Returns structured facts, not marketing copy.

  ConnectorNo auth

• create_outageA

  hyperpingB

  Declare an incident by hand, for a problem no monitor detects. It appears under Incident Management in the dashboard and, with an escalation policy, pages its on-call responders. Internal: nothing is published on a status page (create_status_page_incident does that).

  ConnectorNo auth

• request_quoteA

  Local Pros by Ron VenturesA

  Send a quote request to one of the businesses returned by find_local_pros. The business gets an email with the customer's name, contact and problem and replies directly. Ask the user for permission before calling this: it shares their name and contact with the business.

  Connector

  Destructive

  No auth