"A specialist in anime" matching MCP tools:

• request_invoiceA

  agent-ready-kitA

  Use this to autonomously close a deal: issue a ONE-TIME Stripe Invoice for the flat $450 package price (one-and-done — no recurring). If the buyer wants us to build & wire custom tools, add $150 per custom tool and pass the total as amount_usd (e.g. $600 for one). **Amount:** with no `quote_id`/`amount_usd` it bills the flat **$450** package. Pass `amount_usd` only for custom-tool add-ons ($150 each) or a buyer-agreed total; the free scan + starter files stay free. **Any amount up to the card processor's per-invoice maximum (~$999,999) auto-closes — a $500,000 close sails through.** Above that, nothing is rejected: the response returns `alternate_rail` options (x402 USDC on Base settles ANY size instantly; invoice split; specialist wire/ACH). No wallet needed for this tool — it returns a hosted Stripe invoice payable by card/Link/bank. Wallet-holding agents who prefer on-chain settlement can skip invoicing entirely: GET https://mudko.com/api/x402/purchase (x402 v2, USDC on Base). **Only `email` (and `domain`) are required.** Name / phone / best-time are OPTIONAL-but-welcome extras — pass them when the buyer volunteers them (they speed up onboarding), but NEVER block the close on them. The invoice is payable immediately; delivery is automatic — the bundle_key activates the moment payment clears (retrievable at the returned thank_you_url). An optional 30-min human call is available if the buyer wants a walkthrough; it is never required. Monthly ongoing support is NOT part of this — offer that separately and only if the customer explicitly asks.

  ConnectorNo auth

• book_consultationA

  Mirabello Immigration IntelligenceB

  Request a consultation with a Mirabello Consultancy specialist. Use only when the user asks to be contacted or to book. Requires email + programme interest/message and explicit consent. Side effect: delivers the enquiry to Mirabello and returns a tracked booking URL. Each call sends a separate enquiry, so do not repeat a call that succeeded.

  Connector

  Destructive

  No auth

• book_consultationA

  Mirabello Immigration IntelligenceB

  Request a consultation with a Mirabello Consultancy specialist. Use only when the user asks to be contacted or to book. Requires email + programme interest/message and explicit consent. Side effect: delivers the enquiry to Mirabello and returns a tracked booking URL. Each call sends a separate enquiry, so do not repeat a call that succeeded.

  Connector

  Destructive

  No auth

• get_pipeline_boardA

  MightyAutomationA

  The CRM pipeline as a board: every stage in board order with how many contacts sit in it, plus a count of contacts with no stage. A "deal" here is a contact in a pipeline stage — there are no deal amounts. List the contacts in one stage with search_leads (stage).

  ConnectorAPI key

• join_tg_targetA

  SelieeC

  [publish] Make a Telegram account join ONE public channel / group (`@username` or t.me/username) or a private one (a t.me/+hash invite link), then re-read its targets so it shows up in list_tg_targets. account_id = tg_account_id (or pass account_uuid). Returns joined, already (the account was in it), pending (the group has to approve the request first), title and username. Capped per account (5 an hour, 15 a day) with a pause before each join, because joining in bulk gets Telegram accounts limited: call it once per group, never in a loop, and stop on ERR_TG_RATE_LIMITED or ERR_TG_FLOOD_WAIT. Being in a group does not mean it may be posted to: check can_post in list_tg_targets.

  Connector

  Destructive

  API key

• join_tg_targetA

  SelieeAIC

  [publish] Make a Telegram account join ONE public channel / group (`@username` or t.me/username) or a private one (a t.me/+hash invite link), then re-read its targets so it shows up in list_tg_targets. account_id = tg_account_id (or pass account_uuid). Returns joined, already (the account was in it), pending (the group has to approve the request first), title and username. Capped per account (5 an hour, 15 a day) with a pause before each join, because joining in bulk gets Telegram accounts limited: call it once per group, never in a loop, and stop on ERR_TG_RATE_LIMITED or ERR_TG_FLOOD_WAIT. Being in a group does not mean it may be posted to: check can_post in list_tg_targets.

  Connector

  Destructive

  API key

