Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Algenta MCP Server

PYPI · ALGENTA-MCP · 2 COMPONENTS

Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.

0 this week 84 Trust /100

Last scanned (12 hours ago)

Scores higher than 87% of PyPI servers

Category AI and Machine Learning

Recent critical change

GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 37 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 21251 tokens (~151/item across 140 items; 140 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
Tool Safety94
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 12 of 16 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query_data" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 140 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Provenance: unverified → fail ▼ security
    • Security disclosure: unverified → pass ▲ functional
  • 3 Nov 26 0
    • Provenance: fail → unverified ▼ security
    • Security disclosure: pass → unverified ▼ functional
  • 1 Nov 26 +1
    • Provenance: unverified → fail ▼ security
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → pass ▲ functional
  • 31 Oct 26 −1
    • Provenance: fail → unverified ▼ security
    • Security disclosure: pass → unverified ▼ functional
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Provenance: unverified → fail ▼ security
  • 26 Oct 26 0
    • Provenance: fail → unverified ▼ security
  • 24 Oct 26 0
    • Provenance: unverified → fail ▼ security
  • 23 Oct 26 0
    • Provenance: fail → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/algenta-mcp@1.0.31

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 37 packages
Packages resolved 37
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 140 exposed · ~21,251 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
product_optimize ~250

Estimate the best value for each decision variable given a plain-English objective, and return the per-variable optima. Every variable is sampled uniformly over its [min, max] range; an objective containing 'maximize' favors each variable's max, anything else favors the min, and the returned optimum blends that endpoint with the range midpoint. Use product_decision when you want a proceed/pause/reject recommendation instead of raw optima. Synchronous deterministic compute; nothing is persisted. Returns optimal_values, objective_value, improvement_vs_midpoint (percent), constraints_satisfied, and iterations_run.

NameTypeReqDescription
constraintsarray–Business constraints the answer must respect.
enginestring–Simulation engine; auto (default) selects one, lhs is recommended for optimization. Options: lhs, monte_carlo, qmc_sobol.
iterationsinteger–Search iterations, 100-100000; defaults to 1000.
objectivestringyesWhat to optimize, e.g. 'maximize profit' or 'minimize cost'; the wording sets the search direction.
variablesarrayyesVariables as {name, min, max, unit?} objects with their allowed ranges.

No output schema declared.

No examples provided.

product_retrieve ~218

Rank caller-supplied documents against a search query and return the top matches with snippets. Scoring is deterministic lexical word-overlap between query and document plus a bonus when the query prefix appears in the document; results sort by relevance_score with rank starting at 1. Provide documents or a collection_id - a call with neither fails with missing_source. Use query_data for analytics over connected datasets instead. Read-only; nothing is stored. Returns results (rank, document_id, content excerpt, relevance_score, snippet) and total_searched.

NameTypeReqDescription
collection_idstring–ID of a connected data source to search.
documentsarray–Inline documents as {id?, content, metadata?} objects; the set that actually gets ranked.
querystringyesWhat you are looking for (min 3 characters).
rerankboolean–Accepted for compatibility; ranking is always the deterministic lexical score.
top_kinteger–Number of results to return, 1-50; defaults to 5.

No output schema declared.

No examples provided.

query_agent_run_checkpoints ~228

Search persisted checkpoints across all of the organization's agent runs, paginated (defaults page 1, limit 25). Filter by run_id or checkpoint_id to pinpoint one, or by status, request_hash, policy_snapshot_id, or schema_snapshot_id to audit lineage. Use get_agent_run_checkpoints when you already know the run_id and want its full checkpoint list. Read-only. Returns data, total, page, limit, and pages.

NameTypeReqDescription
checkpoint_idstring–Fetch exactly this checkpoint.
limitinteger–Checkpoints per page, up to 200; defaults to 25.
pageinteger–1-based page number; defaults to 1.
policy_snapshot_idstring–Keep only checkpoints under this execution-policy snapshot.
request_hashstring–Keep only checkpoints of runs with this request hash.
run_idstring–Keep only checkpoints of this run.
schema_snapshot_idstring–Keep only checkpoints under this schema snapshot.
statusstring–Keep only checkpoints of runs in this status.

No output schema declared.

No examples provided.

query_agent_run_mission_events ~236

Search canonical mission-event records across all of the organization's agent runs, paginated (defaults page 1, limit 25) and newest first. Filter by run_id or event_type to pinpoint, or by status, request_hash, policy_snapshot_id, or schema_snapshot_id for lineage audits. Use get_agent_run_mission_events when you already know the run_id. Read-only. Returns data, total, page, limit, and pages.

NameTypeReqDescription
event_typestring–Keep only events of this type, e.g. run_completed.
limitinteger–Events per page, up to 200; defaults to 25.
pageinteger–1-based page number; defaults to 1.
policy_snapshot_idstring–Keep only events under this execution-policy snapshot.
request_hashstring–Keep only events of runs with this request hash.
run_idstring–Keep only events of this run.
schema_snapshot_idstring–Keep only events under this schema snapshot.
statusstring–Keep only events of runs in this status.

No output schema declared.

No examples provided.

query_agent_run_telemetry ~247

Search runtime telemetry batches across all of the organization's agent runs, paginated (defaults page 1, limit 25). Filter by run_id, telemetry_kind, or module_name to pinpoint, or by status, request_hash, policy_snapshot_id, or schema_snapshot_id for lineage audits. Use get_agent_run_telemetry when you already know the run_id. Read-only. Returns data, total, page, limit, and pages.

NameTypeReqDescription
limitinteger–Batches per page, up to 200; defaults to 25.
module_namestring–Keep only telemetry batches from this runtime module.
pageinteger–1-based page number; defaults to 1.
policy_snapshot_idstring–Keep only telemetry under this execution-policy snapshot.
request_hashstring–Keep only telemetry of runs with this request hash.
run_idstring–Keep only telemetry of this run.
schema_snapshot_idstring–Keep only telemetry under this schema snapshot.
statusstring–Keep only telemetry of runs in this status.
telemetry_kindstring–Keep only telemetry batches of this kind.

No output schema declared.

No examples provided.

query_batch ~129

Execute several governed exact queries in one API call. Use this for multi-metric prompts after choosing a dataset with list_data and get_data_summary. Each item reuses the same structured query contract as query_data; defaults may provide shared dataset_id, filter, limit, and order. Read-only against the engine; executes under the active API key with no separate per-route rate limit. Returns request_id and a results array with each item's key, data envelope, metadata, or error.

NameTypeReqDescription
defaultsobject–Optional shared exact-query fields applied to each item before execution.
queriesarrayyes–

No output schema declared.

No examples provided.

query_data ~390

Execute a structured query against connected data sources. Convert the user's question to a structured intent and call this tool — do NOT try to write SQL or parse column names yourself. The engine resolves column meaning from mathematical relationships and statistical structure only. It works on any dataset without configuration. The governed filter shape is a record-predicate contract over normalized rows, not a SQL predicate language, so it also applies to Redis and other non-SQL sources. Structural roles (use in metric.role): - derived_measure: the main financial/operational aggregate (revenue, spend, value) - base_measure: counts, quantities, discrete amounts - unit_measure: per-unit prices, rates - ratio: percentages, margins, fill rates (0-1 range) - metric: let the engine pick the best numeric column If clarification_required is true, or if confidence < 0.85, check the candidates list and ask the user to clarify. Never fabricate column names or SQL. Read-only against the engine; executes under the active API key with no separate per-route rate limit. Returns the query envelope: result, result_type, row_count, confidence, resolved_column, decision_path, and plan, with candidates and clarification_required set when the engine cannot resolve deterministically.

NameTypeReqDescription
aggregationstring–How to aggregate the metric column.
dataset_idstring–Preferred path. dataset_id returned by connect_data or list_data.
filterobject––
group_byarray–Dimension words from the user's question (e.g. ['customer', 'region']). The engine finds the best matching column.
limitinteger–Top-N limit. Use for 'top 5 customers' type questions.
metricobject–What to measure.
orderstring––
sourcesarray–Data sources to query. Usually omitted when dataset_id is provided.

No output schema declared.

No examples provided.

query_repository_graph ~300

Walk the dependency graph of one persisted repository snapshot from optional file_path/symbol_name seeds and return impacted files and symbols with change-risk scores. Seed scope comes from snapshot_id or a triage workspace_evidence_bundle_ref — one of the two is required. direction inbound follows dependents, outbound follows dependencies, both (default) walks both. Use this before simulate_repository or apply_repository to size the blast radius of a change. Read-only against the repository; persists a lookup artifact. Returns seed files/symbols, direct dependencies and dependents, impacted files/symbols, graph nodes and edges, and top_change_risk_files.

NameTypeReqDescription
directionstring–Edge direction to walk: inbound = dependents, outbound = dependencies; defaults to both.
file_pathstring–Optional seed file to walk the graph from.
max_depthinteger–Traversal depth from the seeds, 1-6; defaults to 2.
max_nodesinteger–Graph node cap, 1-1024; defaults to 128.
repository_idstringyesSaved repository connector id from list_connectors.
snapshot_idstring–Snapshot id from create_repository_snapshot; required unless workspace_evidence_bundle_ref is given.
symbol_namestring–Optional seed symbol to walk the graph from.
workspace_evidence_bundle_refstring–Triage bundle ref; alternative seed scope to snapshot_id.

No output schema declared.

No examples provided.

query_sql_report ~116

Execute a constrained read-only SQL rowset query over authorized datasets. Use this only for wide reports that do not fit the governed exact-query surface. SQL must be a single SELECT/WITH statement over the provided dataset aliases. Returns columns, rows, row_count, truncated, request_id, and latency_ms.

NameTypeReqDescription
max_rowsinteger–Optional row cap, up to the API maximum.
sourcesarrayyesAuthorized datasets made available to the SQL report.
sqlstringyesSingle read-only SELECT or WITH statement.

No output schema declared.

No examples provided.

recommend ~128

Compare multiple named actions/options and get a ranked recommendation. Use when you need to choose between two or more alternatives with uncertainty. Synchronous deterministic compute; nothing is persisted and no separate rate limit applies. Returns recommended_action, confidence, rationale, and the ranked action list with expected_value and score per action. Which to use: a ranked pick among 2+ named actions with confidence and rationale; use compare for named scenario deltas, or simulate for one scenario's full envelope.

NameTypeReqDescription
actionsarrayyesList of options to compare (minimum 2)
n_simulationsinteger––

No output schema declared.

No examples provided.

record_outcome ~136

Close the feedback loop: record what actually happened after a decision was made. Sets actual_outcome and computes outcome_delta = actual - expected. Over time this data measures prediction accuracy and reveals systematic biases. Recording updates the persisted decision record in place; repeat calls with the same value converge. Returns decision_id, chosen_action, expected_value, actual_outcome, outcome_delta, and a summary line.

NameTypeReqDescription
actual_outcomenumberyesThe observed real-world outcome value.
decision_idstringyesDecision ID from log_decision or list_decisions.
outcome_notesstring–Optional explanation of what happened and why.

No output schema declared.

No examples provided.

refresh_credits ~159

Issue a compatibility credit batch to a quota-governed managed runtime. This exists for non-Algenta managed plans; Algenta editions are unmetered and do not need execution credits. Requires an API-key identity (api_key_identity_required otherwise) and a registered device_id. credits_used reports consumption since the last refresh and defaults to 0. Returns credits_granted, credits_issued_this_month, monthly_limit (0 means unlimited), monthly_remaining, expires_at, refresh_after, and server_time.

NameTypeReqDescription
billing_periodstringyesBilling month in YYYY-MM form.
credits_usedinteger–Credits consumed since the last refresh; defaults to 0.
device_idstringyesRegistered device id the credits are issued to.

No output schema declared.

No examples provided.

refresh_data ~104

Re-pull a saved dataset from its original database, API, or object-store origin using the stored connection and selection, and return the same envelope as connect_data (status, schema_summary, refreshable). Only datasets created from a live connection can refresh — an inline upload fails with not_refreshable (check the refreshable flag in list_data first), and an unknown dataset_id fails with not_found.

NameTypeReqDescription
dataset_idstringyesDataset ID from connect_data or list_data.

No output schema declared.

No examples provided.

register_source ~211

Advanced tool. Register a data source and get full schema profiling + join detection. Profiles every column (type, cardinality, fill rate, distribution). Detects formula relationships (A×B≈C) within the source. Detects join keys to every already-registered source automatically. After registration the source is queryable by name via query_data. Safe to call multiple times — re-registration is a no-op if data is unchanged. Registration persists the source profile under the active API key's organization. Returns source_id and the profiled schema with columns, roles, formulas, and detected join keys. Which to use: the advanced path — full column profiling, formula detection, and join-key detection across registered sources (browse the results with list_data); use onboard_dataset for semantic training, or connect_data for refreshable live connections.

NameTypeReqDescription
descriptionstring–Optional human description of this source.
sourceobjectyesData source definition. Provide exactly one of: records, csv, json_str, url.

No output schema declared.

No examples provided.

register_trigger ~269

Register a real-time trigger that watches a data source for a threshold condition. The engine evaluates the condition automatically when the source data updates; when the threshold is met it runs the simulation template and POSTs a result summary to webhook_url if set. auto_execute=true additionally dispatches the full DecisionPlan to execution_webhook_url after every successful fire (same payload format as execute_decision, through the execution-policy gates). Examples: 'alert me when monthly revenue drops below $80k', 'simulate expansion if Downtown revenue exceeds $200k'. Use fire_trigger to test it immediately and delete_trigger to remove it. Returns trigger_id, name, status, condition, and created_at.

NameTypeReqDescription
auto_executeboolean–When true, automatically dispatch the decision plan to execution_webhook_url after the trigger fires.
conditionobjectyesThreshold condition to watch.
descriptionstring–Human-readable description of what this trigger monitors.
execution_webhook_urlstring–Optional HTTPS URL to POST the DecisionPlan execution payload to when auto_execute is enabled.
namestringyesHuman-readable trigger name.
simulation_templateobjectyesSimulateRequest-compatible payload to run when trigger fires.
webhook_urlstring–Optional HTTPS URL to POST results to when the trigger fires.

No output schema declared.

No examples provided.

remove_team_member ~132

Remove one member from the caller's organization by user_id (find ids with list_team_members). Requires an admin API key. The member is suspended immediately — their API keys stop authenticating at once — and removing the last active owner is refused (last_owner). Removing is idempotent: repeating the call on an already-removed or never-existing user_id returns success with already_absent: true instead of not_found. Returns removed: true with the removed user_id. Use update_team_member_role to change access without removing the member.

NameTypeReqDescription
user_idstringyesMember's user_id from list_team_members.

No output schema declared.

No examples provided.

rerank ~173

Rank caller-supplied document embeddings against a query embedding with a supported deterministic similarity metric (default embeddings.cosine_similarity), most relevant first. This tool does not embed text — call embeddings first to produce the query and document vectors. Every document embedding must share the query's dimension or the call fails with invalid_embedding_dimensions. Read-only and deterministic. Returns ranked items with rank (starting at 1) and score, plus total_documents and returned_documents counts.

NameTypeReqDescription
documentsarrayyesCandidate documents to rank against the query vector.
modelstring–Similarity model id from list_models; selects the metric.
query_embeddingarrayyesQuery vector every document embedding is scored against.
top_ninteger–Optional cap on how many top-ranked documents are returned; omit to return all documents ranked.

No output schema declared.

No examples provided.

resolve_artifact_bridge ~119

Resolve a Hugging Face artifact path through the Algenta compatibility-ring artifact bridge. Defaults to cache-only lookup and never downloads unless local_files_only=false. Use this only for Hugging Face artifact paths; use list_models for the model catalog. Returns the resolution record: status, backend, artifact_backend, resolved_path, cache_root, revision, auth_env_var_used, and auth_configured.

NameTypeReqDescription
filenamestringyes–
local_files_onlyboolean––
repo_idstringyes–
revisionstring––

No output schema declared.

No examples provided.

responses ~219

Run the unified Algenta response envelope over one string or a list of independent strings, each processed as its own single-turn request. The envelope returns id, model, status, an output array with one {index, content} item per input, and usage with the total token count. The content per item depends on the model: tokenization models (default text.tokenizer) return the input's tokens and token_count; embedding models return a deterministic vector of dimensions length; provider-backed chat models advertised by list_models return generated text. Use chat_completions for an ordered multi-role transcript and embeddings when you specifically need vectors. Stateless and non-destructive: no conversation state is created, continued, or stored by this tool. An unsupported model id fails with model_not_supported.

NameTypeReqDescription
dimensionsinteger–Embedding vector length when the selected model produces embeddings.
input–yesOne string, or a list of independent strings each processed as its own single-turn request.
modelstring–Model id from list_models; selects the output item type.

No output schema declared.

No examples provided.

resume_agent_run ~112

Resume a paused agent run by run_id. A run created with approval_mode=auto executes to completion synchronously and returns completed; a manual-mode run moves to requires_approval and still needs approve_agent_run. Resuming anything that is not paused fails with agent_run_invalid_state; an unknown run_id fails with agent_run_not_found. The transition is audit-logged and checkpointed. Returns the updated run resource.

NameTypeReqDescription
run_idstringyesPaused run id from create_agent_run or list_agent_runs.

No output schema declared.

No examples provided.

retrain_dataset ~136

Re-trigger background semantic training for one dataset and return immediately with status and a confirmation message — the build runs asynchronously, so poll get_dataset_status until model_tier reaches 'schema'. Use after schema changes, alias updates, or to force a fresh model build. epochs (default 80, range 5-500) controls training length. An unknown dataset_id fails with not_found; a dataset whose training backend is unavailable fails with semantic_training_unavailable.

NameTypeReqDescription
dataset_idstringyesDataset ID from onboard_dataset or list_datasets.
epochsinteger–Training epochs, 5-500; defaults to 80.

No output schema declared.

No examples provided.

revoke_api_key ~142

Revoke one API key by id (find ids with list_api_keys). The key stops authenticating and the revocation cannot be undone from this tool. This is a credential revocation, not an idempotent delete: an unknown key_id — including an already-revoked one — fails with api_key_not_found (no silent no-op, so a mistyped id can never mask a live credential). Guardrails: revoking the organization's last active key is refused with cannot_revoke_last_key — create a replacement with create_api_key first. Returns key_id with revoked: true.

NameTypeReqDescription
key_idstringyesAPI key id from list_api_keys.

No output schema declared.

No examples provided.

revoke_device ~113

Revoke one registered device by registration_id (find ids with list_devices), freeing one device slot. The device loses access on its next license refresh. This is a credential revocation, not an idempotent delete: an unknown registration_id — including an already-revoked one — fails with not_found (no silent no-op, so a mistyped id can never masquerade as a successful revocation). Returns revoked: true with the registration_id.

NameTypeReqDescription
registration_idstringyesDevice registration id from list_devices.

No output schema declared.

No examples provided.

route_capabilities ~250

Pick the best unified capability for a natural-language objective and return the route plan: the selected capability, binding, and kind, the authoritative execution_owner, whether approval is required, confidence and reason, plus ordered fallbacks (max_fallbacks, default 3). The optional filters narrow which catalog entries may be selected. Routing never executes anything — feed the selected_capability_id to execute_capability. This picks a capability for an objective; it is not decision analysis — use plan_decision or simulate for a DecisionPlan or full risk envelope instead. Read-only.

NameTypeReqDescription
artifact_affinitiesarray–Prefer capabilities affine to these artifacts.
binding_idsarray–Restrict candidates to these bindings.
execution_ownersarray–Restrict candidates to these execution owners.
kindsarray–Restrict candidates to these capability kinds.
max_fallbacksinteger–How many fallback routes to return, 0-10; defaults to 3.
objectivestringyesWhat you want to accomplish, in plain words.
provider_idsarray–Restrict candidates to these providers.
tagsarray–Prefer capabilities carrying these tags.

No output schema declared.

No examples provided.

run_repository_fix ~154

Run the repository pipeline and then apply its result in one call, returning the canonical repository envelope for both stages. pipeline takes run_repository_pipeline's arguments and must complete through simulate (the call fails otherwise); apply takes apply_repository's arguments with mode defaulting to patch_only — the write modes still require the simulation gate to pass and write_permission=true. Use the separate stage tools when you need to review the plan or simulation before anything is written.

NameTypeReqDescription
applyobject–apply_repository arguments (branch, message, PR fields, write_permission); mode defaults to patch_only.
pipelineobject–run_repository_pipeline arguments; defaults to {}.
repository_idstringyesSaved repository connector id from list_connectors.

No output schema declared.

No examples provided.

run_repository_pipeline ~323

Run the whole repository-intelligence chain — snapshot, triage, plan, simulate — in one call and return the canonical repository envelope with every stage's response, stage timings, and the ids (snapshot_id, plan_id, simulation_id) the apply step needs. Pass snapshot_id to reuse an existing snapshot or snapshot to create one inline; stop_after halts the chain early (triage skips the LLM planner, plan also skips the deterministic simulate). Signals, triage bounds, model, runs, and seed mirror the standalone stage tools. Use the single-stage tools when you need to inspect or adjust between stages.

NameTypeReqDescription
max_evidence_itemsinteger–Triage evidence item cap; defaults to 16.
max_snippet_linesinteger–Triage per-snippet line cap; defaults to 40.
modelstring–Optional planner model override for the plan stage.
repository_idstringyesSaved repository connector id from list_connectors.
runsinteger–Simulation scenario count; omit for the complexity-adaptive count.
seedinteger–Simulation seed; defaults to 42.
signalsobject–Triage evidence seeds (see triage_repository).
snapshotobject–Inline create_repository_snapshot arguments when no snapshot_id is given.
snapshot_idstring–Existing snapshot id to reuse.
stop_afterstring–Stage to halt after; defaults to simulate (full chain).
token_budgetinteger–Triage evidence token budget; defaults to 6000.

No output schema declared.

No examples provided.

score ~180

Run one simulation request (the same payload shape as simulate) and return the decision envelope fields plus a composite score with its breakdown. The score blends the normalized expected value and one minus the probability of loss; scoring_weights tunes the blend (expected_value default 0.6, downside_risk default 0.4). Use simulate when you need the full envelope without scoring, and compare to rank several scenarios. Synchronous deterministic compute; nothing is persisted. Returns recommended_action, expected_value, probability_of_loss, score, and score_breakdown. Which to use: one scenario reduced to a single weighted number; use simulate for the full envelope without scoring, or compare and recommend to pick between options.

NameTypeReqDescription
requestobjectyesSimulation request forwarded to POST /v1/score.
scoring_weightsobject–Optional expected_value/downside_risk weights.

No output schema declared.

No examples provided.

simulate ~274

Run a Monte Carlo simulation and get a structured decision recommendation. Use for: quantifying risk in a decision, comparing expected outcomes, getting probability-weighted recommendations. Synchronous deterministic compute governed by the plan's per-minute rate limit and monthly quota (429 on excess); the run is recorded asynchronously and appears in list_runs. Returns the decision envelope: recommended_action, expected_value, probability_of_loss, confidence, percentiles, and run metadata (run_id, execution_ms, scenarios_run). Which to use: the full decision-envelope analysis on ONE scenario; use compare for named scenario bake-offs, recommend for a ranked pick among actions, score for a single weighted number, plan_decision for just the plan summary, or product_decision for plain-English inputs.

NameTypeReqDescription
modestring–auto = minimal setup; expert = full distribution control
n_simulationsinteger–Monte Carlo iteration count. Auto mode accepts 100–100,000; expert mode accepts 100–1,000,000.
objectivestring–Auto-mode objective. For expert mode, use objective_function.
objective_functionstring–Expert-mode expression, for example 'revenue - cost'. Required when mode='expert'.
variablesarrayyesInput variables as triangular distributions (low, most-likely, high)

No output schema declared.

No examples provided.

simulate_repository ~200

Score the patch risk of a stored repository DecisionPlan with the deterministic simulation engine and return the gated DecisionEnvelope whose apply gate apply_repository checks. snapshot_id is resolved from the plan when omitted. runs pins the scenario count (100 or more; omit for the complexity-adaptive count) and seed (default 42) makes repeated calls reproducible — no LLM is involved in this stage. Call create_repository_decision_plan first; use simulate_repository_patch instead for a patch that has no stored plan.

NameTypeReqDescription
decision_plan_idstringyesPlan id from create_repository_decision_plan.
repository_idstringyesSaved repository connector id from list_connectors.
runsinteger–Scenario count, 100-250000; omit for the complexity-adaptive count.
seedinteger–Simulation seed for reproducible results; defaults to 42.
snapshot_idstring–Snapshot id; resolved from the decision plan when omitted.

No output schema declared.

No examples provided.

simulate_repository_patch ~141

Simulate the risk of an in-flight unified diff against one persisted snapshot and return the canonical repository envelope — without creating a stored decision plan. Use this to verify a working-tree patch mid-run; use simulate_repository when a stored DecisionPlan already exists. Deterministic; no LLM is involved. Returns the gated DecisionEnvelope including the apply gate verdict.

NameTypeReqDescription
confidencenumber–Optional caller confidence recorded with the simulation.
patch_diffstringyesUnified diff of the in-flight patch to evaluate.
repository_idstringyesSaved repository connector id from list_connectors.
snapshot_idstringyesSnapshot id from create_repository_snapshot.

No output schema declared.

No examples provided.

submit_job ~158

Submit a long-running async simulation job. Use for n_simulations > 500,000 or when you need a callback. variables is an array of {name, low, high} objects — one uniform range per variable; objective defaults to maximize and n_simulations defaults to 1000000. Returns a job_id — poll with get_job_status. Submitting persists the job under the active API key's organization; when callback_url is set, completion is delivered to it by outbound webhook.

NameTypeReqDescription
callback_urlstring–Webhook URL for completion notification
n_simulationsinteger––
objectivestring––
variablesarrayyesOne {name, low, high} object per variable (uniform range).

No output schema declared.

No examples provided.

test_capability_binding ~201

Run a health test on one capability binding and return the outcome. Pass binding_id to test a saved binding, or a full inline definition (provider_id, profile_id, config, ...) to preview-test one that was never saved — nothing is persisted in the preview form. Use this after create_capability_binding or update, before routing traffic to the binding.

NameTypeReqDescription
binding_idstring–Saved binding id to test; omit to preview-test inline.
configobject–Credentials/options for the inline preview form.
customer_metadataobject–Metadata for the inline preview form.
execution_ownerstring–Execution owner for the inline preview form.
profile_idstring–Profile id for the inline preview form.
provider_idstring–Provider id for the inline preview form.
scopestring–Scope for the inline preview form.
scope_refstring–Scope reference for the inline preview form.

No output schema declared.

No examples provided.

test_connector ~97

Run a real connectivity test against one saved connector's stored config and persist the outcome as its live or error status with last_tested_at. This opens an actual connection to the source. Use preview_test_connector for an unsaved inline definition, and browse_connector once the connector is live. Returns success, message, latency_ms, status, error_type, and recoverable.

NameTypeReqDescription
connector_idstringyesSaved connector id from list_connectors.

No output schema declared.

No examples provided.

test_webhook_delivery ~103

Send one real test webhook payload (event webhook.test with a sample message) to a callback URL and return the delivery result. This makes an actual outbound HTTP POST from the Algenta API to the given URL, with no retries. Use it to verify a receiver before wiring callback_url into submit_job or register_trigger. Returns success, the receiver's HTTP status_code, and a message.

NameTypeReqDescription
callback_urlstringyesURL that should receive the test webhook payload.

No output schema declared.

No examples provided.

tokenize ~135

Tokenize UTF-8 text into individual tokens with a supported deterministic Algenta tokenizer model (default text.tokenizer; call list_models for every supported model id). Use this when you need the token strings themselves; call count_tokens when you only need the number. Read-only and deterministic: the same input and model always return the same tokens, and nothing is stored. Returns the resolved model id, its tokenizer_kind, the tokens array, and token_count. An unsupported model id fails with model_not_supported.

NameTypeReqDescription
inputstringyesUTF-8 text to tokenize.
modelstring–Tokenizer model id from list_models.

No output schema declared.

No examples provided.

triage_repository ~240

Condense one repository snapshot into a bounded workspace evidence bundle for the planner: ranked suspect files and symbols with scored, budget-capped snippets. signals seeds the search — pass issue_text, diagnostics, failing_tests, changed_files, and/or workspace_context. The returned workspace_evidence_bundle_ref is the required input to create_repository_decision_plan; use run_repository_pipeline to chain both stages in one call. Read-only against the repository; persists the bundle artifact. Returns suspect_files, suspect_symbols, evidence_items, and token reduction stats.

NameTypeReqDescription
max_evidence_itemsinteger–Evidence item cap, 1-64; defaults to 16.
max_snippet_linesinteger–Per-snippet line cap, 5-200; defaults to 40.
repository_idstringyesSaved repository connector id from list_connectors.
signalsobjectyesEvidence seeds: issue_text, diagnostics, failing_tests, changed_files, workspace_context.
snapshot_idstringyesSnapshot id from create_repository_snapshot.
token_budgetinteger–Total evidence token budget, 256-32000; defaults to 6000.

No output schema declared.

No examples provided.

update_connector ~152

Partially update one saved connector: only the supplied fields change. Passing a new config replaces the encrypted credentials and resets the connector to untested, so call test_connector again afterwards. Requires manage permission on the connector (access_scope_denied otherwise) and at least one field; an unknown id fails with not_found. Returns the updated connector. Use preview_test_connector to validate a new config before applying it here.

NameTypeReqDescription
configobject–Replacement connection config; resets health status to untested.
connector_idstringyesSaved connector id from list_connectors.
descriptionstring–New description note.
namestring–New human-readable name.
visibilitystring–New visibility.

No output schema declared.

No examples provided.

update_execution_policy ~193

Partially update the organization's autonomous execution policy: only the fields supplied change, the rest keep their values. min_confidence blocks decisions below that confidence, risk_floor blocks decisions whose worst-case (p5) loss exceeds it, require_calibration makes auto-execution wait for enough recorded outcomes, and allow_reexecution is the idempotency gate. Changes take effect immediately, are recorded in the audit log, and write a new policy snapshot (see list_execution_policy_snapshots). Read the current values first with get_execution_policy. Returns the full updated policy.

NameTypeReqDescription
allow_reexecutionboolean–Idempotency gate preventing double-actions.
min_confidencenumber–Block executions whose confidence is below this, 0-1.
require_calibrationboolean–Require recorded outcomes before auto-execution.
risk_floornumber–Block executions whose worst-case (p5) loss exceeds this.

No output schema declared.

No examples provided.

update_me ~118

Update the current user's name and/or the organization name for the active API key; only the supplied fields change. Renaming the organization requires an admin or owner key (access_scope_denied otherwise), and the key must be linked to a user (user_not_found for service keys). At least one of name or org_name is required. Returns the updated identity; read it first with get_me.

NameTypeReqDescription
namestring–New display name for the calling user.
org_namestring–New organization name; requires admin or owner role.

No output schema declared.

No examples provided.

update_team_member_role ~140

Change one organization member's role by user_id (find ids with list_team_members). Requires an admin API key. Guardrails: you cannot change your own role (self_role_change_forbidden), only an owner can grant the owner role (owner_grant_forbidden), and demoting the last active owner is refused (last_owner). An unknown user_id fails with not_found. Returns the updated user_id and a confirmation message. Use remove_team_member to take the member out of the organization instead.

NameTypeReqDescription
rolestringyesNew org role for the member.
user_idstringyesTarget member's user_id from list_team_members.

No output schema declared.

No examples provided.

Install

How do I install the Algenta MCP Server server?

Algenta MCP Server runs locally as a PyPI package, launched with uvx algenta-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · algenta-mcp

# add to Claude Code
claude mcp add thyn-ai-algenta -- uvx algenta-mcp
Common questions

What is the Algenta MCP Server server?

Algenta MCP Server is listed in the public MCP registry as io.github.thyn-ai/algenta. Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP. This page covers its PyPI package (algenta-mcp).

Is the Algenta MCP Server server safe to use?

Algenta MCP Server scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Algenta MCP Server server expose?

Algenta MCP Server exposes 140 tools: onboard_dataset, list_datasets, get_dataset_status, retrain_dataset, connect_data, and 135 more. Their descriptions and schemas cost roughly 21,251 tokens of context every time the server is loaded.

Is the Algenta MCP Server server still maintained?

Algenta MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Algenta MCP Server server under?

Algenta MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.