MCP server for DeepL translation API
Nothing to run from here
SMI Aware Assistant is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
40
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http smi-aware-assistant-mcp https://mcp.smiaware.com/mcp
# 2 — ask your agent for something these tools do
# onboarding_next_step, verify_access, smi_get_cowork_instructions and 37 more
SMI Aware Assistant costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SMAll 1 server
smiaware1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http smi-aware-assistant-mcp https://mcp.smiaware.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
40 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hasToken | string | no | Answer to the fork question "Do you already have an SMI token?" — omit on the first call to receive the question. |
Verifies the session Personal Access Token (PAT) against the SMI identity endpoint and returns the resolved account identity.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| firstName | string | yes | Prospect first name. |
| lastName | string | yes | Prospect last name. |
| string | yes | Prospect email address; our team will reach out here. | |
| organization | string | yes | Prospect's organization name. |
Lists SMI deep reports with pagination and optional filtering.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
| status | string | no | Only include records with this status |
| statusStartDate | string | no | Only include records with a status on or after this date (YYYY-MM-DD) |
| statusEndDate | string | no | Only include records with a status on or before this date (YYYY-MM-DD) |
| subjectFirstName | string | no | Only include records for a subject with this first name |
| subjectLastName | string | no | Only include records for a subject with this last name |
| subjectCompanyName | string | no | Only include records for a subject with this company name |
| include | array | no | 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, whi |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 ar |
| include | array | no | 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, whi |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | no | 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. | |
| orders | array | yes | — |
Submits previously created SMI deep report drafts (Draft status only) for processing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deepReportId | integer | yes | — |
| fileName | string | yes | — |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deepReportId | integer | yes | — |
| fileName | string | yes | — |
| version | string | yes | — |
Lists SMI exports with pagination and optional filtering.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
| status | string | no | Only include records with this status |
| statusStartDate | string | no | Only include records with a status on or after this date (YYYY-MM-DD) |
| statusEndDate | string | no | Only include records with a status on or before this date (YYYY-MM-DD) |
| url | string | no | Only include records with this url |
| include | array | no | Related resources to include: releases |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 ar |
| include | array | no | Related resources to include: releases |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | no | 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. | |
| orders | array | yes | — |
Submits previously created SMI export drafts (Draft status only) for processing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | — |
Lists SMI projects with pagination.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
Lists the SMI reference set of products.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
Lists the SMI reference set of platforms.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
Lists the SMI reference set of statuses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
Lists the SMI reference set of relationships.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
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 order
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
| reportIds | array | no | 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. |
| isScopeRelated | boolean | no | Only include findings marked scope-related |
| isConfirmed | boolean | no | Only include confirmed findings |
| platformIds | array | no | Only include findings for these platforms. Accepts a platform name (Facebook, TikTok) or its numeric id; names are matched case-insensitively. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
| deepReportId | integer | yes | Id of the deep report whose releases should be listed |
Lists releases for a given SMI export, with pagination.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number to return |
| take | integer | no | Number of items per page (1-100) |
| exportId | integer | yes | Id of the export whose releases should be listed |
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 nev
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 |
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_ch
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search query, e.g. a subject name or record id |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A typed reference returned by search, e.g. "deep_report:123" |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| notes | string | yes | Free-text case notes to score against the 5-signal gap-analysis rubric. |
| weights | object | no | Optional override of all 5 signal weights; normalized to sum 100. |
| thresholds | object | no | Optional override of the RECOMMEND/REVIEW verdict thresholds. |
Attaches a postal address to an SMI subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| country | string | yes | The country the address is in, spelled out (e.g. United States). |
| 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. |
| street1 | string | no | The street number and name. |
| street2 | string | no | A second address line, such as an apartment, suite, or unit number. |
| city | string | no | The city. |
| county | string | no | The county, if the user gave one. |
| state | string | no | The state or province. |
| zip | string | no | The postal or zip code. |
Attaches a phone number to an SMI subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| phone | string | yes | The phone number to attach to the subject. |
| extension | string | no | The phone extension, if there is one. |
Attaches an email address to an SMI subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| string | yes | The email address to attach to the subject. |
Attaches an alias to an SMI subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| alias | string | yes | A name the subject is also known by. |
Attaches a surname to an SMI subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| name | string | yes | An additional or prior surname for the subject, such as a maiden name. |
Attaches a url to an SMI subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
Attaches an employer to an SMI subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| name | string | yes | The employer's name. |
| 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. |
| position | string | no | The subject's job title or role at this employer. |
| startMonth | integer | no | When the subject started this job. A month number from 1 (January) to 12 (December). |
| startYear | integer | no | When the subject started this job. A four-digit year, e.g. 2019. |
| endMonth | integer | no | When the subject left this job, if they have. A month number from 1 (January) to 12 (December). |
| endYear | integer | no | When the subject left this job, if they have. A four-digit year, e.g. 2019. |
Attaches an employee to an SMI subject (for COMPANY-type subjects).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| firstName | string | yes | The employee's first name. |
| lastName | string | yes | The employee's last 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. |
| middleName | string | no | The employee's middle name, if known. |
| position | string | no | The employee's job title or role at the subject company. |
| startMonth | integer | no | When this employee's job started. A month number from 1 (January) to 12 (December). |
| startYear | integer | no | When this employee's job started. A four-digit year, e.g. 2019. |
| endMonth | integer | no | When this employee's job ended, if it has. A month number from 1 (January) to 12 (December). |
| endYear | integer | no | When this employee's job ended, if it has. A four-digit year, e.g. 2019. |
Attaches a url to an SMI subject employee, referenced by the subjectEmployeeId returned from smi_add_subject_employee.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
Attaches an educational institution to an SMI subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| name | string | yes | The institution's name. |
| 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 | no | The subject's field of study, if known. |
| startMonth | integer | no | When the subject started attending. A month number from 1 (January) to 12 (December). |
| startYear | integer | no | When the subject started attending. A four-digit year, e.g. 2019. |
| endMonth | integer | no | When the subject stopped attending or graduated, if they have. A month number from 1 (January) to 12 (December). |
| endYear | integer | no | When the subject stopped attending or graduated, if they have. A four-digit year, e.g. 2019. |
Attaches a relationship to an SMI subject, using a relationshipId from smi_list_relationships.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subjectId | yes | The subject's id, from a prior smi_get_subject or subject-enrichment call. | |
| relationshipId | yes | The relationship type id from smi_list_relationships (e.g. spouse, parent, associate). | |
| firstName | string | yes | The related person's first name. |
| lastName | string | yes | The related person's last name. |
| middleName | string | no | The related person's middle name, if known. |
Attaches a url to an SMI subject relationship, referenced by the subjectRelationshipId returned from smi_add_subject_relationship.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 organiza |
| firstName | string | no | The subject's updated first name, required whenever type is PERSON. |
| lastName | string | no | The subject's updated last name, required whenever type is PERSON. |
| companyName | string | no | The subject's updated company name, required whenever type is COMPANY. |
| birthYear | integer | no | The subject's updated birth year. Treated as the year the company was founded, for a COMPANY subject. |
| birthMonth | integer | no | 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. |
| birthDay | integer | no | The subject's updated day of birth. Treated as the day the company was founded, for a COMPANY subject. |
| gender | string | no | The subject's updated gender (PERSON subjects only). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deepReportId | string | yes | Deep report id whose subject to read (no standalone GET /subjects/{id} exists upstream) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SMI Aware Assistant or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish SMI Aware Assistant can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.