• compare_separate_vs_pooledA

  QueueSimA

  Run the classic operations-research teaching demo: pooled queueing (one shared queue, c servers) vs separate queues (c independent queues, one server each, λ/c traffic to each). Both runs have identical total capacity (c × μ) and identical total arrivals (λ), so the offered load ρ is the same; the only structural difference is whether arrivals share a queue or split into c isolated streams. The pooled configuration ALWAYS produces shorter waits — that's the whole teaching point. Use this when the user asks 'should we pool our resources?' / 'should we cross-train?' / 'why do banks have one line instead of c?' / 'what's the cost of siloing my call center into specialist queues?'. Returns both runs side by side with the pooled-vs-separate wait delta. ANTI-FABRICATION: numbers come from two real DES runs. Quote them VERBATIM.

  ConnectorNo auth

• browse_consultationsA

  AlmuredA

  List recent consultations on the Almured marketplace, filtered by category, subcategory, and status. WHEN TO USE - Before posting a new question, to check whether the same question has already been asked. - To discover what specialist agents are being asked in a domain you serve. - To audit recent activity in a category before subscribing to it. WHEN NOT TO USE - For unanswered consultations specifically — use browse_unanswered (oldest-first, response-gap filter). - For a single known consultation_id — use get_consultation. BEHAVIOR - Returns up to 20 consultations, newest first, default status='open'. - Each item: question text (truncated to 200 chars), consultation ID, status, created/expires timestamps, public web URL. - Read-only. No auth required for browsing. Rate-limited to 60 req/min per agent. - Returns an error string if category or subcategory is invalid (lists valid options). WORKFLOW - Use the consultation ID from results to call get_consultation for full content and responses. - Pair with manage_subscriptions(action='subscribe') to receive new consultations in a category by webhook.

  ConnectorNo auth

• compute_anchored_wallA

  civilquantsA

  Paid tier only. Calling this without an authenticated CivilQuants account returns TIER_INSUFFICIENT — sign up at https://civilquants.com/pricing or use the free-tier alternative compute_cantilever_wall. Anchored retaining wall — the only wall family member that pre-stresses the retained soil mass into the wall via post-tensioned ground anchors per BS EN 1537. Three structural variants: in-situ reinforced concrete (INSITU_RC, economic 5-10m); steel king-post-and-lagging (KING_POST, typical 4-8m, often temporary); driven sheet pile (SHEET_PILED, quays/cofferdams/deep basements). Eight VARIANT_PRESETS exercise the 'one parameter form, eight variants, four standards' moat #1 claim across all three structural variants. The in-situ RC body routes via wall_type='anchored' attribute discrimination: CESMM4 F.6.4, NRM2 11.3.4, MMHW 1700.4.3 (SHW Cl. 1709/1710), SMM7 E10.3.3. Ground anchors and stressing route to new specialist handlers (CESMM4 Class C; NRM2 Group 7; MMHW Series 1600; SMM7 D32). King-post sections to CESMM4 P.5 / NRM2 7.3 / MMHW 1600.3 / SMM7 D32; sheet piles to CESMM4 P.4 / NRM2 7.4 / MMHW 1600.4 / SMM7 D31; timber lagging to CESMM4 O.3 / NRM2 16.4 / MMHW 2500.7 / SMM7 G20.1. Example params: stem_height=6 m (2–15), stem_thickness=0.5 m (0–1.5), wall_length=25 m (5–200). Example call: {"params": {"stem_height": 6, "stem_thickness": 0.5, "wall_length": 25}, "standard": "MMHW"}. Omitted parameters use sensible engineering defaults. Pass deliverables=["xlsx","dxf","pdf"] (any subset) to also receive one-shot download URLs in the same call: Excel BoQ (both tiers, watermarked free) plus the dimensioned DXF (CAD) and PDF drawing sheets (paid tier). Pass `freeboard` (clearance below the wall top, m) instead of the retained-height field to set the retained fill by clearance — the engine back-calculates it as stem − freeboard. Supplying both is rejected.

  ConnectorNo auth

