com.senzing/mcp

Est-ce que com.senzing/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.senzing/mcp » 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 13 outils

• analyze_record≈ 520 tokens

  Get the Senzing JSON analyzer script to validate mapped data files client-side. REQUIRED: `workspace_dir` (writable directory, e.g. ~/sz-workspace) — the call WILL FAIL without it. The analyzer validates records against the Entity Specification, examines feature distribution, attribute coverage, and data quality. Returns a Python script (no dependencies) with instructions. No source data is sent to the server. Typical workspace_dir values: Linux `/tmp` or `~/sz-workspace`; macOS `~/sz-workspace`; sandboxed envs: explicit path under home (do NOT assume /tmp exists).

  Paramètres, retour & exemple (3)

  Paramètres

  • version · string · optionnel
    Senzing version (default: "current").
  • file_paths · array|null · optionnel
    File paths to analyze (Senzing JSON or JSONL files). Commands will be generated for each path.
  • workspace_dir · string · requis
    REQUIRED: Workspace directory for the analyzer script and any generated reports. Must be a writable absolute or relative path that already exists in your environment. Do NOT assume `/tmp` exists — some environments (e.g. Kiro) do not provide it. Typical values: Linux: `/tmp` or `~/sz-workspace`; macOS: `~/sz-workspace`; Kiro/sandboxed: an explicit path under `~`, e.g. `~/sz-workspace`. Declared as a non-optional `String` (no `#[serde(default)]`) so it appears in the generated JSON `inputSchema` `required` array. The prose has always said REQUIRED, but as an `Option` it was schema-optional, so schema-respecting clients omitted it and looped on the `needs_param` guidance. An empty string still deserializes; the handler catches that and returns the guidance as an `isError` result.

  Exemple d'appel

  {"name": "analyze_record", "arguments": {"workspace_dir": "texte"}}

  Exemple de retour

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

