Connect-MCP

SMI Aware Assistant

com.smiaware.mcp/smi-aware-assistant · v0.1.1

Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.

MCPremoteno credentialsE-commerce

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 40 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 99/100

What it does: 40 tools · 20 read, 20 write · E-commerce

Test call onboarding_next_step: worked (986 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +9
  • Read/write annotations: +5
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://mcp.smiaware.com/mcp

Tools

40 tools listed at last check
  • onboarding_next_step 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 net
  • verify_access Verifies the session Personal Access Token (PAT) against the SMI identity endpoint and returns the resolved account identity.
  • smi_get_cowork_instructions 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;
  • submit_contact_request 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.
  • smi_list_deep_reports Lists SMI deep reports with pagination and optional filtering.
  • smi_get_deep_report 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
  • smi_create_deep_report 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_submit_deep_reports Submits previously created SMI deep report drafts (Draft status only) for processing.
  • smi_request_upload_url 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 f
  • smi_confirm_upload 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_list_exports Lists SMI exports with pagination and optional filtering.
  • smi_get_export 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_create_export 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_submit_exports Submits previously created SMI export drafts (Draft status only) for processing.
  • smi_list_projects Lists SMI projects with pagination.
  • smi_list_products Lists the SMI reference set of products.
  • smi_list_platforms Lists the SMI reference set of platforms.
  • smi_list_statuses Lists the SMI reference set of statuses.
  • smi_list_relationships Lists the SMI reference set of relationships.
  • smi_get_report_findings 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 includ
  • smi_get_deep_report_releases 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_export_releases Lists releases for a given SMI export, with pagination.
  • smi_check_order_complete 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
  • search 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 resu
  • fetch 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 readine
  • smi_analyze 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 pro
  • smi_add_subject_address Attaches a postal address to an SMI subject.
  • smi_add_subject_phone Attaches a phone number to an SMI subject.
  • smi_add_subject_email Attaches an email address to an SMI subject.
  • smi_add_subject_alias Attaches an alias to an SMI subject.
  • smi_add_subject_surname Attaches a surname to an SMI subject.
  • smi_add_subject_url Attaches a url to an SMI subject.
  • smi_add_subject_employer Attaches an employer to an SMI subject.
  • smi_add_subject_employee Attaches an employee to an SMI subject (for COMPANY-type subjects).
  • smi_add_subject_employee_url Attaches a url to an SMI subject employee, referenced by the subjectEmployeeId returned from smi_add_subject_employee.
  • smi_add_subject_education Attaches an educational institution to an SMI subject.
  • smi_add_subject_relationship Attaches a relationship to an SMI subject, using a relationshipId from smi_list_relationships.
  • smi_add_subject_relationship_url Attaches a url to an SMI subject relationship, referenced by the subjectRelationshipId returned from smi_add_subject_relationship.
  • smi_update_subject 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/birthD
  • smi_get_subject 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.

Badge

Connect-MCP badge for com.smiaware.mcp/smi-aware-assistant

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/com.smiaware.mcp/smi-aware-assistant.svg)](https://clawy.uk/mcp/s/com.smiaware.mcp/smi-aware-assistant)

Repository · Website