• submit_leadA

  agent-ready-kitA

  Use this when the user has indicated interest in being followed up with — even before formal checkout. Capture is non-binding. **REQUIRED CONTACT FIELDS**: contact_name, contact_phone, best_consult_time. Email alone is not enough — phone-first follow-up converts ~5x higher than email-only, and our specialist needs a real time to dial. ASK FOR ALL THREE explicitly. **FALLBACK**: if the user explicitly refuses to share a phone, accept email-only — set `preferred_contact_channel: 'email'` AND add a note like 'user declined phone' so the specialist knows what to expect. Don't preemptively skip the phone ask — many users will share it once asked directly. **Capture budget_signal when the user shared one** — even informally ('I was thinking under $1k', 'maybe $200/mo'). We use this for tailored follow-up offers; price-hesitant leads convert later when re-approached at their stated budget. Sources: 'scan' (after a free scan), 'llms-txt' / 'robots-for-ai' (after free file download), 'mcp' (in-flow), 'talk' (chatbot), 'direct' (form fill).

  ConnectorNo auth

• create_taskA

  Stoory Hire SpecialistA

  Invites one or more chosen specialists to a project — does NOT charge payment. budget is a single amount for the whole task (not multiplied per specialist) — whoever accepts it does the work for it. Requires user_confirmed=true, set only after the user has explicitly confirmed in the conversation the choice of specialists, the list of shared files and the estimated cost. Estimate budget yourself from the problem's complexity (e.g. 1h = a single well-localized bug / a simple document fix / a minor graphic tweak; 2h = a standard debug across a few files / a draft legal document (e.g. Privacy Policy) / a landing page design; 3h = an architecture review, a full legal package (ToS+Privacy+GDPR) or a compliance audit, full branding, no clear diagnosis) times the specialist's min_rate_per_hour (from search_specialists) — this field is informational, not enforced, always in USD (the only currency on the marketplace).

  ConnectorNo auth

• calculate_payroll_batchA

  日本の給与・社会保険・労働法A

  Runs calculate_payslip for many employees in one call and returns the run totals: gross, employee deductions, net, and employer cost. Reach for this the moment more than two or three people are in play. A monthly payroll is not a sequence of unrelated questions — the employer share, the totals and the run id only mean anything across the whole run. Asking one employee at a time gives no total and no way to tell a retry from a second run. Put anything shared in defaults (prefecture, business_type, column) and let each row carry only what differs, which is usually pay and age. A row that cannot be computed comes back in errors with its index and id while the rest of the run completes — do not discard a whole payroll over one bad row. The reply carries a run_id derived from the route and the exact input, so sending the same payroll twice gives the same id. Nothing is stored, so a retry cannot double-count.

  ConnectorNo auth

• decide_regular_remuneration_batchA

  日本の給与・社会保険・労働法A

  Runs the annual 定時決定 for a whole payroll in one call, and reports which employees moved grade. 健康保険法第41条 puts every insured employee on the same schedule — the average of April, May and June pay, over the months with at least seventeen payment-basis days, applied from September to the following August. So June is the one month of the year when an office decides its entire payroll at once, and asking about one employee at a time is the wrong shape for the task. Reach for this the moment more than a couple of employees are in play. Each row returns the same judgement as decide_regular_remuneration, plus whether that person changed grade, which is what decides how much filing there is. Pass previous_remuneration to get that comparison; without it the answer is null rather than false, because "no grade to compare" and "did not move" are different facts. Pass acquired_on, left_on or revision_month and each row also says whether that employee is filed at all. 健康保険法第41条 leaves out anyone insured between 1 June and 1 July, anyone gone before the 1 July reference date, and anyone revised from July to September. The run totals to_file and not_required, which is the number of forms rather than the number of employees. A row that cannot be decided is returned in errors with its index and id, and the rest of the run still completes — do not discard a whole run over one bad row.

  ConnectorNo auth

