SMI Aware Assistant MCP server

• fetchFree

  Fetches the full SMI record for a typed reference ("<type>:<id>") that search returned. Pass only an id that appeared in a search result; do not construct one. If you already have a plain SMI record id, use smi_get_deep_report or smi_get_export to read it, or smi_check_order_complete for its readiness.

• onboarding_next_stepFree

  Pre-connection onboarding helper, callable before any SMI token is set. With no input, returns the fork question "Do you already have an SMI token?" — call again with hasToken: "yes" for connect guidance (then verify_access), or hasToken: "no" for prospect-intake guidance. Runs locally; makes no network calls and never reads or requires credentials.

• searchFree

  Open-ended discovery across SMI deep reports, research bundles, and exports when you do not already have a record id — finds candidates by subject name, url, or keyword and returns typed references to pass to fetch. If you already have a record id from the conversation rather than from a search result, call the specific tool instead: smi_get_deep_report or smi_get_export to read one record, smi_check_order_complete for order readiness, smi_list_deep_reports or smi_list_exports for filtered listings, smi_get_report_findings for findings within a report. Deep reports and research bundles are filtered server-side by subject first/last name, broadening to an unfiltered fetch ranked client-side (across id, name, url, summary) when the filtered fetch finds nothing; exports match on url.

• smi_add_subject_addressFree

  Attaches a postal address to an SMI subject.

• smi_add_subject_aliasFree

  Attaches an alias to an SMI subject.

• smi_add_subject_educationFree

  Attaches an educational institution to an SMI subject.

• smi_add_subject_emailwrite actionFree

  Attaches an email address to an SMI subject.

• smi_add_subject_employeeFree

  Attaches an employee to an SMI subject (for COMPANY-type subjects).

• smi_add_subject_employee_urlFree

  Attaches a url to an SMI subject employee, referenced by the subjectEmployeeId returned from smi_add_subject_employee.

• smi_add_subject_employerFree

  Attaches an employer to an SMI subject.

• smi_add_subject_phoneFree

  Attaches a phone number to an SMI subject.

• smi_add_subject_relationshipFree

  Attaches a relationship to an SMI subject, using a relationshipId from smi_list_relationships.

• smi_add_subject_relationship_urlFree

  Attaches a url to an SMI subject relationship, referenced by the subjectRelationshipId returned from smi_add_subject_relationship.

• smi_add_subject_surnameFree

  Attaches a surname to an SMI subject.

• smi_add_subject_urlFree

  Attaches a url to an SMI subject.

• smi_analyzeFree

  Scores free-text case notes against 5 weighted gap-analysis signals (no prior SMI order, high-relevance case type, known online presence, date of loss, social media mentioned) and returns a RECOMMEND/REVIEW/NO ACTION verdict, a confidence rating, which signals were/were not detected, a suggested product, and a best-effort orderData prefill (subject, matter id, case type, date of loss, handles/urls, suggested scope) for smi_create_deep_report. Runs entirely locally; makes no network calls.

• smi_check_order_completewrite actionFree

  Checks the status of a deep report or export record (by its record id, e.g. from smi_create_deep_report draftIds). Returns state = ready | in_progress | draft | failed | unknown and a terminal flag. Poll with bounded attempts and backoff while in_progress; stop as soon as terminal is true (ready or failed) — a failed record will never become ready. Also stop when state is draft: the record was never submitted, so it will not progress until smi_submit_deep_reports or smi_submit_exports is called on it.

• smi_confirm_uploadwrite actionFree

  Confirms a file already PUT to a presigned URL returned by smi_request_upload_url and persists the deep report upload record. Requires the version (the x-amz-version-id response header captured during the PUT).

• smi_create_deep_reportwrite actionFree

  Creates one or more SMI deep report drafts from subject orders. Returns the draft ids for review before submission. All orders in one call are filed under a single project; call once per project.

• smi_create_exportwrite actionFree

  Creates one or more SMI export drafts from profile-url orders. Returns the draft ids for review before submission. All orders in one call are filed under a single project; call once per project.

• smi_get_cowork_instructionsFree

  Returns a consolidated, copy-paste-ready Markdown system prompt of SMI Aware house rules and a when-to-call-which-tool routing guide, plus exact paste-in locations for Claude Projects/Cowork/Desktop, Cursor, and other clients, so the assistant calls the right smi_* tools automatically. Runs locally; makes no network calls and takes no case data.

