"A server for finding information on writing or researching a thesis" matching MCP tools:

• content_discoveryA

  gapup-mcpC

  Discover content franchises within a domain. Two modes: pass `tag` for a precise taxonomy match (every game tagged 'co-op'), or pass `query` for free-text SEMANTIC search powered by pgvector embeddings — finding franchises by meaning ('dark atmospheric games about isolation') even when no literal tag matches. Results are verifiable: tag mode carries tag confidence/corroboration, semantic mode carries a similarity score; both carry entity freshness. When to use: an agent wants a domain-scoped shortlist by tag or by intent. Inputs: a domain plus either a tag or a free-text query.

  ConnectorNo auth

• content_discoveryA

  mcp-knowledgeC

  Discover content franchises within a domain. Two modes: pass `tag` for a precise taxonomy match (every game tagged 'co-op'), or pass `query` for free-text SEMANTIC search powered by pgvector embeddings — finding franchises by meaning ('dark atmospheric games about isolation') even when no literal tag matches. Results are verifiable: tag mode carries tag confidence/corroboration, semantic mode carries a similarity score; both carry entity freshness. When to use: an agent wants a domain-scoped shortlist by tag or by intent. Inputs: a domain plus either a tag or a free-text query.

  ConnectorNo auth

• content_discoveryA

  gapup-mcpC

  Discover content franchises within a domain. Two modes: pass `tag` for a precise taxonomy match (every game tagged 'co-op'), or pass `query` for free-text SEMANTIC search powered by pgvector embeddings — finding franchises by meaning ('dark atmospheric games about isolation') even when no literal tag matches. Results are verifiable: tag mode carries tag confidence/corroboration, semantic mode carries a similarity score; both carry entity freshness. When to use: an agent wants a domain-scoped shortlist by tag or by intent. Inputs: a domain plus either a tag or a free-text query.

  ConnectorNo auth

• list_investment_thesesA

  crashtestyourstrategyA

  Discover the investment-thesis catalog. Each entry is a descriptive case study that pairs an economic framework with a rule-based portfolio and the synthetic + historical stress evidence for that allocation. Returns one compact summary per thesis (slug, title, one-liner, tags, risk tiers, framework summary, headline finding). Call get_investment_thesis(slug) for the full framework / portfolio / stress evidence, or read the thesis://{slug} resource. Descriptive, not advisory — the agent decides what is suitable.

  ConnectorNo auth

• lookup_provider_taxonomyA

  mcpB

  Look up a NUCC provider taxonomy code (the specialty codes used on HIPAA transactions + NPI registrations) or search by keyword. Returns classification + type + optional specialization. Source: NUCC Health Care Provider Taxonomy Code Set (public; CMS-accepted). WHEN TO USE: Resolving a NUCC provider taxonomy code to its specialty description. WHEN NOT: For finding a provider by specialty in a region (not yet implemented).

  ConnectorNo auth

• explain_findingA

  MalinoisA

  Returns the plain-language meaning and step-by-step fix for one Malinois finding. Use it while helping the user fix an issue reported by scan_app, or when they ask what a finding means. Pass the rule_id exactly as scan_app returned it. Read-only, no network, instant.

  ConnectorNo auth

• tascan_post_messageA

  TaScanB

  Post a message on a task trail (protocol v0.2 trail_messages): kind question, answer, handoff or discussion. A message never completes a task, never satisfies a gate and never pages anyone. The actor is stamped from your credential (key:<id>, actor_type "key" — a credential, never a human), never from the body; the executor and the reviewer consume a key's answers only when the key holds agent:dispatch. On an ordinary task this is write tier. On a CYCLE task (one with coord) it needs agent:dispatch (agent:dispatch:code when the task, or the asker a question task stands for, is CODE:/SHELL:) because the text can become executor prompt or reviewer input. kind=answer on a dispatcher-addressed question task answers it through coord_answer_question and releases the blocked asker; a human-addressed question is answered only on the worker page (403 here). finding (reviewer runner) and decision (human completion) cannot be posted. Body ≤ 8000 chars; idempotency_key makes a replay return the same message.

  ConnectorNo auth