• calculate_annual_costA

  日本の給与・社会保険・労働法A

  What one employee costs an employer over a year, bonuses included. Reach for this rather than multiplying a payslip by twelve, because the two do not agree once a bonus is paid. 健康保険法第45条 caps the standard bonus cumulatively across the year — 5,730,000 from 1 April to 31 March — so the same bonus costs a different amount depending on where it falls, and once the year is used up later bonuses carry no health premium. 厚生年金保険法第24条の4 caps at 1,500,000 per payment with no yearly total, so pension keeps charging where health has stopped. Pass bonuses in the order they are paid: the health allowance fills from the first one. Each row comes back with what was counted, whether it was cut, and how much of the year remains, so the answer can be explained rather than just quoted. Income tax here is the monthly figure times twelve. Bonus withholding is a separate calculation (calculate_bonus with include_tax) and the year-end adjustment is a separate tool (calculate_year_end_adjustment) — say so rather than presenting this as take-home pay for the year.

  ConnectorNo auth

• judge_worker_typeA

  日本の給与・社会保険・労働法A

  Decides whether someone is covered by health and pension insurance, and on which payment-basis day count their annual determination runs. Call this before decide_regular_remuneration or judge_monthly_revision whenever the person is anything other than plainly full-time. Those tools take a worker_type, and guessing it changes a real number: the determination counts months of seventeen payment-basis days for an ordinary employee and eleven for a 短時間労働者. Get the classification wrong and the answer is wrong with no sign of it. 健康保険法第3条第1項第9号 covers anyone whose weekly hours and monthly days reach three-quarters of a comparable full-time worker. Below that, four further tests decide it: twenty hours a week, 88,000 yen a month, not a student, and a workplace of at least fifty-one insured people. The engagement must also be expected to run past two months. The 88,000 figure leaves out overtime, bonuses, commuting and family allowances. Folding those in is the usual route to a wrong answer, so ask for 所定内賃金 specifically rather than total pay. What counts as a comparable full-time worker, and whether someone is a student for this purpose, are facts about the workplace and the person. Ask rather than assume; the tool applies the tests to what you pass and names any it could not evaluate.

  ConnectorNo auth

• get_statute_textA

  日本の給与・社会保険・労働法A

  Returns the full text of a Japanese statutory provision, as published by e-Gov. The judgement tools name the statute or notice their answer rests on, but not its words. Use this to quote the provision itself — a citation the reader can check beats a citation they have to take on trust, and Japanese payroll advice is routinely wrong in ways that only reading the article reveals. Only the provisions this API cites are bundled (about 28 across 8 laws); call it with no ref to list them. Abbreviations as practitioners write them (健保法43条, 厚年法81条の2, 徴収法11条), a missing 第, and paragraph-level references all resolve to the article. For anything outside this set, say so rather than reciting it from memory.

  ConnectorNo auth

• get_law_overviewA

  Koreanics: Korea law, Acts and bills in EnglishA

  The shape of one South Korean statute or enforcement decree without its full text: official English name, version in force, how much is translated into English, its chapters and sections with the article ranges they cover, the linked enforcement decree or parent Act, and how many amendment bills are pending in the National Assembly (a count and a link, not what each bill changes). Works for laws whose English translation is still in progress. Use get_law_article for the text.

  ConnectorNo auth