• smi_get_deep_reportFree

  Fetches a single SMI deep report by id. Research Bundles are deep-report products, so use this tool for a Research Bundle id too rather than constructing a research_bundle: reference for the generic fetch tool. Accepts product-prefixed ids: RB-11751 (Research Bundle) and DR-11751 (Deep Report) both resolve here.

• smi_get_deep_report_releasesFree

  Lists releases for a given SMI deep report, with pagination. Each release links its downloadable deliverable files (report PDF, CSV, JSON) and the findings screenshot archive when available — use this tool to fetch the generated report PDF.

• smi_get_exportFree

  Fetches a single SMI export by id. Accepts product-prefixed ids: EX-30001 resolves here, while RB and DR ids belong to smi_get_deep_report.

• smi_get_export_releasesFree

  Lists releases for a given SMI export, with pagination.

• smi_get_report_findingsFree

  Lists SMI release findings with pagination and optional filtering by report, platform, scope, and confirmation status. Report filters accept the displayed identifier (RB-11751, DR-402) or a bare numeric id, and platform filters accept a platform name (Facebook) or its numeric id. Each finding includes its summary, profile URL, and screenshot/evidence links. Findings are grouped by report and ordered by ascending sequence, so sequence 1 is Finding #1 of that report; refer to a finding by that number rather than by its id, which is an internal record key the reader cannot see. The ordering covers the returned page: SMI decides which findings a page carries, so a report with more findings than take may not begin at Finding #1 on page 1.

• smi_get_subjectFree

  Reads a subject's full profile out of a deep report (no standalone GET /subjects/{id} exists upstream, so the input is a deepReportId, not a subject id). Returns the subject as structured JSON — any atomic field (e.g. date of birth via `subject.birthDate`) can be extracted from it directly.

• smi_list_deep_reportsFree

  Lists SMI deep reports with pagination and optional filtering.

• smi_list_exportsFree

  Lists SMI exports with pagination and optional filtering.

• smi_list_platformsFree

  Lists the SMI reference set of platforms.

• smi_list_productsFree

  Lists the SMI reference set of products.

• smi_list_projectsFree

  Lists SMI projects with pagination.

• smi_list_relationshipsFree

  Lists the SMI reference set of relationships.

• smi_list_statusesFree

  Lists the SMI reference set of statuses.

• smi_request_upload_urlwrite actionFree

  Requests a presigned URL for uploading a large deep-report reference file (csv, doc, docx, gif, jpg, jpeg, pdf, png, txt, webp, xls, xlsx) directly to storage. This server never proxies file bytes: the caller must PUT the file to the returned signedUrl, capture the x-amz-version-id response header from that PUT, and then call smi_confirm_upload with that version to persist the upload record.

• smi_submit_deep_reportswrite actionFree

  Submits previously created SMI deep report drafts (Draft status only) for processing.

• smi_submit_exportswrite actionFree

  Submits previously created SMI export drafts (Draft status only) for processing.

• smi_update_subjectwrite actionFree

  Partially updates an SMI subject via PATCH /subjects/:id. type (PERSON or COMPANY) is required on every call — the SMI backend requires it as a discriminator on every subject PATCH. Editable fields match the API contract: firstName/lastName (or companyName for a COMPANY), birthYear/birthMonth/birthDay, and gender. At least one editable field must be provided.

• submit_contact_requestwrite actionFree

  Submits a prospect contact request — first name, last name, email, and organization — to SMI so the sales team can follow up. For prospects who do not yet have an SMI Aware token.

• verify_accessFree

  Verifies the session Personal Access Token (PAT) against the SMI identity endpoint and returns the resolved account identity.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 777ms20/20
• Tool poisoning40 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 10 write-action tools with no auth3/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityverified namespace with website, no repo4/10

SMI Aware Assistant: common questions

Is SMI Aware Assistant MCP server safe?

With care: it is graded C, so read the findings first (60/100). Read the SMI Aware Assistant safety report

How do I install SMI Aware Assistant?

It runs remotely at mcp.smiaware.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does SMI Aware Assistant need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is SMI Aware Assistant maintained?

The latest release is v0.1.1.

Is SMI Aware Assistant up?

95% of our last 20 checks got an answer. We check remote servers about four times a day.