• record_finding_verdictA

  aictrlA

  Apply a post-hoc triage verdict to a finding that was previously recorded via record_finding. Used by the /reply-to-code-review flow to persist whether a finding is TRUE / FALSE / UNCERTAIN and the FIX / DEFER / IGNORE action taken. The finding is located only by the exact `finding_id` returned by list_pr_findings, on ANY lifecycle status (open, fixed, or dismissed — so verdicts still apply after a PR is merged and findings were swept to dismissed). Only findings recorded into the data layer (the aictrl-dev MCP path) can receive a verdict. Idempotent: re-applying overwrites the prior verdict. A not_found response is an application error; call list_pr_findings to refresh stale IDs and do not treat the write as successful. `judged_at_sha` is required: send the full 40-hex commit SHA of the code you actually read. A SHA that is neither the review SHA nor a later commit of the same PR is rejected with validation_error. `reasoning` is required too (#5364): a verdict whose reasoning cannot be audited later is not worth storing. Each write appends to the finding's judgment history; a re-judge from the same run at the same commit updates that run's own row rather than appending a duplicate. A FALSE verdict on an OPEN finding of severity MINOR or NIT (medium/low/info) also dismisses it as a false positive, with your `reason` as the note; on MAJOR or BLOCKER (high/critical) it stays a suggestion a person confirms. The result reports `autoDismissed` (and `autoDismissReason` when false). A dismissal is not reopened by this tool; a person can restore the finding from the pull-request page.

  Connector

  Destructive

  API key

• get_tier1_recommendationsA

  Tier1 IT AssessmentA

  Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.

  ConnectorNo auth

• run_gauntletA

  SHPBL: Repository Audit & RepairA

  One runner for an entire SHPBL repository audit and repair: survey, opening library comparison, evaluation, repair, the batched harvest, closing library comparison, the branded HTML report, and the write-back path. STRICT SEQUENCE: call it once with no `step` for the run card, then `step: 1`, `step: 2`, one step per turn, in order. Do the returned step, report one line to the person, then call the next. Never call two steps in one turn, never attempt the whole run at once, and never infer a finding you were not handed. From `step: 2` on you must pass `ledger_digest`; every 3 steps (adjustable with `checkpoint_interval`, max 10, only when the person asks for fewer pauses) the run pauses and you must ask the person before continuing, then pass `continue_ack: "continue"`. The final step hands over the report template and the write-back path. Your own model does all reading and writing. This full conductor requires a Practitioner key (7-day free trial). The free lane provides repository evaluation, not a partial or full gauntlet.

  ConnectorNo auth

• update_load_test_notesA

  LoadsterA

  Replace the notes on a finished Load Test's Test Report — the only thing on a Load Test this surface edits. Ask the user before writing: notes belong to the user, and advising on a test never requires writing them. The text sent becomes the report's entire notes, so first read the current notes with get_load_test_report and preserve the user's content in what you send.

  Connector

  Destructive

  OAuth

• gunspec_api_operationA

  GunSpecA

  Returns what the GunSpec API reference documents for an endpoint: its parameters and accepted values, the plan it needs, whether a key is required, caching, every error status with the error.reason values to branch on, and the languages a sample is printed in. Use this tool before writing or explaining code that calls the GunSpec API, instead of recalling parameters. The path may be a template (/v1/firearms/{id}), a concrete path or a URL; a partial path such as /v1/vendor lists the operations under it.

  ConnectorAPI key

• describePricingEquationApiA

  PhasioA

  Start here before reading, writing or changing a pricing equation. Returns the TypeScript contract the equation runs against (specification, revision, requisition, customer, workflow, done(), variable(), round, useDimension, createBands; for scope ORDER: parts, subtotal, customer, addLineItem), narrowed to the given scope + ownerId: its technology, material names and material variable names, lead-time names, and which modules the manufacturer has. Explains the loop: save(entity=typescriptEquation) to validate and store a draft, generateQuote(equationId) to test it, then — only on the manufacturer's explicit request — publishEquation to make it live. Pass includeSource=true to also get the live equation's source, or equationId=<id> to get the source of one specific equation (a draft, for example) with its live/not-live state.

  ConnectorAPI key

• load_skillA

  AeviaA

  How this Aevia connection works, plus playbooks for results, reports, systems. Returns a skill's playbook as the result; takes no action itself. A playbook is step-by-step guidance for a multi-step job, too long for a description. `connector_guide` covers how this connection works: workspaces, refs, finding data, the library, building, calculating and failures. `assessment_interpretation` covers reading and comparing results: what an indicator result is and is not, a figure's anchors, functional-unit equivalence and comparison discipline. `report_writing` covers writing results up as a document, from a screening note to an ISO 14044 study. `product_system_authoring` covers building a new product system with `lca_compose_assembly` / `lca_compose_linked`: build order, which of the two fits, failure modes, and tagging life-cycle phases. A loaded playbook stays in context; one load per session suffices. Skills are gated on what the token can call; an unavailable request returns the available list.

  ConnectorAPI key

• ask_agentA

  SwogeAgenticA

  Use this when a question needs several of these tools chained together and a written answer, for example comparing tokens or researching a launcher. SwogeAgentic, a Claude agent, picks the tools, reads the numbers and answers in Markdown with its sources and sample sizes. API key only: billed at its real cost, up to the quoted maximum ("quote": true gives it). Takes 10 to 60 seconds.

  ConnectorNo auth

• tag_contactsA

  SendingA

  Applies a tag to one or more contacts (max 100). Get the `tagId` from list_tags (or from create_tag for a new one). Idempotent: contacts already tagged are ignored. Each application emits the contact.tag_added event: use list_automations to see which automations listen to that event before writing.

  ConnectorAPI key

• describePricingEquationApiA

  PhasioA

  Start here before reading, writing or changing a pricing equation. Returns the TypeScript contract the equation runs against (specification, revision, requisition, customer, workflow, done(), variable(), round, useDimension, createBands; for scope ORDER: parts, subtotal, customer, addLineItem), narrowed to the given scope + ownerId: its technology, material names and material variable names, lead-time names, and which modules the manufacturer has. Explains the loop: save(entity=typescriptEquation) to validate and store a draft, generateQuote(equationId) to test it, then — only on the manufacturer's explicit request — publishEquation to make it live. Pass includeSource=true to also get the live equation's source, or equationId=<id> to get the source of one specific equation (a draft, for example) with its live/not-live state.

  ConnectorAPI key

• crypto_reportA

  EventTrader MCPB

  A short research report on what a link or a topic means for one coin, grounded in the coin's dashboard, with its own public page to share. To ask: pass symbol and about (a public http(s) link such as a post on X, a press release or an article, or a topic of 3 to 300 characters); the answer comes at once with status=writing and the report's id. To read: pass report_id (no key needed); status is writing, ready or unavailable. At most 6 reports an hour and one a minute. The report is written by EventTrader's AI and can be wrong. Asking needs a registered agent (API key). From EventTrader's crypto dashboards (cymetica.com/crypto). Every number carries its source and time; a number that failed a plausibility check is withheld, never guessed. Places no orders, moves no funds. Not financial advice.

  ConnectorNo auth

• verify_readiness_fixA

  CleoticA

  Re-check a fix without a full scan. With opportunity_id, re-checks an inbox readiness task; the result updates the task. With check_id, re-checks that open finding on its affected pages. Returns pending with the re-check's id; follow it with get_operation or get_readiness_finding's check_request_id. Cost: by opportunity_id free, once every 10 minutes; by check_id one of the plan's monthly re-checks.

  ConnectorOAuth

• search_exercisesA

  MoveMate: Gym Workout TrackerA

  Looks up exercises in MoveMate's library (including the user's own custom exercises) and returns their exercise_id and exercise_type. Renders nothing for the user — it is the lookup for building or editing a workout. The model must only compose workouts from exercises returned here — never invented ones. Resolve every exercise a workout needs in ONE call: pass all their names in queries rather than calling once per exercise. Each result carries an exercise_type saying how that movement is measured (reps, time, distance, or speed and level on a cardio machine) — it decides which target fields create_planned_workout will accept for it, so read it before writing sets. To show exercises to the user ("what can I do for chest?"), call show_exercises instead.

  ConnectorOAuth

• add_keywordsA

  AppTail – ASO & Keyword ResearchA

  Start tracking search terms for one of your apps, in one storefront. Send terms, or `keyword_ids` for suggestions returned by discover_keywords — a suggestion MUST be added by id, because re-resolving its term can land on a different keyword row. Counts against the plan's per-app keyword limit; `dry_run` reports what would happen without writing anything. Terms already in the corpus come back under `already_tracked` rather than as an error — that is the state the caller asked for.

  ConnectorNo auth