Is io.github.thyn-ai/algenta up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://api.algenta.ai/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardCould not tell (HTTP 525).
/.well-known/agent-card.json
MCP server card (SEP-2127)Could not tell (HTTP 525).
https://api.algenta.ai/mcp/server-card
MCP server card (SEP-1649 location)Could not tell (HTTP 525).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryCould not tell (HTTP 525).
/.well-known/http-message-signatures-directory

Read at https://api.algenta.ai with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 140 tools: apply_repository, approve_agent_run, batch, browse_connector, cancel_agent_run, cancel_job, chat_completions, compare, connect_data, count_tokens, create_agent_run, create_api_key, create_billing_checkout, create_billing_portal, create_capability_binding, create_connector, create_deployment, create_repository_decision_plan, create_repository_snapshot, delete_connector, delete_decision, delete_deployment, delete_trigger, disable_skill, disconnect_data, discover_capability_binding, embedding_similarity, embeddings, enable_skill, execute_capability, execute_decision, execute_runtime_library, fire_trigger, get_agent_run, get_agent_run_checkpoints, get_agent_run_events, get_agent_run_mission_events, get_agent_run_telemetry, get_analytics, get_audit_log_artifacts, get_audit_logs, get_billing_info, get_capability, get_connector, get_contract, get_data_schema, get_data_summary, get_dataset_status, get_decision, get_deployment, get_deployment_cost, get_execution_policy, get_job_result, get_job_status, get_limits, get_me, get_repository_intelligence_capabilities, get_repository_snapshot, get_run, get_runtime_benchmarks, get_runtime_manifest, get_runtime_modules, get_runtime_release_validation, get_source_schema, get_usage, ingest_data, ingest_metering_events, invite_team_member, list_agent_runs, list_api_keys, list_capabilities, list_capability_bindings, list_capability_providers, list_connectors, list_data, list_datasets, list_decisions, list_deployment_regions, list_devices, list_distributions, list_execution_policy_snapshots, list_jobs, list_models, list_runs, list_runtime_libraries, list_skills, list_sources, list_team_members, list_templates, list_triggers, log_decision, onboard_dataset, pause_trigger, plan_decision, poll_job, preview_browse_connector, preview_test_connector, product_agent_run, product_decision, product_forecast and 40 more.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameio.github.thyn-ai/algenta
Endpointhttps://api.algenta.ai/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy