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

REMOTE · API.ALGENTA.AI · 2 COMPONENTS

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

+55 this week 78 Trust /100

Last scanned (5 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 20559 tokens (~146/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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 −12
    • Stability: pass → 0.10 functional
  • 3 Nov 26 0
    • Server version: 1.0.42 → 1.0.44 functional
  • 1 Nov 26 +67
    • Authorization: unverified → fail ▼ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Server version: 1.0.33 → 1.0.42 functional
  • 10 Oct 26 −65
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 4 Oct 26 −2
    • HSTS header: pass → fail ▼ security
  • 1 Oct 26 0
    • Server version: 1.0.32 → 1.0.33 functional
  • 29 Sept 26 0
    • Server version: 1.0.31 → 1.0.32 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 · Probed https://api.algenta.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=algenta.ai CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 184b59994cbb2b570e579ee995b33edd
SANs: algenta.ai, *.algenta.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.algenta.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
algenta.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="algenta", error="invalid_token"

Bearer realm="algenta", error="invalid_token"
Header Value
strict-transport-security max-age=15552000; includeSubDomains

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.algenta.ai/mcp Verified 200
http (plaintext) http://api.algenta.ai/mcp HTTPS enforced 301 https://api.algenta.ai/mcp
MCP tools · 140 exposed · ~20,559 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
apply_repository ~358

Materialize a simulated repository decision in one of three modes. patch_only just returns the validated patch diff with applied=false and writes nothing. local_branch commits the patch to a new branch (default algenta/<plan-suffix>) in the engine-side checkout and returns commit_sha and local_checkout_path. remote_pr additionally pushes the branch and opens a pull request, returning pull_request_url. Both write modes are hard-gated: the simulation must satisfy policy thresholds (otherwise repository_apply_gate_failed) and write_permission=true must be passed explicitly (otherwise repository_write_permission_required). Use patch_only to review the diff before writing anything, and run_repository_fix to chain the whole flow. Requires decision_plan_id and simulation_id from simulate_repository.

NameTypeReqDescription
base_branchstring–Branch the patch applies onto and the PR targets; defaults to the connector's default branch.
branch_namestring–Branch to create; defaults to algenta/<plan-suffix>.
commit_messagestring–Commit message; a default naming the plan id is used otherwise.
decision_plan_idstringyesPlan id from create_repository_decision_plan.
modestringyespatch_only returns the diff; local_branch commits it; remote_pr pushes and opens a PR.
pull_request_bodystring–PR body for remote_pr mode.
pull_request_titlestring–PR title for remote_pr mode.
repository_idstringyesSaved repository connector id from list_connectors.
simulation_idstringyesSimulation id from simulate_repository.
snapshot_idstring–Snapshot id; resolved from the decision plan when omitted.
write_permissionboolean–Must be true for local_branch and remote_pr; ignored for patch_only.

No output schema declared.

No examples provided.

approve_agent_run ~113

Approve an agent run that is waiting on manual approval (status requires_approval) and execute it synchronously to completion. Runs in any other state fail with agent_run_invalid_state; an unknown run_id fails with agent_run_not_found. The approval is the human-in-the-loop gate for manual-mode runs and is audit-logged and checkpointed. Returns the updated run resource. Use resume_agent_run for paused runs instead.

NameTypeReqDescription
run_idstringyesWaiting run id from create_agent_run or list_agent_runs.

No output schema declared.

No examples provided.

batch ~102

Run multiple simulation requests in one call and return per-item success or failure details. Synchronous deterministic compute; nothing is persisted and no separate rate limit applies. Use simulate for a single request and submit_job for very large async runs. Returns total, succeeded, failed, and a per-item results array with index, success, the envelope's recommended_action and expected_value, or the item error.

NameTypeReqDescription
itemsarrayyesSimulation requests forwarded to POST /v1/batch.

No output schema declared.

No examples provided.

browse_connector ~107

Discover what one saved connector exposes — files, tables, endpoints, or items — with discovery labels and metadata for choosing what to onboard. The connector must be live: an untested or errored connector fails with not_connected, so run test_connector first. Use preview_browse_connector for an unsaved inline definition. Read-only against the source. Returns connector_type, items, total, message, labels, and discovery.

NameTypeReqDescription
connector_idstringyesSaved connector id from list_connectors.

No output schema declared.

No examples provided.

cancel_agent_run ~145

Cancel an agent run by run_id, ending its lifecycle at cancelled. Only a paused or requires_approval run can be cancelled — anything else fails with agent_run_invalid_state. Cancelling is idempotent: repeating the call on an already-cancelled or never-existing run_id returns success with already_absent: true instead of agent_run_not_found. Use resume_agent_run or approve_agent_run to continue a waiting run instead. The first cancellation is audit-logged and checkpointed; the run record is kept, not deleted, and repeats record nothing further. Returns the updated run resource.

NameTypeReqDescription
run_idstringyesRun id from create_agent_run or list_agent_runs.

No output schema declared.

No examples provided.

cancel_job ~103

Cancel a queued or running async simulation job by id. Use this for queued or running jobs; list_jobs shows their states. Cancelling is idempotent: repeating the call on an already-cancelled or never-existing id returns success with already_absent: true instead of an error; a completed or failed job is still refused with job_already_terminal. Returns the updated job record with its terminal status.

NameTypeReqDescription
job_idstringyesUUID of the async job

No output schema declared.

No examples provided.

chat_completions ~149

Run one ordered chat transcript through an Algenta model and return the assistant message plus token usage. The default text.tokenizer model is a deterministic tokenizer-backed utility route whose assistant message is a JSON tokenization summary of the user messages — not a generative LLM; provider-backed chat models advertised by list_models are routed through the configured provider service. Use responses for independent single-string utility calls. This tool does not stream and does not expose function/tool calling, and nothing is persisted. An unsupported model id fails with model_not_supported.

NameTypeReqDescription
messagesarrayyesOrdered conversation transcript; the last user message is the prompt.
modelstring–Chat-capable model id from list_models.

No output schema declared.

No examples provided.

compare ~158

Run 2-10 named scenarios side by side and return the winner plus each scenario's deltas versus the best one. The winner is the scenario with the highest expected value; every entry reports its recommended_action, expected_value, probability_of_loss, and delta_vs_best. Each scenario's request uses the simulate payload shape; runs and seed are forwarded for reproducibility. Use recommend for a ranked recommendation over actions instead. Synchronous deterministic compute; nothing is persisted.

NameTypeReqDescription
runsinteger–Scenario count per simulation; forwarded to each run.
scenariosarrayyesNamed scenarios, each {name, request} with request in the simulate payload shape; 2-10 items.
seedinteger–Simulation seed for reproducible results.

No output schema declared.

No examples provided.

connect_data ~408

High-level data onboarding flow. Use this instead of advanced connector/source tools for normal users. Connect data once, pick the table/file/endpoint, and get a reusable dataset_id. If the result status is needs_selection, call connect_data again with connection_id and the chosen selection. Creating a connection persists it and the dataset under the active API key's organization, and live sources are dialed during this call; no separate per-route rate limit applies. Returns status with dataset_id and connection_id on success, or status needs_selection with the choices array to pick from.

NameTypeReqDescription
connection_configobject–Legacy compatibility field for connector credentials/config. Prefer connector.location and connector.auth.credentials.
connection_idstring–Existing saved connection_id when resuming after selection.
connection_namestring–Optional label for the saved connection.
connection_typestring–Legacy compatibility field. Prefer connector.type with the canonical connector envelope.
connectorobject–Canonical connector envelope with type/location/auth/options. Preferred when the same request shape should work across Python Runtime, TypeScript Runtime, and MCP.
csvstring–Raw CSV text for direct file_upload datasets.
dataset_namestringyesName to save and reuse later.
descriptionstring––
excel_b64string–Base64-encoded Excel payload.
json_strstring–Raw JSON text for direct file_upload datasets.
parquet_b64string–Base64-encoded Parquet payload.
providerstring–Legacy compatibility field for provider selection. Prefer connector.type plus connector.location/auth/options.
recordsarray–Inline JSON records for direct file_upload datasets.
selectionobject–Legacy compatibility field for chosen table/query/path. Use the selection object returned in choices when resuming a legacy connection flow.
urlstring–URL for direct file_upload or API datasets.
visibilitystring–Shared requires admin/owner permissions.

No output schema declared.

No examples provided.

count_tokens ~134

Count how many tokens a supported deterministic Algenta tokenizer model produces for UTF-8 text (default text.tokenizer; call list_models for every supported model id). Use this for prompt-size checks and token budgeting; call tokenize when you also need the token strings. Read-only and deterministic: the same input and model always return the same count, and nothing is stored. Returns the resolved model id, its tokenizer_kind, and token_count. An unsupported model id fails with model_not_supported.

NameTypeReqDescription
inputstringyesUTF-8 text whose tokens are counted.
modelstring–Tokenizer model id from list_models.

No output schema declared.

No examples provided.

create_agent_run ~290

Create a persisted agent run lifecycle resource for a natural-language task. With approval_mode=auto (default) the run picks a tool from the task wording, executes synchronously, and returns completed; approval_mode=manual parks it at requires_approval until approve_agent_run, and start_paused=true parks it at paused until resume_agent_run. The run, its step log, append-only events, and a replayable checkpoint are persisted under the caller's organization and the creation is audit-logged. Use product_agent_run for the simpler synchronous helper, list_agent_runs to browse, and get_agent_run_events to follow the trail. Returns the full run resource with run_id and status.

NameTypeReqDescription
approval_modestring–auto executes immediately (default); manual waits for approve_agent_run before executing.
contextobject–Optional structured context or data for the task.
max_stepsinteger–Maximum execution steps, 1-50; defaults to 10.
output_formatstring–Result format: text (default), json, or markdown.
start_pausedboolean–Persist the run in paused state until resume_agent_run.
taskstringyesWhat the agent should do, in plain words (min 5 characters).
toolsarray–Restrict the tools the agent may pick from; defaults to search, simulate, optimize, calculate, summarize.

No output schema declared.

No examples provided.

create_api_key ~157

Create a new API key for the current organization and return its raw_key value exactly once — it is never shown again, so store it immediately. expires_at optionally sets an ISO-8601 expiry and device_limit caps how many devices the key may register (validated against the plan ceiling, invalid_device_limit on excess). Key creation is rate-limited per organization (api_key_create_rate_limited). Use list_api_keys to see existing keys and revoke_api_key to retire one.

NameTypeReqDescription
device_limitinteger–Optional per-key device cap; must not exceed the plan ceiling.
expires_atstring–Optional ISO-8601 expiry timestamp for the key.
labelstringyesHuman-readable label identifying the key's purpose.

No output schema declared.

No examples provided.

create_billing_checkout ~98

Create a Stripe Checkout session for the active organization and return its hosted checkout URL. The user completes the purchase in the browser; nothing is charged by this call itself. Requires an owner API key. plan defaults to developer; an unsupported plan fails with invalid_plan. Use get_billing_info to check the current plan and create_billing_portal to manage an existing subscription.

NameTypeReqDescription
planstring–Plan to purchase; defaults to developer.

No output schema declared.

No examples provided.

create_billing_portal ~77

Create a Stripe Billing Portal session for the active organization and return its URL, where the user manages payment methods, invoices, and the subscription. Requires an owner API key and an existing billing account — an org that has never checked out fails with no_billing_account (call create_billing_checkout first). This call itself changes nothing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_capability_binding ~231

Save one capability binding for a provider/profile pair and return it with its binding_id. scope (default workspace) decides who can use it, execution_owner decides where executions run (algenta_managed on the engine, client_managed in the customer app or adapter path), and config carries the profile's credentials and options. Find valid provider_id/profile_id pairs with list_capability_providers, then call discover_capability_binding to publish the binding's capabilities and test_capability_binding to verify. Persists the binding.

NameTypeReqDescription
binding_namestringyesHuman-readable binding name.
configobject–Profile credentials and options.
customer_metadataobject–Optional caller metadata stored with the binding.
execution_ownerstring–Where executions run; defaults to the profile's default_execution_owner.
profile_idstringyesProfile id within the provider.
provider_idstringyesProvider id from list_capability_providers.
scopestring–Visibility scope; defaults to workspace.
scope_refstring–Optional concrete user/workspace id the scope binds to.

No output schema declared.

No examples provided.

create_connector ~182

Save one connector configuration (host, credentials, options) for later data onboarding, health checks, and schema browsing. config is encrypted at rest and the new connector starts untested — call test_connector to verify it reaches the source, then browse_connector to discover what it exposes. Returns the saved connector with its connector_id, persisted under the active API key's organization. To try a definition without saving anything, call preview_test_connector instead.

NameTypeReqDescription
configobject–Type-specific connection settings and credentials; encrypted at rest and never returned.
connector_typestringyesConnector type id, e.g. a database, API, file, or repository type.
descriptionstring–Optional note on what this connector is for.
namestringyesHuman-readable connector name.
visibilitystring–Who can see the connector; defaults to private.

No output schema declared.

No examples provided.

create_deployment ~178

Request a new isolated engine deployment for the active organization on the chosen provider and region. Returns immediately with status requested — provisioning is asynchronous, so poll get_deployment until status is active; API calls then route to the isolated deployment automatically. Requires an owner API key. Only one active or in-progress deployment is allowed per org (deployment_exists otherwise — call delete_deployment first), and unknown provider/region pairs fail validation; list_deployment_regions shows the valid combinations.

NameTypeReqDescription
billing_markup_pctnumber–Billing markup percentage applied to this deployment, 0-200.
configobject–Optional provider-specific configuration.
providerstring–Cloud provider: algenta_shared (default), aws, azure, or gcp.
regionstring–Region id from list_deployment_regions; defaults to algenta-shared.

No output schema declared.

No examples provided.

create_repository_decision_plan ~171

Create one stored, immutable repository DecisionPlan revision from a triage workspace evidence bundle and return its decision_plan_id plus the validated patch diff inline. snapshot_id is resolved from the bundle when omitted. This is the only LLM-touching stage of the repository chain; model optionally picks the planner model. The decision_plan_id feeds simulate_repository and apply_repository. Persists the plan revision. Use run_repository_pipeline to chain snapshot, triage, plan, and simulate in one call instead.

NameTypeReqDescription
modelstring–Optional planner model override.
repository_idstringyesSaved repository connector id from list_connectors.
snapshot_idstring–Snapshot id; resolved from the evidence bundle when omitted.
workspace_evidence_bundle_refstringyesBundle ref returned by triage_repository.

No output schema declared.

No examples provided.

create_repository_snapshot ~245

Create or reuse an immutable, content-hashed snapshot of a saved repository connector (a connector of a repository type — find its id with list_connectors). Re-running with identical inputs returns the existing snapshot (status='existing') instead of duplicating it. The snapshot is the input to triage_repository and query_repository_graph; every later stage references it by snapshot_id. Reads the repository and persists snapshot, symbol, and dependency graph artifacts; it never writes to the repository. Returns snapshot_id, resolved_revision, content_hash, file_count, language_counts, and artifact refs.

NameTypeReqDescription
exclude_patternsarray–Glob patterns excluding files from the snapshot.
include_patternsarray–Glob patterns limiting which files are snapshotted.
max_file_size_bytesinteger–Per-file size cap in bytes, 1024-10000000; defaults to 1000000.
max_filesinteger–File-count cap, up to 200000; defaults to 20000.
refstring–Git ref to snapshot; defaults to the connector's default ref.
repository_idstringyesSaved repository connector id from list_connectors.

No output schema declared.

No examples provided.

delete_connector ~75

Delete one saved connector by id. Use update_connector to change config without losing the saved definition. Deleting is idempotent: repeating the call on an already-deleted or never-existing id returns success with already_absent: true instead of an error. Returns connector_id with deleted: true.

NameTypeReqDescription
connector_idstringyes–

No output schema declared.

No examples provided.

delete_decision ~82

Delete one decision-memory record by id. Deletion is permanent; review with list_decisions first. Deleting is idempotent: repeating the call on an already-deleted or never-existing id returns success with already_absent: true instead of an error. Returns the deletion confirmation for the decision_id.

NameTypeReqDescription
decision_idstringyesDecision ID to delete.

No output schema declared.

No examples provided.

delete_deployment ~97

Request deprovisioning for one deployment by id. Deprovision with this before create_deployment when a deployment already exists. Deleting is idempotent: repeating the call on an already-deprovisioned or never-existing id returns success with already_absent: true instead of an error. Returns status 'deprovisioning' with the deployment_id; deprovisioning is asynchronous.

NameTypeReqDescription
deployment_idstringyes–

No output schema declared.

No examples provided.

delete_trigger ~106

Delete one trigger by trigger_id (find ids with list_triggers). The trigger is removed immediately and will no longer fire automatically; its registration cannot be recovered from this tool. To stop a trigger temporarily instead, use pause_trigger. Deleting is idempotent: repeating the call on an already-deleted or never-existing id returns success with already_absent: true instead of an error. Returns trigger_id with deleted: true.

NameTypeReqDescription
trigger_idstringyesTrigger ID to delete.

No output schema declared.

No examples provided.

disable_skill ~126

Disable one skill by deleting its capability binding (find binding ids with list_skills or list_capability_bindings). The skill immediately stops appearing in the capability catalog and can no longer be routed or executed; the deletion is permanent. Disabling is idempotent: repeating the call on an already-disabled or never-existing binding returns success with already_absent: true instead of an error. Returns binding_id with disabled: true. Use this only for permanent removal — re-enabling later requires a fresh enable_skill call.

NameTypeReqDescription
binding_idstringyesSkill binding id from list_skills.

No output schema declared.

No examples provided.

disconnect_data ~134

Delete a saved dataset and disconnect it from future use. When no other dataset in the workspace still uses the backing saved connection, that connection is deleted too and connection_deleted is true in the response. Requires manage permission on the dataset (access_scope_denied otherwise). Use list_data to confirm the dataset first — deletion is immediate. Deleting is idempotent: repeating the call on an already-deleted or never-existing dataset_id returns success with already_absent: true instead of not_found. Returns dataset_id, status 'deleted', and connection_deleted.

NameTypeReqDescription
dataset_idstringyesDataset ID from connect_data or list_data.

No output schema declared.

No examples provided.

discover_capability_binding ~194

Discover the capabilities one binding exposes and return them as catalog entries. Pass binding_id to discover a saved binding (this publishes or refreshes its capabilities in the catalog), or a full inline definition to preview-discover one that was never saved. Call this after create_capability_binding, then browse the result with list_capabilities.

NameTypeReqDescription
binding_idstring–Saved binding id to discover; omit to preview 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.

embedding_similarity ~137

Score the similarity between two caller-supplied embedding vectors with a supported deterministic metric (default embeddings.cosine_similarity). This tool does not generate embeddings from text — call embeddings first to produce the vectors. left and right must have equal length or the call fails with invalid_embedding_dimensions. Read-only and deterministic. Returns the resolved model id, similarity_metric, the score, and the shared vector dimension.

NameTypeReqDescription
leftarrayyesFirst embedding vector; length must equal right's.
modelstring–Similarity model id from list_models; selects the metric.
rightarrayyesSecond embedding vector; length must equal left's.

No output schema declared.

No examples provided.

embeddings ~161

Generate one embedding vector per input string (a single string or a list of strings). The default text.hash_embedding_v1 model produces deterministic lexical hash embeddings — identical input always yields the identical vector; provider-backed embedding models advertised by list_models are routed through the configured provider service. Use embedding_similarity to score two vectors or rerank to order documents against a query vector. Read-only; nothing is stored. Returns one {index, embedding, token_count} item per input plus total token usage. An unsupported model id fails with model_not_supported.

NameTypeReqDescription
dimensionsinteger–Length of each returned embedding vector.
input–yesText to embed: one string, or a list embedded item by item.
modelstring–Embedding model id from list_models.

No output schema declared.

No examples provided.

enable_skill ~159

Enable one prompt skill as a first-class capability binding and return its discovered catalog entry. The skill's instruction text becomes an instruction_only capability under the caller's user scope, selectable by route_capabilities. Persists a new binding; remove it with disable_skill. Use list_skills to see what is already enabled.

NameTypeReqDescription
artifact_affinitiesarray–Optional artifact affinities for routing.
descriptionstring–Optional human-readable summary of the skill.
execution_ownerstring–Where executions run; defaults to client_managed.
instructionstringyesInstruction text the skill injects when selected.
skill_namestringyesSkill name; also names the new binding.
tagsarray–Optional routing tags.

No output schema declared.

No examples provided.

execute_capability ~178

Execute one routed or known algenta_managed capability by capability id and return the execution receipt. client_managed routes must execute in the customer app or adapter path — this tool will not run them. If the capability requires approval (approval_required), this returns a pending plan (status='approval_required', plus plan_id/plan_hash/nonce) instead of executing — approval and the final plan_id execution are separate, credentialed HTTP operations and are NOT available as tools. Route first with route_capabilities when the right capability is not known.

NameTypeReqDescription
binding_idstring–Optional binding id to disambiguate the execution target.
capability_idstringyesCapability id from route_capabilities or list_capabilities.
inputobject–Capability-specific execution input.
request_idstring–Optional caller request id for correlation.

No output schema declared.

No examples provided.

execute_decision ~168

Dispatch a logged decision to an external webhook and persist the execution receipt. Use record_outcome instead when reporting a result rather than dispatching an action. Returns the delivery receipt: decision_id, webhook_url, execution_status, response_code, executed_at, and the policy and schema snapshot ids.

NameTypeReqDescription
decision_idstringyesDecision ID from log_decision or list_decisions.
forceboolean–Override the idempotency gate for one re-execution.
metadataobject–Optional key-value pairs merged into the webhook payload.
override_safetyboolean–Bypass confidence and risk-floor policy gates for this execution.
timeout_secondsnumber–Webhook timeout in seconds.
webhook_urlstringyesHTTPS webhook that should receive the decision payload.

No output schema declared.

No examples provided.

execute_runtime_library ~122

Execute one local-runtime Mojo library function by module and function name. Pass args as either a JSON object, array, scalar, or null. This surface is local/runtime-backed only and does not route through hosted data/query APIs.

NameTypeReqDescription
args––JSON-serializable args payload. May be an object, array, scalar, or null.
functionstringyesFunction name exposed by the runtime module.
modulestringyesCanonical runtime module name, including dotted names.
request_idstring–Optional stable request identifier for traceability.

No output schema declared.

No examples provided.

fire_trigger ~119

Manually fire a trigger — evaluates its condition and runs the simulation template regardless of whether the threshold is currently met. Useful for testing triggers or forcing an immediate evaluation. Use pause_trigger to stop automatic firing without deleting the trigger. Returns trigger_id, condition_met, fired, simulation_run_id, recommended_action, expected_value, confidence, and fired_at.

NameTypeReqDescription
forceboolean–When true, run simulation even if the condition is not currently met (default: false).
trigger_idstringyesTrigger ID from register_trigger or list_triggers.

No output schema declared.

No examples provided.

get_agent_run ~103

Fetch one persisted agent run by run_id: status, task, selected_tool, steps, result, tools_used, and the policy/schema snapshot ids it ran under. Use list_agent_runs to find run ids, get_agent_run_events for its event trail, and get_agent_run_checkpoints for replay checkpoints. Read-only; an unknown run_id fails with agent_run_not_found.

NameTypeReqDescription
run_idstringyesRun id returned by create_agent_run or list_agent_runs.

No output schema declared.

No examples provided.

get_agent_run_checkpoints ~89

List the persisted checkpoints of one agent run — the deterministic snapshots written at creation and every lifecycle transition that make the run replayable. Use query_agent_run_checkpoints to search checkpoints across runs. Read-only; an unknown run_id fails with agent_run_not_found. Returns the run's checkpoint records.

NameTypeReqDescription
run_idstringyesRun id returned by create_agent_run or list_agent_runs.

No output schema declared.

No examples provided.

get_agent_run_events ~126

Fetch the append-only event stream of one agent run — run_created, tool_selected, tool_executed, run_completed, and the pause/approve/cancel transitions — in order. Use get_agent_run_mission_events for the canonical mission-event projection of the same trail. Read-only; an unknown run_id fails with agent_run_not_found. Returns data plus total_events.

NameTypeReqDescription
limitinteger–Maximum events returned, up to 1000; defaults to 1000.
run_idstringyesRun id returned by create_agent_run or list_agent_runs.

No output schema declared.

No examples provided.

get_agent_run_mission_events ~126

Fetch the canonical mission-event records of one agent run — the typed, indexed projection of its lifecycle used for audit and replay. Use get_agent_run_events for the raw append-only stream and query_agent_run_mission_events to search mission events across runs. Read-only; an unknown run_id fails with agent_run_not_found. Returns the run's canonical mission-event records.

NameTypeReqDescription
limitinteger–Maximum events returned, up to 1000; defaults to 1000.
run_idstringyesRun id returned by create_agent_run or list_agent_runs.

No output schema declared.

No examples provided.

get_agent_run_telemetry ~114

Fetch the runtime telemetry batches recorded for one agent run — the module-level timing and execution detail captured while it ran. Use query_agent_run_telemetry to search telemetry across runs by kind or module. Read-only; an unknown run_id fails with agent_run_not_found. Returns the run's telemetry batches.

NameTypeReqDescription
limitinteger–Maximum batches returned, up to 1000; defaults to 1000.
run_idstringyesRun id returned by create_agent_run or list_agent_runs.

No output schema declared.

No examples provided.

get_analytics ~87

Get aggregate usage analytics over the organization's simulation runs inside a lookback window: total_simulations, avg_confidence, action_breakdown (how recommended actions distribute), and latency_p95_ms. days sets the window (default 30, range 1-365). Use list_runs for individual runs instead of aggregates. Read-only.

NameTypeReqDescription
daysinteger–Lookback window in days

No output schema declared.

No examples provided.

get_audit_log_artifacts ~286

Query the organization's immutable Parquet audit-log artifacts with pagination (defaults page 1, limit 25) and exact-match filters, including content_hash for pinpointing one artifact. Artifacts are the tamper-evident copy of the audit trail; use get_audit_logs for the live audit-event table. Requires an admin API key; a workspace-scoped key sees only its own workspace's artifacts. Read-only. Returns entries plus total, page, limit, and pages.

NameTypeReqDescription
actionstring–Keep only artifacts with this action.
actor_emailstring–Keep only artifacts by this actor email.
content_hashstring–Keep only the artifact with this content hash.
limitinteger–Entries per page, up to 100; defaults to 25.
manifest_versionstring–Keep only artifacts tied to this runtime manifest version.
pageinteger–1-based page number; defaults to 1.
policy_snapshot_idstring–Keep only artifacts tied to this execution-policy snapshot.
request_hashstring–Keep only artifacts tied to this request hash.
resource_typestring–Keep only artifacts against this resource type.
resultstring–Keep only artifacts with this result value.
schema_snapshot_idstring–Keep only artifacts tied to this schema snapshot.

No output schema declared.

No examples provided.

get_audit_logs ~288

Query the organization's audit-event log, newest first, with pagination (defaults page 1, limit 25) and exact-match filters. Every entry records who did what to which resource with which result; an org with no events returns an honest empty page. Requires an admin API key. Use get_audit_log_artifacts for the immutable Parquet artifact copy, and filter by policy_snapshot_id, schema_snapshot_id, manifest_version, or request_hash to trace one execution. Read-only. Returns entries plus total, page, limit, and pages.

NameTypeReqDescription
actionstring–Keep only events with this action, e.g. execution_policy.update.
actor_emailstring–Keep only events by this actor email.
limitinteger–Entries per page, up to 100; defaults to 25.
manifest_versionstring–Keep only events tied to this runtime manifest version.
pageinteger–1-based page number; defaults to 1.
policy_snapshot_idstring–Keep only events tied to this execution-policy snapshot.
request_hashstring–Keep only events tied to this request hash.
resource_typestring–Keep only events against this resource type.
resultstring–Keep only events with this result value.
schema_snapshot_idstring–Keep only events tied to this schema snapshot.

No output schema declared.

No examples provided.

get_billing_info ~65

Get current billing plan and subscription info for the active organization. Read-only and non-destructive; not separately rate-limited. Use create_billing_checkout or create_billing_portal to change anything. Returns plan, stripe_customer_id, subscription_status, and current_period_end.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_capability ~101

Fetch one unified capability catalog entry by capability_id: kind, provider, binding, execution owner, approval requirement, and tags. include_instruction=true also returns the skill instruction text. Find capability ids with list_capabilities or route_capabilities. Read-only; an unknown id fails with not_found.

NameTypeReqDescription
capability_idstringyesCapability id from list_capabilities or route_capabilities.
include_instructionboolean–Also return the instruction text for skill capabilities.

No output schema declared.

No examples provided.

get_connector ~73

Fetch one saved connector by connector_id: name, connector_type, status, visibility, timestamps, and the config fingerprint — never the stored credentials. Use list_connectors to find ids. Read-only; an unknown or invisible id fails with not_found.

NameTypeReqDescription
connector_idstringyesSaved connector id from list_connectors.

No output schema declared.

No examples provided.

get_contract ~64

Get the machine-readable Algenta public contract. Use this when an agent needs the canonical discovery, summary, query, batch, SQL report, governed filter rules, CLI, or MCP entrypoints before planning tool use. Read-only and non-destructive; not separately rate-limited.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_data_schema ~96

Get a saved dataset plus its schema and relationship metadata by dataset_id. Read-only and non-destructive; reads only the active API key's organization and is not separately rate-limited. Use get_data_summary first for a low-token look. Returns the dataset record and its schema: row_count, columns, roles_summary, formulas, and query_hints.

NameTypeReqDescription
dataset_idstringyesDataset ID from connect_data or list_data.

No output schema declared.

No examples provided.

get_data_summary ~105

Get the low-token dataset selection summary for a saved dataset_id. Use this after list_data(search=..., compact=true) before paying for the full schema payload. Read-only and non-destructive; reads only the active API key's organization and is not separately rate-limited. Returns dataset_id, name, status, source_names, row_count, column_count, registered_at, and query_hints.

NameTypeReqDescription
dataset_idstringyesDataset ID from connect_data or list_data.

No output schema declared.

No examples provided.

get_dataset_status ~133

Get the live training status and model tier of one dataset: whether semantic training is still running or the dataset is ready, and which model serves queries — model_tier 'none' = deterministic fallback only, 'base' = generic model, 'schema' = fully trained schema-specific model (best quality). Poll this after onboard_dataset until training completes, and use retrain_dataset after schema or alias changes. Read-only; an unknown dataset_id fails with not_found. Also returns name, column_count, source_names, and updated_at.

NameTypeReqDescription
dataset_idstringyesDataset ID from onboard_dataset or list_datasets.

No output schema declared.

No examples provided.

get_decision ~81

Fetch one decision-memory record by id. Read-only and non-destructive; not separately rate-limited. Use list_decisions to find decision ids. Returns the full decision record including context, options_considered, risk fields, integrity hashes, and outcome fields when recorded.

NameTypeReqDescription
decision_idstringyesDecision ID from log_decision or list_decisions.

No output schema declared.

No examples provided.

get_deployment ~76

Fetch the current deployment for the active organization, if one exists. Read-only and non-destructive; not separately rate-limited. Poll this after create_deployment until status is active. Returns the deployment record (deployment_id, provider, region, status, config, created_at) or null when the organization is on the shared pool.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Algenta MCP Server server?

Algenta MCP Server is a hosted endpoint at https://api.algenta.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.algenta.ai

# add to Claude Code
claude mcp add --transport http thyn-ai-algenta 'https://api.algenta.ai/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 hosted endpoint (https://api.algenta.ai/mcp).

Is the Algenta MCP Server server safe to use?

Algenta MCP Server scores 78 out of 100 on VerifyMCP. 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 20,559 tokens of context every time the server is loaded.

Does the Algenta MCP Server server require authentication?

Yes. Algenta MCP Server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

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.