Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SMI Aware Assistant

REMOTE · MCP.SMIAWARE.COM · SCANNED SEP 30

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

Available components

+46 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5051 tokens (~117/item across 43 items; 40 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
  • Structured output schemas are declared (90% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 40 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 41 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the SMI Aware Assistant MCP server?

SMI Aware Assistant is a hosted endpoint at https://mcp.smiaware.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.smiaware.com

# add to Claude Code
claude mcp add --transport http com-smiaware-mcp-smi-aware-assistant 'https://mcp.smiaware.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-smiaware-mcp-smi-aware-assistant": {
      "url": "https://mcp.smiaware.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-smiaware-mcp-smi-aware-assistant": {
      "type": "http",
      "url": "https://mcp.smiaware.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-smiaware-mcp-smi-aware-assistant]
url = "https://mcp.smiaware.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-smiaware-mcp-smi-aware-assistant": {
      "type": "remote",
      "url": "https://mcp.smiaware.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-smiaware-mcp-smi-aware-assistant --url 'https://mcp.smiaware.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-smiaware-mcp-smi-aware-assistant:
    url: "https://mcp.smiaware.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-smiaware-mcp-smi-aware-assistant": {
      "Transport": "http",
      "Url": "https://mcp.smiaware.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-smiaware-mcp-smi-aware-assistant -t streamable-http -u 'https://mcp.smiaware.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-smiaware-mcp-smi-aware-assistant": {
      "type": "http",
      "url": "https://mcp.smiaware.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 30 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +43
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 93 functional
    • First check of Tool coverage: 90 functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 30 Sept 2026 · Probed https://mcp.smiaware.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.smiaware.com CN=YE2,O=Let's Encrypt,C=US 7 Aug 2026 5 Nov 2026 ECDSA 256 ECDSA-SHA384 59c32c7821224847f2e2dd6641d8f562fe2
SANs: mcp.smiaware.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.smiaware.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
smiaware.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.smiaware.com/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://mcp.smiaware.com/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Protected resource metadata

Document https://mcp.smiaware.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.smiaware.com/mcp
Authorisation server https://mcp.smiaware.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.smiaware.com/mcp Verified 200
http (plaintext) http://mcp.smiaware.com/mcp HTTPS enforced 308 https://mcp.smiaware.com/mcp
MCP tools · 40 exposed · ~4,930 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fetch ~105

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.

NameTypeReqDescription
idstringyesA typed reference returned by search, e.g. "deep_report:123"
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

onboarding_next_step ~120

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.

NameTypeReqDescription
hasTokenstring–Answer to the fork question "Do you already have an SMI token?" — omit on the first call to receive the question.

No output schema declared.

No examples provided.

search ~195

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.

NameTypeReqDescription
querystringyesFree-text search query, e.g. a subject name or record id
NameTypeReqDescription
resultsarrayyes–

No examples provided.

smi_add_subject_address ~184

Attaches a postal address to an SMI subject.

NameTypeReqDescription
citystring–The city.
countrystringyesThe country the address is in, spelled out (e.g. United States).
countystring–The county, if the user gave one.
isCurrentbooleanyesWhether the subject currently lives at this address, as opposed to a former one. Ask the user directly if it isn't clear from context.
statestring–The state or province.
street1string–The street number and name.
street2string–A second address line, such as an apartment, suite, or unit number.
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
zipstring–The postal or zip code.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_alias ~59

Attaches an alias to an SMI subject.

NameTypeReqDescription
aliasstringyesA name the subject is also known by.
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_education ~227

Attaches an educational institution to an SMI subject.

NameTypeReqDescription
endMonthinteger–When the subject stopped attending or graduated, if they have. A month number from 1 (January) to 12 (December).
endYearinteger–When the subject stopped attending or graduated, if they have. A four-digit year, e.g. 2019.
isCurrentbooleanyesWhether the subject is currently enrolled at this institution, as opposed to having left or graduated. Ask the user directly if it isn't clear from context.
majorstring–The subject's field of study, if known.
namestringyesThe institution's name.
startMonthinteger–When the subject started attending. A month number from 1 (January) to 12 (December).
startYearinteger–When the subject started attending. A four-digit year, e.g. 2019.
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_email ~60

Attaches an email address to an SMI subject.

NameTypeReqDescription
emailstringyesThe email address to attach to the subject.
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_employee ~262

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

NameTypeReqDescription
endMonthinteger–When this employee's job ended, if it has. A month number from 1 (January) to 12 (December).
endYearinteger–When this employee's job ended, if it has. A four-digit year, e.g. 2019.
firstNamestringyesThe employee's first name.
isCurrentbooleanyesWhether this person currently works for the subject company, as opposed to a former employee. Ask the user directly if it isn't clear from context.
lastNamestringyesThe employee's last name.
middleNamestring–The employee's middle name, if known.
positionstring–The employee's job title or role at the subject company.
startMonthinteger–When this employee's job started. A month number from 1 (January) to 12 (December).
startYearinteger–When this employee's job started. A four-digit year, e.g. 2019.
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_employee_url ~74

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

NameTypeReqDescription
subjectEmployeeId–yesThe id smi_add_subject_employee returned for this employee record.
urlstringyesA url tied to this employee's own profile or accounts.
NameTypeReqDescription
recordId–––
subjectEmployeeId–yes–

No examples provided.

smi_add_subject_employer ~225

Attaches an employer to an SMI subject.

NameTypeReqDescription
endMonthinteger–When the subject left this job, if they have. A month number from 1 (January) to 12 (December).
endYearinteger–When the subject left this job, if they have. A four-digit year, e.g. 2019.
isCurrentbooleanyesWhether this is the subject's current employer, as opposed to a former one. Ask the user directly if it isn't clear from context.
namestringyesThe employer's name.
positionstring–The subject's job title or role at this employer.
startMonthinteger–When the subject started this job. A month number from 1 (January) to 12 (December).
startYearinteger–When the subject started this job. A four-digit year, e.g. 2019.
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_phone ~75

Attaches a phone number to an SMI subject.

NameTypeReqDescription
extensionstring–The phone extension, if there is one.
phonestringyesThe phone number to attach to the subject.
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_relationship ~122

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

NameTypeReqDescription
firstNamestringyesThe related person's first name.
lastNamestringyesThe related person's last name.
middleNamestring–The related person's middle name, if known.
relationshipId–yesThe relationship type id from smi_list_relationships (e.g. spouse, parent, associate).
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_relationship_url ~74

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

NameTypeReqDescription
subjectRelationshipId–yesThe id smi_add_subject_relationship returned for this relationship record.
urlstringyesA url tied to the related person's own profile or accounts.
NameTypeReqDescription
recordId–––
subjectRelationshipId–yes–

No examples provided.

smi_add_subject_surname ~66

Attaches a surname to an SMI subject.

NameTypeReqDescription
namestringyesAn additional or prior surname for the subject, such as a maiden name.
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_add_subject_url ~62

Attaches a url to an SMI subject.

NameTypeReqDescription
subjectId–yesThe subject's id, from a prior smi_get_subject or subject-enrichment call.
urlstringyesA url tied to the subject's own profile or accounts.
NameTypeReqDescription
recordId–––
subjectId–yes–

No examples provided.

smi_analyze ~185

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.

NameTypeReqDescription
notesstringyesFree-text case notes to score against the 5-signal gap-analysis rubric.
thresholdsobject–Optional override of the RECOMMEND/REVIEW verdict thresholds.
weightsobject–Optional override of all 5 signal weights; normalized to sum 100.
NameTypeReqDescription
confidencestringyesConfidence in the verdict, derived from how many of the 5 signals were detected.
orderDataobjectyesBest-effort prefill for smi_create_deep_report; fields absent when undetectable.
signalsarrayyesPer-signal scoring breakdown.
signalsDetectedarrayyesSignal ids whose fraction is 1 (fully detected).
signalsNotDetectedarrayyesSignal ids whose fraction is below 1 (not detected).
suggestedProductstringyesRecommended SMI product based on the detected subject kind.
totalnumberyesWeighted total score, 0-100.
verdictstringyesOverall gap-analysis verdict.

No examples provided.

smi_check_order_complete ~219

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.

NameTypeReqDescription
orderIdstringyesDeep-report or export record id — the same id returned as draftIds by smi_create_deep_report and accepted by fetch. There is no separate order-level id. Product-prefixed ids are accepted and stripped…
orderTypestringyesWhether the order is a deep report or an export
NameTypeReqDescription
orderIdstringyes–
orderTypestringyes–
readybooleanyes–
statestringyes–
statusstringyes–
terminalbooleanyes–

No examples provided.

smi_confirm_upload ~77

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).

NameTypeReqDescription
deepReportIdintegeryes–
fileNamestringyes–
versionstringyes–
NameTypeReqDescription
deepReportIdnumberyes–
fileNamestringyes–
idnumberyes–

No examples provided.

smi_create_deep_report ~102

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.

NameTypeReqDescription
ordersarrayyes–
projectId––The SMI project (matter/case) every order in this call is filed under. One call cannot span two projects, so call once per project. Get ids from smi_list_projects.
NameTypeReqDescription
draftIdsarrayyes–
requestedCountintegeryes–
warningstring––

No examples provided.

smi_create_export ~100

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.

NameTypeReqDescription
ordersarrayyes–
projectId––The SMI project (matter/case) every order in this call is filed under. One call cannot span two projects, so call once per project. Get ids from smi_list_projects.
NameTypeReqDescription
draftIdsarrayyes–
requestedCountintegeryes–
warningstring––

No examples provided.

smi_get_cowork_instructions ~87

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

smi_get_deep_report ~230

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.

NameTypeReqDescription
idstringyesSMI resource id. Accepts a bare numeric id or a product-prefixed one (RB = Research Bundle, DR = Deep Report, EX = Export); the prefix is stripped before the call. Research Bundles and Deep Reports a…
includearray–Related resources to include: subject, findings, releases, uploads. SMI accepts "findings" but never populates it: the response carries no findings key at all, even for a report that has findings, wh…
NameTypeReqDescription
recordobjectyes–

No examples provided.

smi_get_deep_report_releases ~110

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.

NameTypeReqDescription
deepReportIdintegeryesId of the deep report whose releases should be listed
pageinteger–1-based page number to return
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_get_export ~135

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.

NameTypeReqDescription
idstringyesSMI resource id. Accepts a bare numeric id or a product-prefixed one (RB = Research Bundle, DR = Deep Report, EX = Export); the prefix is stripped before the call. Research Bundles and Deep Reports a…
includearray–Related resources to include: releases
NameTypeReqDescription
recordobjectyes–

No examples provided.

smi_get_export_releases ~71

Lists releases for a given SMI export, with pagination.

NameTypeReqDescription
exportIdintegeryesId of the export whose releases should be listed
pageinteger–1-based page number to return
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_get_report_findings ~309

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.

NameTypeReqDescription
isConfirmedboolean–Only include confirmed findings
isScopeRelatedboolean–Only include findings marked scope-related
pageinteger–1-based page number to return
platformIdsarray–Only include findings for these platforms. Accepts a platform name (Facebook, TikTok) or its numeric id; names are matched case-insensitively.
reportIdsarray–Only include findings belonging to these reports. Accepts a bare numeric id or the displayed prefixed form (RB-11751, DR-402); the prefix is stripped before the call.
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_get_subject ~104

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.

NameTypeReqDescription
deepReportIdstringyesDeep report id whose subject to read (no standalone GET /subjects/{id} exists upstream)
NameTypeReqDescription
deepReportIdstringyes–
subjectobjectyes–

No examples provided.

smi_list_deep_reports ~244

Lists SMI deep reports with pagination and optional filtering.

NameTypeReqDescription
includearray–Related resources to include: subject, findings, releases, uploads. SMI accepts "findings" but never populates it: the response carries no findings key at all, even for a report that has findings, wh…
pageinteger–1-based page number to return
statusstring–Only include records with this status
statusEndDatestring–Only include records with a status on or before this date (YYYY-MM-DD)
statusStartDatestring–Only include records with a status on or after this date (YYYY-MM-DD)
subjectCompanyNamestring–Only include records for a subject with this company name
subjectFirstNamestring–Only include records for a subject with this first name
subjectLastNamestring–Only include records for a subject with this last name
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_list_exports ~137

Lists SMI exports with pagination and optional filtering.

NameTypeReqDescription
includearray–Related resources to include: releases
pageinteger–1-based page number to return
statusstring–Only include records with this status
statusEndDatestring–Only include records with a status on or before this date (YYYY-MM-DD)
statusStartDatestring–Only include records with a status on or after this date (YYYY-MM-DD)
takeinteger–Number of items per page (1-100)
urlstring–Only include records with this url
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_list_platforms ~50

Lists the SMI reference set of platforms.

NameTypeReqDescription
pageinteger–1-based page number to return
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_list_products ~49

Lists the SMI reference set of products.

NameTypeReqDescription
pageinteger–1-based page number to return
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_list_projects ~47

Lists SMI projects with pagination.

NameTypeReqDescription
pageinteger–1-based page number to return
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_list_relationships ~50

Lists the SMI reference set of relationships.

NameTypeReqDescription
pageinteger–1-based page number to return
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_list_statuses ~50

Lists the SMI reference set of statuses.

NameTypeReqDescription
pageinteger–1-based page number to return
takeinteger–Number of items per page (1-100)
NameTypeReqDescription
hasMorebooleanyes–
itemsarrayyes–
pageintegeryes–
takeintegeryes–
totalinteger––

No examples provided.

smi_request_upload_url ~122

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.

NameTypeReqDescription
deepReportIdintegeryes–
fileNamestringyes–
NameTypeReqDescription
fileNamestringyes–
signedUrlstringyes–
uploadMethodstringyes–
versionHeaderstringyes–

No examples provided.

smi_submit_deep_reports ~36

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

NameTypeReqDescription
idsarrayyes–
NameTypeReqDescription
acceptedarrayyes–
outcomesEnumeratedbooleanyes–
rejectedarrayyes–
statusstringyes–

No examples provided.

smi_submit_exports ~33

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

NameTypeReqDescription
idsarrayyes–
NameTypeReqDescription
acceptedarrayyes–
outcomesEnumeratedbooleanyes–
rejectedarrayyes–
statusstringyes–

No examples provided.

smi_update_subject ~340

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.

NameTypeReqDescription
birthDayinteger–The subject's updated day of birth. Treated as the day the company was founded, for a COMPANY subject.
birthMonthinteger–The subject's updated birth month, as a number from 1 (January) to 12 (December). Treated as the month the company was founded, for a COMPANY subject.
birthYearinteger–The subject's updated birth year. Treated as the year the company was founded, for a COMPANY subject.
companyNamestring–The subject's updated company name, required whenever type is COMPANY.
firstNamestring–The subject's updated first name, required whenever type is PERSON.
genderstring–The subject's updated gender (PERSON subjects only).
lastNamestring–The subject's updated last name, required whenever type is PERSON.
subjectId–yesThe SMI subject id to update, from a prior smi_get_subject call.
typestringyesThe subject's type. Required on every call as a discriminator, even when it isn't changing — SMI's PATCH endpoint rejects the request without it. PERSON for a person, COMPANY for a company or organiz…
NameTypeReqDescription
subjectId–yes–
updatedFieldsarrayyes–

No examples provided.

submit_contact_request ~102

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.

NameTypeReqDescription
emailstringyesProspect email address; our team will reach out here.
firstNamestringyesProspect first name.
lastNamestringyesProspect last name.
organizationstringyesProspect's organization name.

No output schema declared.

No examples provided.

verify_access ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the SMI Aware Assistant MCP server?

SMI Aware Assistant is an MCP server listed in the public MCP registry as com.smiaware.mcp/smi-aware-assistant. Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP. This page covers its hosted endpoint (https://mcp.smiaware.com/mcp).

Is the SMI Aware Assistant MCP server safe to use?

SMI Aware Assistant scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SMI Aware Assistant MCP server expose?

SMI Aware Assistant exposes 40 tools: onboarding_next_step, verify_access, smi_get_cowork_instructions, submit_contact_request, smi_list_deep_reports, and 35 more. Their descriptions and schemas cost roughly 4,930 tokens of context every time the server is loaded.

Does the SMI Aware Assistant MCP server require authentication?

Yes. SMI Aware Assistant asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the SMI Aware Assistant MCP server still maintained?

SMI Aware Assistant is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.