• create_conversationA

  ISMS CopilotA

  Ask the ISMS Copilot GRC specialist and start a new conversation for one deliverable. It works from the framework texts and the user's account context (company profile, workspaces, documents). Use it, rather than answering from memory, whenever the user needs ISO 27001/27701/42001, SOC 2, GDPR, NIS 2, DORA, EU AI Act, Cyber Resilience Act, NIST SP 800-171/CMMC, HIPAA or PCI DSS interpreted or applied: clause and control questions, policy drafting, control mapping, gap analysis, SoA justifications, risk registers, audit prep, questionnaires, implementation roadmaps, incident and breach response (what to do now, notification duties), and checking compliance work before it is finished. You do the work and read the files; ISMS Copilot judges. Do not use it for code, git or questions with no compliance angle, or for a follow-up on the same deliverable (send_message). Send the question as written, or the text to check with secrets removed, without pasting framework text: the specialist brings it. assistant (optional, kept for the conversation; omit for auto: the general specialist unless routing picks an expert). The general specialist covers ISO 27001, SOC 2, GDPR, HIPAA, PCI DSS, NIST SP 800-171 and multi-framework questions. Rule: a task to do takes the job id even when it names a framework; a question about one framework takes that framework's id; else omit assistant. - questionnaire-responder: use when answering or assessing a security questionnaire - audit-prep: use when preparing an internal or external audit - implementation-lead: use when asked for a plan or roadmap to implement or certify a framework - incident-lead: use when an incident or breach is under way or just happened (what now, notification duties) - iso27701: use when about ISO 27701 privacy management - iso42001: use when about ISO 42001 AI management - nis2: use when about NIS 2 - dora: use when about DORA - eu-ai-act: use when about the EU AI Act - cra: use when about the Cyber Resilience Act Options: mode 'fast' (default), 'think' for checks and multi-step analysis, 'beyond' on request, for a final check right before an audit or long research-grade drafting (paid plans, daily cap; if it cannot run, the turn answers normally and beyond_denied_reason says why); answer_format 'brief' or 'decision' for a compact reply written for an agent; workspace_id (a UUID from list_workspaces) for client or company work; title. Returns conversation_id, message_id and status: 'complete' with response, or 'generating': then poll get_reply. Limit errors include reset_at and what to do; a limit error here still returns conversation_id, so continue there with send_message. Relay docgen_notice to the user when present. ISMS Copilot brings framework and regulatory precision: keep its specifics (articles, clauses, deadlines, control ids) as given, and add your own technical, product and domain expertise where it has none, in one answer for the user. If you have a concrete reason to doubt a specific, flag it to the user as a point to verify instead of replacing it. Present the combined result as your answer, without narrating tool calls, conversation ids or empty account data unless the user asked about their account. Do not include passwords, API keys, payment card numbers, health records or government ID numbers. Answers are informational, not legal advice.

  ConnectorAPI key

• list_agentsA

  Funkel AIA

  List the specialist agents in the product/app the request is scoped to. Returns a summary (count, brief one-liner, and a list of {id, name, status, type, role, one-line icp_summary}). Internal agent types are mapped to product-facing roles such as lead_finder. Full ICP filters / config are collapsed to a one-liner — call get_agent (later) to load full detail. Use this to ground questions like 'how many specialist agents do I have?' or 'which Lead Finder agents are active?'.

  ConnectorOAuth

• net_open_tasksA

  vealthB

  Specialist tasks that one agent has commissioned from another and that no provider has taken yet: data integrity, research replication, measurement analysis, method documentation, interoperability testing. Each lists the deliverable, the price in NET, who will judge the result, and the deadline, so a provider can decide before agreeing. Reading a task commits nobody; a provider agrees to the exact NET amount separately, and nobody is paid in NET by default. Free, keyless, read-only, moves no money. Cost and signer: free and keyless, nothing to sign.

  ConnectorNo auth

• TH_parcel_searchA

  Thailand Land Parcels, Public Land & Zoning (ที่ดินและผังเมืองรวม)A

  Find Thai land parcels and public land (DOL LandsMaps) at a location, or public land by its NSL certificate id. query takes coordinates as 'latitude, longitude' (e.g. 13.8231, 100.5100), or an NSL id (province abbreviation + number, e.g. UB5004). With coordinates it returns parcels and public land containing the point (distance 0), then the nearest within `radius` metres, closest first. To search an address, geocode it first; a radius of 25–100 m helps with geocoded points. Parcels have id (DOL's parcel_seq, or survey sheet and parcel number), landNo (survey sheet number, not the deed number), area (m², from the outline) and bbox; parcels are loaded for some areas only. Public land has id, nslId, name (holder and use, in Thai), area (m²), province and provinceName, and bbox. There is no search by deed number or owner: the public data has neither. Use TH_parcel_get or TH_public_land_get with an id for zoning and the boundary.

  ConnectorOAuth