com.smiaware.mcp/smi-aware-assistant

Est-ce que com.smiaware.mcp/smi-aware-assistant est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.smiaware.mcp/smi-aware-assistant » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 40 outils

• fetch≈ 275 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    A typed reference returned by search, e.g. "deep_report:123"

  Exemple d'appel

  {"name": "fetch", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "text": "texte", "title": "texte", "metadata": {}}}

• onboarding_next_step≈ 213 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • hasToken · string · optionnel · yes | no
    Answer to the fork question "Do you already have an SMI token?" — omit on the first call to receive the question.

  Exemple d'appel

  {"name": "onboarding_next_step", "arguments": {"hasToken": "yes"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search≈ 392 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    Free-text search query, e.g. a subject name or record id

  Exemple d'appel

  {"name": "search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": []}}

• smi_add_subject_address≈ 454 tokens

  Attaches a postal address to an SMI subject.

  Paramètres, retour & exemple (9)

  Paramètres

  • zip · string · optionnel
    The postal or zip code.
  • city · string · optionnel
    The city.
  • state · string · optionnel
    The state or province.
  • county · string · optionnel
    The county, if the user gave one.
  • country · string · requis
    The country the address is in, spelled out (e.g. United States).
  • street1 · string · optionnel
    The street number and name.
  • street2 · string · optionnel
    A second address line, such as an apartment, suite, or unit number.
  • isCurrent · boolean · requis
    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.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.

  Exemple d'appel

  {"name": "smi_add_subject_address", "arguments": {"country": "texte", "isCurrent": true, "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_alias≈ 251 tokens

  Attaches an alias to an SMI subject.

  Paramètres, retour & exemple (2)

  Paramètres

  • alias · string · requis
    A name the subject is also known by.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.

  Exemple d'appel

  {"name": "smi_add_subject_alias", "arguments": {"alias": "texte", "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_education≈ 506 tokens

  Attaches an educational institution to an SMI subject.

  Paramètres, retour & exemple (8)

  Paramètres

  • name · string · requis
    The institution's name.
  • major · string · optionnel
    The subject's field of study, if known.
  • endYear · integer · optionnel
    When the subject stopped attending or graduated, if they have. A four-digit year, e.g. 2019.
  • endMonth · integer · optionnel
    When the subject stopped attending or graduated, if they have. A month number from 1 (January) to 12 (December).
  • isCurrent · boolean · requis
    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.
  • startYear · integer · optionnel
    When the subject started attending. A four-digit year, e.g. 2019.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.
  • startMonth · integer · optionnel
    When the subject started attending. A month number from 1 (January) to 12 (December).

  Exemple d'appel

  {"name": "smi_add_subject_education", "arguments": {"name": "texte", "isCurrent": true, "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_email≈ 285 tokens

  Attaches an email address to an SMI subject.

  Paramètres, retour & exemple (2)

  Paramètres

  • email · string · requis
    The email address to attach to the subject.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.

  Exemple d'appel

  {"name": "smi_add_subject_email", "arguments": {"email": "texte", "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_employee≈ 556 tokens

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

  Paramètres, retour & exemple (10)

  Paramètres

  • endYear · integer · optionnel
    When this employee's job ended, if it has. A four-digit year, e.g. 2019.
  • endMonth · integer · optionnel
    When this employee's job ended, if it has. A month number from 1 (January) to 12 (December).
  • lastName · string · requis
    The employee's last name.
  • position · string · optionnel
    The employee's job title or role at the subject company.
  • firstName · string · requis
    The employee's first name.
  • isCurrent · boolean · requis
    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.
  • startYear · integer · optionnel
    When this employee's job started. A four-digit year, e.g. 2019.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.
  • middleName · string · optionnel
    The employee's middle name, if known.
  • startMonth · integer · optionnel
    When this employee's job started. A month number from 1 (January) to 12 (December).

  Exemple d'appel

  {"name": "smi_add_subject_employee", "arguments": {"lastName": "texte", "firstName": "texte", "isCurrent": true, "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_employee_url≈ 284 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    A url tied to this employee's own profile or accounts.
  • subjectEmployeeId · ? · requis
    The id smi_add_subject_employee returned for this employee record.

  Exemple d'appel

  {"name": "smi_add_subject_employee_url", "arguments": {"url": "texte", "subjectEmployeeId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectEmployeeId": "texte"}}

• smi_add_subject_employer≈ 488 tokens

  Attaches an employer to an SMI subject.

  Paramètres, retour & exemple (8)

  Paramètres

  • name · string · requis
    The employer's name.
  • endYear · integer · optionnel
    When the subject left this job, if they have. A four-digit year, e.g. 2019.
  • endMonth · integer · optionnel
    When the subject left this job, if they have. A month number from 1 (January) to 12 (December).
  • position · string · optionnel
    The subject's job title or role at this employer.
  • isCurrent · boolean · requis
    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.
  • startYear · integer · optionnel
    When the subject started this job. A four-digit year, e.g. 2019.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.
  • startMonth · integer · optionnel
    When the subject started this job. A month number from 1 (January) to 12 (December).

  Exemple d'appel

  {"name": "smi_add_subject_employer", "arguments": {"name": "texte", "isCurrent": true, "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_phone≈ 290 tokens

  Attaches a phone number to an SMI subject.

  Paramètres, retour & exemple (3)

  Paramètres

  • phone · string · requis
    The phone number to attach to the subject.
  • extension · string · optionnel
    The phone extension, if there is one.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.

  Exemple d'appel

  {"name": "smi_add_subject_phone", "arguments": {"phone": "texte", "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_relationship≈ 393 tokens

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

  Paramètres, retour & exemple (5)

  Paramètres

  • lastName · string · requis
    The related person's last name.
  • firstName · string · requis
    The related person's first name.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.
  • middleName · string · optionnel
    The related person's middle name, if known.
  • relationshipId · ? · requis
    The relationship type id from smi_list_relationships (e.g. spouse, parent, associate).

  Exemple d'appel

  {"name": "smi_add_subject_relationship", "arguments": {"lastName": "texte", "firstName": "texte", "subjectId": "texte", "relationshipId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_relationship_url≈ 297 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    A url tied to the related person's own profile or accounts.
  • subjectRelationshipId · ? · requis
    The id smi_add_subject_relationship returned for this relationship record.

  Exemple d'appel

  {"name": "smi_add_subject_relationship_url", "arguments": {"url": "texte", "subjectRelationshipId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectRelationshipId": "texte"}}

• smi_add_subject_surname≈ 260 tokens

  Attaches a surname to an SMI subject.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    An additional or prior surname for the subject, such as a maiden name.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.

  Exemple d'appel

  {"name": "smi_add_subject_surname", "arguments": {"name": "texte", "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_add_subject_url≈ 252 tokens

  Attaches a url to an SMI subject.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    A url tied to the subject's own profile or accounts.
  • subjectId · ? · requis
    The subject's id, from a prior smi_get_subject or subject-enrichment call.

  Exemple d'appel

  {"name": "smi_add_subject_url", "arguments": {"url": "texte", "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"recordId": "texte", "subjectId": "texte"}}

• smi_analyze≈ 1036 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • notes · string · requis
    Free-text case notes to score against the 5-signal gap-analysis rubric.
  • weights · object · optionnel
    Optional override of all 5 signal weights; normalized to sum 100.
  • thresholds · object · optionnel
    Optional override of the RECOMMEND/REVIEW verdict thresholds.

  Exemple d'appel

  {"name": "smi_analyze", "arguments": {"notes": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "signals": [], "verdict": "RECOMMEND", "orderData": {}, "confidence": "HIGH", "signalsDetected": [], "suggestedProduct": "DEEP_REPORT", "signalsNotDetected": []}}

• smi_check_order_complete≈ 464 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • orderId · string · requis
    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: RB = Research Bundle, DR = Deep Report (both orderType "deep_report"), EX = Export (orderType "export").
  • orderType · string · requis · deep_report | export
    Whether the order is a deep report or an export

  Exemple d'appel

  {"name": "smi_check_order_complete", "arguments": {"orderId": "texte", "orderType": "deep_report"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ready": true, "state": "ready", "status": "texte", "orderId": "texte", "terminal": true, "orderType": "deep_report"}}

• smi_confirm_upload≈ 258 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • version · string · requis
  • fileName · string · requis
  • deepReportId · integer · requis

  Exemple d'appel

  {"name": "smi_confirm_upload", "arguments": {"version": "texte", "fileName": "texte", "deepReportId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": 1, "fileName": "texte", "deepReportId": 1}}

• smi_create_deep_report≈ 5080 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • orders · array · requis
  • projectId · ? · optionnel
    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.

  Exemple d'appel

  {"name": "smi_create_deep_report", "arguments": {"orders": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"warning": "texte", "draftIds": [], "requestedCount": 1}}

• smi_create_export≈ 1004 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • orders · array · requis
  • projectId · ? · optionnel
    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.

  Exemple d'appel

  {"name": "smi_create_export", "arguments": {"orders": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"warning": "texte", "draftIds": [], "requestedCount": 1}}

• smi_get_cowork_instructions≈ 166 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "smi_get_cowork_instructions", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• smi_get_deep_report≈ 420 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
    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 are both deep-report records, so RB and DR ids route here; EX ids belong to the export tools.
  • include · array · optionnel
    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, while subject, releases and uploads all come back. Call smi_get_report_findings with reportIds to read findings.

  Exemple d'appel

  {"name": "smi_get_deep_report", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"record": {}}}

• smi_get_deep_report_releases≈ 402 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)
  • deepReportId · integer · requis
    Id of the deep report whose releases should be listed

  Exemple d'appel

  {"name": "smi_get_deep_report_releases", "arguments": {"deepReportId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_get_export≈ 298 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • id · string · requis
    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 are both deep-report records, so RB and DR ids route here; EX ids belong to the export tools.
  • include · array · optionnel
    Related resources to include: releases

  Exemple d'appel

  {"name": "smi_get_export", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"record": {}}}

• smi_get_export_releases≈ 350 tokens

  Lists releases for a given SMI export, with pagination.

  Paramètres, retour & exemple (3)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)
  • exportId · integer · requis
    Id of the export whose releases should be listed

  Exemple d'appel

  {"name": "smi_get_export_releases", "arguments": {"exportId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_get_report_findings≈ 904 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)
  • reportIds · array · optionnel
    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.
  • isConfirmed · boolean · optionnel
    Only include confirmed findings
  • platformIds · array · optionnel
    Only include findings for these platforms. Accepts a platform name (Facebook, TikTok) or its numeric id; names are matched case-insensitively.
  • isScopeRelated · boolean · optionnel
    Only include findings marked scope-related

  Exemple d'appel

  {"name": "smi_get_report_findings", "arguments": {"page": 1, "take": 1, "reportIds": [], "isConfirmed": true, "platformIds": [], "isScopeRelated": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_get_subject≈ 269 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • deepReportId · string · requis
    Deep report id whose subject to read (no standalone GET /subjects/{id} exists upstream)

  Exemple d'appel

  {"name": "smi_get_subject", "arguments": {"deepReportId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"subject": {}, "deepReportId": "texte"}}

• smi_list_deep_reports≈ 728 tokens

  Lists SMI deep reports with pagination and optional filtering.

  Paramètres, retour & exemple (9)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)
  • status · string · optionnel
    Only include records with this status
  • include · array · optionnel
    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, while subject, releases and uploads all come back. Call smi_get_report_findings with reportIds to read findings.
  • statusEndDate · string · optionnel
    Only include records with a status on or before this date (YYYY-MM-DD)
  • statusStartDate · string · optionnel
    Only include records with a status on or after this date (YYYY-MM-DD)
  • subjectLastName · string · optionnel
    Only include records for a subject with this last name
  • subjectFirstName · string · optionnel
    Only include records for a subject with this first name
  • subjectCompanyName · string · optionnel
    Only include records for a subject with this company name

  Exemple d'appel

  {"name": "smi_list_deep_reports", "arguments": {"page": 1, "take": 1, "status": "texte", "include": [], "statusEndDate": "texte", "statusStartDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_list_exports≈ 573 tokens

  Lists SMI exports with pagination and optional filtering.

  Paramètres, retour & exemple (7)

  Paramètres

  • url · string · optionnel
    Only include records with this url
  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)
  • status · string · optionnel
    Only include records with this status
  • include · array · optionnel
    Related resources to include: releases
  • statusEndDate · string · optionnel
    Only include records with a status on or before this date (YYYY-MM-DD)
  • statusStartDate · string · optionnel
    Only include records with a status on or after this date (YYYY-MM-DD)

  Exemple d'appel

  {"name": "smi_list_exports", "arguments": {"url": "texte", "page": 1, "take": 1, "status": "texte", "include": [], "statusEndDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_list_platforms≈ 300 tokens

  Lists the SMI reference set of platforms.

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)

  Exemple d'appel

  {"name": "smi_list_platforms", "arguments": {"page": 1, "take": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_list_products≈ 299 tokens

  Lists the SMI reference set of products.

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)

  Exemple d'appel

  {"name": "smi_list_products", "arguments": {"page": 1, "take": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_list_projects≈ 298 tokens

  Lists SMI projects with pagination.

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)

  Exemple d'appel

  {"name": "smi_list_projects", "arguments": {"page": 1, "take": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_list_relationships≈ 303 tokens

  Lists the SMI reference set of relationships.

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)

  Exemple d'appel

  {"name": "smi_list_relationships", "arguments": {"page": 1, "take": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_list_statuses≈ 299 tokens

  Lists the SMI reference set of statuses.

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer · optionnel
    1-based page number to return
  • take · integer · optionnel
    Number of items per page (1-100)

  Exemple d'appel

  {"name": "smi_list_statuses", "arguments": {"page": 1, "take": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": 1, "take": 1, "items": [], "total": 1, "hasMore": true}}

• smi_request_upload_url≈ 320 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • fileName · string · requis
  • deepReportId · integer · requis

  Exemple d'appel

  {"name": "smi_request_upload_url", "arguments": {"fileName": "texte", "deepReportId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"fileName": "texte", "signedUrl": "texte", "uploadMethod": "texte", "versionHeader": "texte"}}

• smi_submit_deep_reports≈ 297 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • ids · array · requis

  Exemple d'appel

  {"name": "smi_submit_deep_reports", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "accepted": [], "rejected": [], "outcomesEnumerated": true}}

• smi_submit_exports≈ 294 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • ids · array · requis

  Exemple d'appel

  {"name": "smi_submit_exports", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "accepted": [], "rejected": [], "outcomesEnumerated": true}}

• smi_update_subject≈ 681 tokens

  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.

  Paramètres, retour & exemple (9)

  Paramètres

  • type · string · requis · PERSON | COMPANY
    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 organization.
  • gender · string · optionnel
    The subject's updated gender (PERSON subjects only).
  • birthDay · integer · optionnel
    The subject's updated day of birth. Treated as the day the company was founded, for a COMPANY subject.
  • lastName · string · optionnel
    The subject's updated last name, required whenever type is PERSON.
  • birthYear · integer · optionnel
    The subject's updated birth year. Treated as the year the company was founded, for a COMPANY subject.
  • firstName · string · optionnel
    The subject's updated first name, required whenever type is PERSON.
  • subjectId · ? · requis
    The SMI subject id to update, from a prior smi_get_subject call.
  • birthMonth · integer · optionnel
    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.
  • companyName · string · optionnel
    The subject's updated company name, required whenever type is COMPANY.

  Exemple d'appel

  {"name": "smi_update_subject", "arguments": {"type": "PERSON", "subjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"subjectId": "texte", "updatedFields": []}}

• submit_contact_request≈ 238 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • email · string · requis
    Prospect email address; our team will reach out here.
  • lastName · string · requis
    Prospect last name.
  • firstName · string · requis
    Prospect first name.
  • organization · string · requis
    Prospect's organization name.

  Exemple d'appel

  {"name": "submit_contact_request", "arguments": {"email": "texte", "lastName": "texte", "firstName": "texte", "organization": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_access≈ 104 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "verify_access", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.smiaware.com/mcp