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
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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
claude mcp add --transport http com-smiaware-mcp-smi-aware-assistant 'https://mcp.smiaware.com/mcp'
{
"mcpServers": {
"com-smiaware-mcp-smi-aware-assistant": {
"url": "https://mcp.smiaware.com/mcp"
}
}
} {
"servers": {
"com-smiaware-mcp-smi-aware-assistant": {
"type": "http",
"url": "https://mcp.smiaware.com/mcp"
}
}
} [mcp_servers.com-smiaware-mcp-smi-aware-assistant] url = "https://mcp.smiaware.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-smiaware-mcp-smi-aware-assistant": {
"type": "remote",
"url": "https://mcp.smiaware.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-smiaware-mcp-smi-aware-assistant --url 'https://mcp.smiaware.com/mcp' --transport streamable-http
mcp_servers:
com-smiaware-mcp-smi-aware-assistant:
url: "https://mcp.smiaware.com/mcp" {
"McpServers": {
"com-smiaware-mcp-smi-aware-assistant": {
"Transport": "http",
"Url": "https://mcp.smiaware.com/mcp"
}
}
} assistant mcp add com-smiaware-mcp-smi-aware-assistant -t streamable-http -u 'https://mcp.smiaware.com/mcp'
{
"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.
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
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 |
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 →
fetch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A typed reference returned by search, e.g. "deep_report:123" |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
onboarding_next_step SMI 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.
| Name | Type | Req | Description |
|---|---|---|---|
| hasToken | string | – | 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text search query, e.g. a subject name or record id |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
smi_add_subject_address Add Subject Address ~184
Attaches a postal address to an SMI subject.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | The city. |
| country | string | yes | The country the address is in, spelled out (e.g. United States). |
| county | string | – | The county, if the user gave one. |
| isCurrent | boolean | yes | Whether the subject currently lives at this address, as opposed to a former one. Ask the user directly if it isn't clear from context. |
| state | string | – | The state or province. |
| street1 | string | – | The street number and name. |
| street2 | string | – | A second address line, such as an apartment, suite, or unit number. |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| zip | string | – | The postal or zip code. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_alias Add Subject Alias ~59
Attaches an alias to an SMI subject.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | A name the subject is also known by. |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_education Add Subject Education ~227
Attaches an educational institution to an SMI subject.
| Name | Type | Req | Description |
|---|---|---|---|
| endMonth | integer | – | When the subject stopped attending or graduated, if they have. A month number from 1 (January) to 12 (December). |
| endYear | integer | – | When the subject stopped attending or graduated, if they have. A four-digit year, e.g. 2019. |
| isCurrent | boolean | yes | Whether 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. |
| major | string | – | The subject's field of study, if known. |
| name | string | yes | The institution's name. |
| startMonth | integer | – | When the subject started attending. A month number from 1 (January) to 12 (December). |
| startYear | integer | – | When the subject started attending. A four-digit year, e.g. 2019. |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_email Add Subject Email ~60
Attaches an email address to an SMI subject.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to attach to the subject. | |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_employee Add Subject Employee ~262
Attaches an employee to an SMI subject (for COMPANY-type subjects).
| Name | Type | Req | Description |
|---|---|---|---|
| endMonth | integer | – | When this employee's job ended, if it has. A month number from 1 (January) to 12 (December). |
| endYear | integer | – | When this employee's job ended, if it has. A four-digit year, e.g. 2019. |
| firstName | string | yes | The employee's first name. |
| isCurrent | boolean | yes | Whether 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. |
| lastName | string | yes | The employee's last name. |
| middleName | string | – | The employee's middle name, if known. |
| position | string | – | The employee's job title or role at the subject company. |
| startMonth | integer | – | When this employee's job started. A month number from 1 (January) to 12 (December). |
| startYear | integer | – | When this employee's job started. A four-digit year, e.g. 2019. |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_employee_url Add Subject Employee Url ~74
Attaches a url to an SMI subject employee, referenced by the subjectEmployeeId returned from smi_add_subject_employee.
| Name | Type | Req | Description |
|---|---|---|---|
| subjectEmployeeId | – | yes | The id smi_add_subject_employee returned for this employee record. |
| url | string | yes | A url tied to this employee's own profile or accounts. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectEmployeeId | – | yes | – |
No examples provided.
smi_add_subject_employer Add Subject Employer ~225
Attaches an employer to an SMI subject.
| Name | Type | Req | Description |
|---|---|---|---|
| endMonth | integer | – | When the subject left this job, if they have. A month number from 1 (January) to 12 (December). |
| endYear | integer | – | When the subject left this job, if they have. A four-digit year, e.g. 2019. |
| isCurrent | boolean | yes | Whether this is the subject's current employer, as opposed to a former one. Ask the user directly if it isn't clear from context. |
| name | string | yes | The employer's name. |
| position | string | – | The subject's job title or role at this employer. |
| startMonth | integer | – | When the subject started this job. A month number from 1 (January) to 12 (December). |
| startYear | integer | – | When the subject started this job. A four-digit year, e.g. 2019. |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_phone Add Subject Phone Number ~75
Attaches a phone number to an SMI subject.
| Name | Type | Req | Description |
|---|---|---|---|
| extension | string | – | The phone extension, if there is one. |
| phone | string | yes | The phone number to attach to the subject. |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_relationship Add Subject Relationship ~122
Attaches a relationship to an SMI subject, using a relationshipId from smi_list_relationships.
| Name | Type | Req | Description |
|---|---|---|---|
| firstName | string | yes | The related person's first name. |
| lastName | string | yes | The related person's last name. |
| middleName | string | – | The related person's middle name, if known. |
| relationshipId | – | yes | The relationship type id from smi_list_relationships (e.g. spouse, parent, associate). |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_relationship_url Add Subject Relationship Url ~74
Attaches a url to an SMI subject relationship, referenced by the subjectRelationshipId returned from smi_add_subject_relationship.
| Name | Type | Req | Description |
|---|---|---|---|
| subjectRelationshipId | – | yes | The id smi_add_subject_relationship returned for this relationship record. |
| url | string | yes | A url tied to the related person's own profile or accounts. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectRelationshipId | – | yes | – |
No examples provided.
smi_add_subject_surname Add Subject Surname ~66
Attaches a surname to an SMI subject.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | An additional or prior surname for the subject, such as a maiden name. |
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_add_subject_url Add Subject Url ~62
Attaches a url to an SMI subject.
| Name | Type | Req | Description |
|---|---|---|---|
| subjectId | – | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. |
| url | string | yes | A url tied to the subject's own profile or accounts. |
| Name | Type | Req | Description |
|---|---|---|---|
| recordId | – | – | – |
| subjectId | – | yes | – |
No examples provided.
smi_analyze Analyze Case Notes ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | yes | Free-text case notes to score against the 5-signal gap-analysis rubric. |
| thresholds | object | – | Optional override of the RECOMMEND/REVIEW verdict thresholds. |
| weights | object | – | Optional override of all 5 signal weights; normalized to sum 100. |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | string | yes | Confidence in the verdict, derived from how many of the 5 signals were detected. |
| orderData | object | yes | Best-effort prefill for smi_create_deep_report; fields absent when undetectable. |
| signals | array | yes | Per-signal scoring breakdown. |
| signalsDetected | array | yes | Signal ids whose fraction is 1 (fully detected). |
| signalsNotDetected | array | yes | Signal ids whose fraction is below 1 (not detected). |
| suggestedProduct | string | yes | Recommended SMI product based on the detected subject kind. |
| total | number | yes | Weighted total score, 0-100. |
| verdict | string | yes | Overall gap-analysis verdict. |
No examples provided.
smi_check_order_complete 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.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | Deep-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… |
| orderType | string | yes | Whether the order is a deep report or an export |
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | – |
| orderType | string | yes | – |
| ready | boolean | yes | – |
| state | string | yes | – |
| status | string | yes | – |
| terminal | boolean | yes | – |
No examples provided.
smi_confirm_upload Confirm Deep Report 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).
| Name | Type | Req | Description |
|---|---|---|---|
| deepReportId | integer | yes | – |
| fileName | string | yes | – |
| version | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deepReportId | number | yes | – |
| fileName | string | yes | – |
| id | number | yes | – |
No examples provided.
smi_create_deep_report 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.
| Name | Type | Req | Description |
|---|---|---|---|
| orders | array | yes | – |
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| draftIds | array | yes | – |
| requestedCount | integer | yes | – |
| warning | string | – | – |
No examples provided.
smi_create_export 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.
| Name | Type | Req | Description |
|---|---|---|---|
| orders | array | yes | – |
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| draftIds | array | yes | – |
| requestedCount | integer | yes | – |
| warning | string | – | – |
No examples provided.
smi_get_cowork_instructions Get SMI Setup 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | SMI 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… |
| include | array | – | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
smi_get_deep_report_releases 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.
| Name | Type | Req | Description |
|---|---|---|---|
| deepReportId | integer | yes | Id of the deep report whose releases should be listed |
| page | integer | – | 1-based page number to return |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_get_export 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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | SMI 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… |
| include | array | – | Related resources to include: releases |
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
smi_get_export_releases Get Export Releases ~71
Lists releases for a given SMI export, with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| exportId | integer | yes | Id of the export whose releases should be listed |
| page | integer | – | 1-based page number to return |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_get_report_findings 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.
| Name | Type | Req | Description |
|---|---|---|---|
| isConfirmed | boolean | – | Only include confirmed findings |
| isScopeRelated | boolean | – | Only include findings marked scope-related |
| page | integer | – | 1-based page number to return |
| platformIds | array | – | Only include findings for these platforms. Accepts a platform name (Facebook, TikTok) or its numeric id; names are matched case-insensitively. |
| reportIds | array | – | 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. |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_get_subject 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.
| Name | Type | Req | Description |
|---|---|---|---|
| deepReportId | string | yes | Deep report id whose subject to read (no standalone GET /subjects/{id} exists upstream) |
| Name | Type | Req | Description |
|---|---|---|---|
| deepReportId | string | yes | – |
| subject | object | yes | – |
No examples provided.
smi_list_deep_reports List Deep Reports ~244
Lists SMI deep reports with pagination and optional filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | 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… |
| page | integer | – | 1-based page number to return |
| status | string | – | Only include records with this status |
| statusEndDate | string | – | Only include records with a status on or before this date (YYYY-MM-DD) |
| statusStartDate | string | – | Only include records with a status on or after this date (YYYY-MM-DD) |
| subjectCompanyName | string | – | Only include records for a subject with this company name |
| subjectFirstName | string | – | Only include records for a subject with this first name |
| subjectLastName | string | – | Only include records for a subject with this last name |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_list_exports List Exports ~137
Lists SMI exports with pagination and optional filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | Related resources to include: releases |
| page | integer | – | 1-based page number to return |
| status | string | – | Only include records with this status |
| statusEndDate | string | – | Only include records with a status on or before this date (YYYY-MM-DD) |
| statusStartDate | string | – | Only include records with a status on or after this date (YYYY-MM-DD) |
| take | integer | – | Number of items per page (1-100) |
| url | string | – | Only include records with this url |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_list_platforms List Platforms ~50
Lists the SMI reference set of platforms.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to return |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_list_products List Products ~49
Lists the SMI reference set of products.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to return |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_list_projects List Projects ~47
Lists SMI projects with pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to return |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_list_relationships List Relationships ~50
Lists the SMI reference set of relationships.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to return |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_list_statuses List Statuses ~50
Lists the SMI reference set of statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number to return |
| take | integer | – | Number of items per page (1-100) |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| items | array | yes | – |
| page | integer | yes | – |
| take | integer | yes | – |
| total | integer | – | – |
No examples provided.
smi_request_upload_url Request Deep Report 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.
| Name | Type | Req | Description |
|---|---|---|---|
| deepReportId | integer | yes | – |
| fileName | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| fileName | string | yes | – |
| signedUrl | string | yes | – |
| uploadMethod | string | yes | – |
| versionHeader | string | yes | – |
No examples provided.
smi_submit_deep_reports Submit Deep Reports ~36
Submits previously created SMI deep report drafts (Draft status only) for processing.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | array | yes | – |
| outcomesEnumerated | boolean | yes | – |
| rejected | array | yes | – |
| status | string | yes | – |
No examples provided.
smi_submit_exports Submit Exports ~33
Submits previously created SMI export drafts (Draft status only) for processing.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | array | yes | – |
| outcomesEnumerated | boolean | yes | – |
| rejected | array | yes | – |
| status | string | yes | – |
No examples provided.
smi_update_subject 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.
| Name | Type | Req | Description |
|---|---|---|---|
| birthDay | integer | – | The subject's updated day of birth. Treated as the day the company was founded, for a COMPANY subject. |
| birthMonth | integer | – | 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. |
| birthYear | integer | – | The subject's updated birth year. Treated as the year the company was founded, for a COMPANY subject. |
| companyName | string | – | The subject's updated company name, required whenever type is COMPANY. |
| firstName | string | – | The subject's updated first name, required whenever type is PERSON. |
| gender | string | – | The subject's updated gender (PERSON subjects only). |
| lastName | string | – | The subject's updated last name, required whenever type is PERSON. |
| subjectId | – | yes | The SMI subject id to update, from a prior smi_get_subject call. |
| type | string | yes | The 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| subjectId | – | yes | – |
| updatedFields | array | yes | – |
No examples provided.
submit_contact_request Submit prospect 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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Prospect email address; our team will reach out here. | |
| firstName | string | yes | Prospect first name. |
| lastName | string | yes | Prospect last name. |
| organization | string | yes | Prospect's organization name. |
No output schema declared.
No examples provided.
verify_access Verify SMI 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.
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.