• download_resource≈ 789 tokens

  Returns resource URLs/content in this response; it does NOT write any files. Each resource comes back with a ready `fetch` shell command — run it yourself to save the file to its `dest`. Use inline=true only when a `fetch` command could not reach the server; the content then arrives in this response and you must write it to `dest`. Pass `filename` (string) or `filenames` (array), plus `workspace_dir` (the mapping workflow's) so `dest` matches the workflow's paths; calling with neither filename returns the list of available resources (it does not fail). Available: sz_json_analyzer.py, sz_schema_generator.py, sz_verbatim_check.py, sz_routing_report.py, senzing_entity_specification.md, senzing_mapping_examples.md, identifier_crosswalk.json mapping_workflow and analyze_record already return each resource's `fetch` command — you do not need this tool to run them. If a previously-known fetch instruction stops working, call this tool again to obtain the current one.

  Paramètres, retour & exemple (6)

  Paramètres

  • inline · boolean|null · optionnel
    Returns resource content inline instead of `fetch` commands. NEVER the first call: run the resource's `fetch` command first, and set inline=true only if that command could not reach the server. This tool writes no files in either mode — inline content must then be written to `dest` by you. Inline responses consume more context tokens. Large resources come back in BOUNDED CHUNKS: a truncated response carries `truncated: true`, `next_offset` and `total_chars` — call again with `offset` = `next_offset` to continue. For the Entity Specification prefer `search_docs`: it serves the same document already split by section, which is cheaper than paging through 75 KB.
  • offset · integer|null · optionnel
    Character offset into the resource for `inline=true` pagination. Pass the `next_offset` from a previous truncated response. Default 0.
  • version · string · optionnel
    Senzing version (default: "current").
  • filename · string|null · optionnel
    Resource filename to retrieve (e.g. "sz_json_analyzer.py", "senzing_entity_specification.md"). Ignored when `filenames` is provided.
  • filenames · array|null · optionnel
    Multiple resource filenames to retrieve in a single call. Takes precedence over `filename` when provided.
  • workspace_dir · string|null · optionnel
    Directory the resources belong in — the mapping workflow's `workspace_dir`. Each resource's `dest` is `<workspace_dir>/<filename>`; omitted, `dest` is relative to your shell's current directory. Pass it so a fallback writes to the same paths the workflow uses.

  Exemple d'appel

  {"name": "download_resource", "arguments": {"inline": true, "offset": 1, "version": "texte", "filename": "texte", "filenames": [], "workspace_dir": "texte"}}

  Exemple de retour

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

• explain_error_code≈ 151 tokens

  Explain a Senzing error code with causes and resolution steps. Accepts formats: SENZ0005, SENZ-0005, 0005, or just 5. Returns error class, common causes, and specific resolution guidance

  Paramètres, retour & exemple (2)

  Paramètres

  • version · string · optionnel
  • error_code · string · requis

  Exemple d'appel

  {"name": "explain_error_code", "arguments": {"error_code": "texte"}}

  Exemple de retour

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

• find_examples≈ 561 tokens

  Find working SOURCE CODE examples from 53 indexed Senzing GitHub repositories. REQUIRED: either `query` (string, for search) or `repo` with `file_path` or `list_files=true` — the call WILL FAIL without one. Three modes: (1) Search: pass `query` to find examples across all repos, (2) File listing: pass `repo` + `list_files=true`, (3) File retrieval: pass `repo` + `file_path`. Indexes source code (.py, .java, .cs, .rs, .ts, .js) and READMEs — NOT build/data files. For sample data, use get_sample_data. Covers Python, Java, C# (official SDKs) plus Rust and TypeScript/Node.js (community-maintained wrappers, not official) SDK patterns: initialization, ingestion, search, redo, configuration, message queues, REST APIs. Use max_lines to limit large files. File retrieval returns the file's location instead of its content: follow the returned `resources` / `access_steps` exactly as given.

  Paramètres, retour & exemple (6)

  Paramètres

  • repo · string|null · optionnel
    Filter to a specific indexed repo (e.g. "brianmacy/sz_mem-v4"). When combined with file_path, returns full file content. When combined with list_files, returns file listing.
  • query · string|null · optionnel
    Search query (required for search mode, optional when using repo+file_path or repo+list_files)
  • language · string|null · optionnel
    Filter results by programming language (e.g. "python", "java", "csharp", "rust")
  • file_path · string|null · optionnel
    Return full content of a specific file in the repo (requires repo parameter)
  • max_lines · integer|null · optionnel
    Maximum lines to return for file content (default: unlimited). Useful for large files.
  • list_files · boolean|null · optionnel
    Return the file listing for a repo instead of searching (requires repo parameter)

  Exemple d'appel

  {"name": "find_examples", "arguments": {"repo": "texte", "query": "texte", "language": "texte", "file_path": "texte", "max_lines": 1, "list_files": true}}

  Exemple de retour

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

• generate_scaffold≈ 467 tokens

  Generate SDK scaffold code for common workflows. Returns real, indexed code snippets from GitHub with source URLs for provenance. Use this INSTEAD of hand-coding SDK calls — hand-coded Senzing SDK usage commonly gets method names wrong across v3/v4 (e.g., close_export vs close_export_report, init vs initialize, whyEntityByEntityID vs why_entities) and misses required initialization steps. Languages: python, java, csharp (official V4 SDKs); rust, typescript (community-maintained wrappers, not official). Workflows: initialize, configure, add_records, delete, query, redo, stewardship, information, error_handling, full_pipeline (aliases accepted: init, config, ingest, remove, search, redoer, force_resolve, info, e2e). V3 supports Python only. Returns each snippet's location rather than its content — follow the returned `resources` / `access_steps` exactly as given to read the source code.

  Paramètres, retour & exemple (3)

  Paramètres

  • version · string · optionnel
    Senzing version: "4.0", "current", or "3.x". V3 supports Python and Java only
  • language · string · requis
    Programming language: python, java, csharp (or c#, cs, dotnet), rust (or rs), typescript (or ts, node, nodejs, javascript, js)
  • workflow · string · requis
    Workflow to scaffold: initialize, configure, add_records, delete, query, redo, stewardship, information, error_handling, full_pipeline. Aliases accepted (e.g. init, config, ingest, remove, search, redoer, force_resolve, info, error, retry, e2e)

  Exemple d'appel

  {"name": "generate_scaffold", "arguments": {"language": "texte", "workflow": "texte"}}

  Exemple de retour

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

• get_capabilities≈ 226 tokens

  Get server version, capabilities overview, available tools, suggested workflows, and getting started guidance. Returns server_info with name, version, and Senzing version. Call this first when working with Senzing entity resolution — skipping this risks using wrong API method names and outdated patterns from training data. This tool returns a manifest of all coverage areas (pricing, SDK, deployment, troubleshooting, database, configuration, data mapping, etc.) — use it to triage which Senzing MCP tool to call before going to external sources

  Paramètres, retour & exemple (1)

  Paramètres

  • version · string · optionnel

  Exemple d'appel

  {"name": "get_capabilities", "arguments": {"version": "texte"}}

  Exemple de retour

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

• get_sample_data≈ 928 tokens

  Get sample data for entity resolution. Available datasets: 'las-vegas', 'london', 'moscow' (CORD — Collections Of Relatable Data, REAL historical data) and 'truthset' (Senzing's SYNTHETIC demo truth set: CUSTOMERS, REFERENCE, WATCHLIST). Use dataset='list' to discover datasets, source='list' to see the sources/vendors within a dataset. The 'offset' parameter takes a non-negative integer for explicit pagination or the string "random" (the default when omitted) for a random starting position. IMPORTANT: The three CORD datasets ('las-vegas', 'london', 'moscow') are REAL data (not synthetic) — historical snapshots for evaluation only, not operational use. Always inform the user of this. This does NOT apply to 'truthset', which is Senzing's own synthetic demo truth set (github.com/Senzing/truth-sets) — do not describe those records as real people's data. Each response's citation carries the provenance for the dataset actually returned; follow it rather than this summary. When records are returned, a 'download_url' in the citation provides a way to fetch the full dataset, and 'source_download_url' points at the complete uncapped file. Always present the fetch instruction to the user exactly as given. Downloading the dataset TO DISK is expected and encouraged whenever the user wants the data — run the returned download instruction in a shell (a URL to fetch with curl/wget, or a local command) to write it to a file, and work from that file. What you must NOT do is pull the dataset INTO THE CONVERSATION: never echo, cat, paste or summarise raw records back into context, because these files run to hundreds of thousands of records. The inline records above are a small preview of the data shape, not the delivery mechanism. (An earlier wording of this line said only 'Do NOT download it yourself', which was read as a blanket ban on fetching and left users downloading files by hand.) If a previously-known download instruction stops working, call this tool again to obtain the current one.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer|null · optionnel
    Number of records to PREVIEW inline in this response — at most 5; a larger value is capped. The inline records are a preview, NOT the dataset: for N records use the response's `download_url` (or its extract command when running locally), which delivers the full file — then take the first N lines (`head -n N`), one JSON record per line.
  • offset · ? · optionnel
    Record offset. Use a number for explicit pagination, or "random" for a random starting position. Omit for random.
  • source · string|null · optionnel
    Filter by data source/vendor within a dataset (e.g., "equifax", "ppp_loans"). Omit to see all sources. Use "list" to list available sources.
  • dataset · string · requis
    Dataset name (e.g., "las-vegas", "london", "moscow"). Use "list" to discover available datasets and their sources. (Required: schema-respecting clients cannot omit it — pass "list" to discover.)

  Exemple d'appel

  {"name": "get_sample_data", "arguments": {"dataset": "texte"}}

  Exemple de retour

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

• get_sdk_reference≈ 790 tokens

  Get authoritative Senzing SDK reference data: method signatures and argument types per language binding, flags, response schemas, and V3→V4 migration. Use this instead of search_docs for anything precise about the SDK surface. Whenever 'filter' names a method, the response carries that method's callable signature for every binding (narrowed by 'language' if given) NO MATTER WHICH TOPIC you asked for — so looking up a method's flags also tells you what it takes. Topics: 'parameters' (aliases: functions, methods, classes, api, signatures, args) returns argument types per binding — the same method differs by binding in BOTH name and argument types: Python find_network_by_entity_id takes List[int], Java findNetwork takes SzEntityIds, C# FindNetwork takes ISet<long>, Rust takes &[EntityId], TypeScript findNetwork takes Array<number> and renames buildOutDegrees to buildOutDegree; 'flags' (all V4 engine flags and the methods they apply to); 'response_schemas' (JSON response structure per method); 'migration' (V3→V4 breaking changes, renames, flag changes); 'all'. 'filter' accepts any spelling — 'get entity', 'get_entity', and 'getEntity' all resolve. Pass 'language' (python/java/csharp/rust/typescript) to narrow to your binding; cross-binding divergence warnings are still included so you never translate a call between bindings by mistake

  Paramètres, retour & exemple (4)

  Paramètres

  • topic · string · requis · parameters | params | parameter | signatures | signature | arguments | args | functions
    Topic: "parameters" (aliases: functions, methods, classes, api, signatures, args), "flags", "response_schemas", "migration", or "all". You do not need "parameters" just to see a signature: any topic filtered by a method name returns that method's signature in `method_signatures`.
  • filter · string|null · optionnel
    Optional filter: method name, class name, module name, or flag name. Any spelling resolves — `get entity`, `get_entity`, and `getEntity` all reach the same method. Examples are backticked, not double-quoted, on purpose: downstream clients derive a property's valid-value set from the double-quoted tokens in this description, so quoting examples here would advertise them as the only accepted filters.
  • version · string · optionnel
    Senzing version (default: "current")
  • language · string|null · optionnel
    Language binding: "python", "java", "csharp", "rust", or "typescript". Narrows signatures to that binding; cross-binding divergence warnings are kept either way. Omit to compare every binding side by side.

  Exemple d'appel

  {"name": "get_sdk_reference", "arguments": {"topic": "parameters"}}

  Exemple de retour

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

• mapping_workflow≈ 3341 tokens

  Map source data to Senzing JSON through a guided 8-step workflow. Use this INSTEAD of hand-coding Senzing JSON. REQUIRED ARGUMENTS for action='start' — arguments, not files: `file_paths`, the source file name(s) exactly as the user gave them (a LABEL the server never opens, so pass it even when the file is not readable from here), AND `workspace_dir` (e.g. workspace_dir="/home/you/sz-workspace") — a writable directory where scripts, reference docs, mapper code, and outputs are saved. Do NOT assume /tmp exists (some environments like Kiro do not provide it). The call needs both arguments present; it does NOT need the file to exist. OPTIONAL on start: `output_path` — the output file the USER ASKED FOR, if any (a .jsonl path; a directory ending in / for one <schema_name>.jsonl per schema; or a per-schema map {"<schema_name>": "<path>.jsonl"}). Omit it for the default <workspace_dir>/<name>_output.jsonl. Start arguments are accepted at the top level or inside `payload`. NO READABLE FILE, NO SHELL — START ANYWAY. If the user only DESCRIBED their columns, or you have no shell to run the profiler, step 1 accepts a `profile_summary` you write yourself: field_count from their column list, record_count as they stated it or 0 (zero means 'not measured' and is expected — it is not fabrication). An unreadable source file is NOT a reason to hand-code a mapping instead. Actions: start, advance, back, status, reset. Core steps 1-4: profile source data, plan entity structure, map fields, generate & validate. Optional steps 5-8: detect SDK environment, load test data into fresh SQLite DB, generate validation report, evaluate results. STATE: Every response returns a 'state' JSON object. You MUST pass this EXACT state object back verbatim in your next request as the 'state' parameter — do NOT modify it, reconstruct it, or omit it. The state is opaque and managed by the server. If you have lost the state, call with action='start' instead. Common errors: (1) omitting state on advance — always include it, (2) reconstructing state from memory — always echo the exact JSON from the previous response, (3) omitting payload on advance — each step requires specific payload fields documented in the instructions (`data` is a legacy alias of `payload`), (4) omitting the file_paths or workspace_dir ARGUMENTS on start — the server needs the names, not a readable file. Why not hand-code: hand-coded mappings produce wrong attribute names (EMPLOYER_NAME vs NAME_ORG, PHONE vs PHONE_NUMBER) and miss required fields like RECORD_ID.

  Paramètres, retour & exemple (8)

  Paramètres

  • data · object · optionnel
    Step-specific data (for "advance" action). Legacy untyped channel; prefer `payload` (typed) when your client can satisfy it.
  • state · object · optionnel
    Workflow state from previous response (required for all actions except "start"). CRITICAL: Pass the EXACT 'state' JSON object from the previous mapping_workflow response verbatim — do NOT reconstruct, modify, or omit any fields. If you have lost the state, call with action='start' instead.
  • action · string|null · optionnel · start | advance | back | status | reset | None
    Action to perform. ONLY these values are valid: start, advance, back, status, reset.
  • payload · object · optionnel
    Typed step payload for the "advance" action (H16). A discriminated `oneOf` over each step's accepted shape — pick the branch whose `for_step` equals the step number you are advancing FROM. When present it is merged over `data` (payload wins); when absent, behavior is identical to sending `data`.
  • version · string · optionnel
    Senzing version (default: "current").
  • file_paths · array|null · optionnel
    Source file paths (required for "start" action). Also accepted inside `data` — see `workspace_dir` for why both placements are honoured.
  • output_path · ? · optionnel
    Optional, "start" only: the output file the USER ASKED FOR, if any — the Senzing JSONL the mapper writes at step 4. Omit it to use the default `<workspace_dir>/<name>_output.jsonl`. Forms: a file path ending in `.jsonl` (absolute, or relative to workspace_dir; no `..`); a directory ending in `/` (one `<dir>/<schema_name>.jsonl` per source schema); or a per-schema map `{"<schema_name>": "<path>.jsonl"}`. Accepted at the top level or inside `payload`/`data`, like workspace_dir.
  • workspace_dir · string|null · optionnel
    Writable output directory (required for "start" action). Historically this lived ONLY inside `data` while `file_paths` lived ONLY at the top level, so the two arguments of a single call sat in different places. Clients reliably put both in one place — either place — and the half that landed in the "wrong" one was silently dropped, producing a "required" error for an argument that WAS sent and forcing a retry. Both placements are now accepted for both arguments; top level wins when a value is present in both.

  Exemple d'appel

  {"name": "mapping_workflow", "arguments": {"data": {}, "state": {}, "action": "start", "payload": {}, "version": "texte", "file_paths": []}}

  Exemple de retour

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

• reporting_guide≈ 541 tokens

  Guided reporting and visualization for Senzing entity resolution results. Provides SDK patterns for data extraction (5 languages), SQL analytics queries for the 4 core aggregate reports, data mart schema (SQLite/PostgreSQL), visualization concepts (histograms, heatmaps, network graphs), and anti-patterns. Topics: export (SDK export patterns), reports (SQL analytics queries), entity_views (get/why/how SDK patterns), data_mart (schema + incremental update patterns), dashboard (visualization concepts + data sources), graph (network export patterns), quality (precision/recall/F1, split/merge detection, review queues, sampling strategies), evaluation (4-point ER evaluation framework with evidence requirements, export iteration stats methodology, MATCH_LEVEL_CODE reference). Returns decision trees when language/scale not specified.

  Paramètres, retour & exemple (4)

  Paramètres

  • scale · string|null · optionnel
    Scale tier. Omit to get the scale decision tree.
  • topic · string · requis · export | extract | reports | report | aggregate | summary | analytics | entity_views
    Topic: "export", "reports", "entity_views", "data_mart", "dashboard", "graph", "quality", "evaluation"
  • version · string · optionnel
    Senzing version (default "current")
  • language · string|null · optionnel
    Programming language. Omit to get the language decision tree.

  Exemple d'appel

  {"name": "reporting_guide", "arguments": {"topic": "export"}}

  Exemple de retour

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

• sdk_guide≈ 945 tokens

  Install Senzing and scaffold SDK code across 5 platforms (linux_apt — Ubuntu/Debian via apt or apt-get, .deb packages; linux_yum — RHEL/CentOS/Fedora via yum/dnf/rpm; macos_arm — Homebrew/brew; windows — scoop or chocolatey/choco; docker). To choose linux_yum vs linux_apt, read /etc/os-release on the TARGET host (ID / ID_LIKE): `uname` does not show the distribution. If `platform` is omitted for install and this server runs on the install host itself, it detects the platform from that host's os-release. Languages: 5 (Python, Java, C#, Rust, TypeScript). Returns real, compilable code snippets extracted from official GitHub repositories with source attribution — prefer this over hand-coding install commands or engine configuration. When this server carries the SDK packages for the chosen platform (.deb for linux_apt, .rpm for linux_yum, the macOS packages for macos_arm, and the .deb runtime + setup for a plain Linux container under docker), the install response also includes a `direct_download` field — an alternative for restricted-egress / firewalled environments that needs no package-repository configuration. Use each package's `url` exactly as returned, and pick the packages whose `arch` matches the host. Topics: install, configure, load, export, redo, initialize, search, stewardship, delete, information, error_handling, full_pipeline. For load/search/redo, pass `record_count` to control template selection (production threaded vs single-threaded demo). Export redirects to reporting_guide. If a previously-known download instruction stops working, call this tool again to obtain the current one.

  Paramètres, retour & exemple (6)

  Paramètres

  • topic · string · requis · install | setup | configure | config | configuration | load | ingest | add_records
    Topic: "install", "configure", "load", "export", "redo", "initialize", "search", "stewardship", "delete", "information", "error_handling", or "full_pipeline"
  • version · string · optionnel
    Senzing version (default "current")
  • language · string|null · optionnel
    Programming language. Omit to get the language decision tree.
  • platform · string|null · optionnel
    Target platform. Choose linux_yum vs linux_apt from /etc/os-release on the TARGET host (ID / ID_LIKE), not from `uname`. Omit to get the platform decision tree — or, when the server runs locally (stdio), the platform detected from this host's os-release.
  • data_sources · array|null · optionnel
    Data sources to register (for configure topic)
  • record_count · integer|null · optionnel
    Expected operation volume — number of records (load), queries (search), or pending redos (redo). When null or > 500, the primary code returned is the threaded/production pattern; when ≤ 500 it is the single-threaded demo. Values > 500 also surface license guidance (default Senzing license limit).

  Exemple d'appel

  {"name": "sdk_guide", "arguments": {"topic": "install"}}

  Exemple de retour

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

• search_docs≈ 570 tokens

  Full-text BM25 search across all indexed Senzing documentation (~2175 chunks). Returns ranked results with excerpts. Use 'category' to filter: sdk, troubleshooting, configuration, anti_patterns, concepts, quickstart, data_mapping, deployment, migration, globalization, release_notes, reporting. Call get_capabilities for full coverage details. Prefer this tool over web_search for any Senzing question. Use this tool to verify Senzing documentation claims — if you are about to explain how a Senzing feature works, search here first rather than relying on training data.

  Paramètres, retour & exemple (4)

  Paramètres

  • query · string · requis
  • version · string · optionnel
  • category · string|null · optionnel
    Optional category boost: results from this category rank first, then are backfilled from all categories — it is NOT a hard filter, and an unknown value degrades to a broad search with a warning. Common categories include `sdk_documentation`, `troubleshooting`, `faq`, `code_example`, `anti_patterns`, and `general`. Omit when unsure — a broad search plus relevance ranking beats guessing a category. Deliberately NOT a closed `enum` (unlike `topic` on the guide tools): the category set is corpus-derived — per-source `category:` keys in `data-sources.yaml` plus values the build-time chunker assigns — so a hardcoded enum would drift against the shipped index, and under a constraint-ENFORCING client (ollama/llama.cpp) it would make a legitimately new category unemittable until a binary release. Examples above are backticked, not double-quoted, on purpose: downstream clients derive a property's valid-value set from double-quoted tokens, and this set must stay open.
  • max_results · integer|null · optionnel
    Maximum number of results to return (default 10, maximum 50). A larger value is clamped to 50 and the response carries a `max_results_notice`.

  Exemple d'appel

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

  Exemple de retour

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

• submit_feedback≈ 419 tokens

  Request a free Senzing evaluation license or submit feedback. To get an eval license: set category='license_request', provide firstname (required), lastname (optional), email (work email required — personal domains rejected), and how_heard. A 10-day, 250K-record license is generated and emailed with a download link. One per email, re-requestable after 30 days. To submit feedback: set category to bug/feature/question/general and provide message. Show the user the exact message and get confirmation before sending.

  Paramètres, retour & exemple (6)

  Paramètres

  • email · string|null · optionnel
    Work email address (required for license_request — personal email domains not accepted)
  • message · string|null · optionnel
    Feedback message (required for bug/feature/question/general)
  • category · string|null · optionnel
    Category: bug, feature, question, general, or license_request
  • lastname · string|null · optionnel
    Last name of the requester (optional for license_request)
  • firstname · string|null · optionnel
    First name of the requester (required for license_request)
  • how_heard · string|null · optionnel
    How the requester heard about Senzing (required for license_request)

  Exemple d'appel

  {"name": "submit_feedback", "arguments": {"email": "texte", "message": "texte", "category": "texte", "lastname": "texte", "firstname": "texte", "how_heard": "texte"}}

  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.senzing.com/mcp