Servidor MCP de SMI Aware

• Nombre en el registrocom.smiaware.mcp/smi-aware-assistantverificado en el registro MCP

El nombre en el registro está bajo smiaware.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-18
• Herramientas40
• El servidor se llamamcp-server
• Versión del servidor0.1.1
• Versión del protocolo2025-06-18

El 2026-10-18 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 235 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 3 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 3 hasta ahora
• Respondiómidiendo3 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta242 ms
• Espacio en el contexto del agente≈ 13.927 tokenslas definiciones de todas sus herramientas (40), que el agente lleva en cada turno
• Definiciones de herramientasA · 98 de 100
• Resultados tipados36 de 40 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 6 de 40

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• onboarding_next_step

  Pre-connection onboarding helper, callable before any SMI token is set. With no input, returns the fork question "Do you already have an SMI token?" — call again with hasToken: "yes" for connect guidance (then verify_access), or hasToken…

• verify_access

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

• smi_get_cowork_instructions

  Returns a consolidated, copy-paste-ready Markdown system prompt of SMI Aware house rules and a when-to-call-which-tool routing guide, plus exact paste-in locations for Claude Projects/Cowork/Desktop, Cursor, and other clients, so the…

• submit_contact_request

  Submits a prospect contact request — first name, last name, email, and organization — to SMI so the sales team can follow up. For prospects who do not yet have an SMI Aware token.

• smi_list_deep_reports

  Lists SMI deep reports with pagination and optional filtering.

• smi_get_deep_report

  Fetches a single SMI deep report by id. Research Bundles are deep-report products, so use this tool for a Research Bundle id too rather than constructing a research_bundle: reference for the generic fetch tool. Accepts product-prefixed…

• smi_create_deep_report

  Creates one or more SMI deep report drafts from subject orders. Returns the draft ids for review before submission. All orders in one call are filed under a single project; call once per project.

• smi_submit_deep_reports

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

• smi_request_upload_url

  Requests a presigned URL for uploading a large deep-report reference file (csv, doc, docx, gif, jpg, jpeg, pdf, png, txt, webp, xls, xlsx) directly to storage. This server never proxies file bytes: the caller must PUT the file to the…

• smi_confirm_upload

  Confirms a file already PUT to a presigned URL returned by smi_request_upload_url and persists the deep report upload record. Requires the version (the x-amz-version-id response header captured during the PUT).

• smi_list_exports

  Lists SMI exports with pagination and optional filtering.

• smi_get_export

  Fetches a single SMI export by id. Accepts product-prefixed ids: EX-30001 resolves here, while RB and DR ids belong to smi_get_deep_report.

• smi_create_export

  Creates one or more SMI export drafts from profile-url orders. Returns the draft ids for review before submission. All orders in one call are filed under a single project; call once per project.

• smi_submit_exports

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

• smi_list_projects

  Lists SMI projects with pagination.

• smi_list_products

  Lists the SMI reference set of products.

• smi_list_platforms

  Lists the SMI reference set of platforms.

• smi_list_statuses

  Lists the SMI reference set of statuses.

• smi_list_relationships

  Lists the SMI reference set of relationships.

• smi_get_report_findings

  Lists SMI release findings with pagination and optional filtering by report, platform, scope, and confirmation status. Report filters accept the displayed identifier (RB-11751, DR-402) or a bare numeric id, and platform filters accept a…

• smi_get_deep_report_releases

  Lists releases for a given SMI deep report, with pagination. Each release links its downloadable deliverable files (report PDF, CSV, JSON) and the findings screenshot archive when available — use this tool to fetch the generated report PDF.

• smi_get_export_releases

  Lists releases for a given SMI export, with pagination.

• smi_check_order_complete

  Checks the status of a deep report or export record (by its record id, e.g. from smi_create_deep_report draftIds). Returns state = ready | in_progress | draft | failed | unknown and a terminal flag. Poll with bounded attempts and backoff…

• search

  Open-ended discovery across SMI deep reports, research bundles, and exports when you do not already have a record id — finds candidates by subject name, url, or keyword and returns typed references to pass to fetch. If you already have a…

• fetch

  Fetches the full SMI record for a typed reference ("<type>:<id>") that search returned. Pass only an id that appeared in a search result; do not construct one. If you already have a plain SMI record id, use smi_get_deep_report or…

• smi_analyze

  Scores free-text case notes against 5 weighted gap-analysis signals (no prior SMI order, high-relevance case type, known online presence, date of loss, social media mentioned) and returns a RECOMMEND/REVIEW/NO ACTION verdict, a confidence…

• smi_add_subject_address

  Attaches a postal address to an SMI subject.

• smi_add_subject_phone

  Attaches a phone number to an SMI subject.

• smi_add_subject_email

  Attaches an email address to an SMI subject.

• smi_add_subject_alias

  Attaches an alias to an SMI subject.

• smi_add_subject_surname

  Attaches a surname to an SMI subject.

• smi_add_subject_url

  Attaches a url to an SMI subject.

• smi_add_subject_employer

  Attaches an employer to an SMI subject.

• smi_add_subject_employee

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

• smi_add_subject_employee_url

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

• smi_add_subject_education

  Attaches an educational institution to an SMI subject.

• smi_add_subject_relationship

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

• smi_add_subject_relationship_url

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

• smi_update_subject

  Partially updates an SMI subject via PATCH /subjects/:id. type (PERSON or COMPANY) is required on every call — the SMI backend requires it as a discriminator on every subject PATCH. Editable fields match the API contract…

• smi_get_subject

  Reads a subject's full profile out of a deep report (no standalone GET /subjects/{id} exists upstream, so the input is a deepReportId, not a subject id). Returns the subject as structured JSON — any atomic field (e.g. date of birth via…