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.

Terradev

REMOTE · TERRADEV-MCP.TERRADEV.CLOUD · 2 COMPONENTS

Cross-cloud GPU orchestration CLI.

0 this week 72 Trust /100

Last scanned (17 hours ago)

Scores higher than 58% of remote servers

Unreachable for 1 day in a row. Last reached 4 Nov 2026.

Category Cloud Infrastructure

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
  • 10 Oct 26 +1
    • Stability: fail → pass ▲ security
  • 7 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 93.

  • 5 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87.

  • 29 Sept 26 0
    • Schema quality: 27375 → 30174 ▼ functional
    • New tool “preflight_provision” functional
    • New tool “migrate_status” functional
    • New tool “migrate_rollback” functional
    • New tool “migrate_plan” functional
    • New tool “migrate_execute” functional
    • New tool “migrate_compare” functional
    • New tool “lineage_trace” functional
    • New tool “lineage_graph” functional
    • New tool “lineage_export” functional
    • New tool “lineage_diff” functional
    • New tool “lineage_checkpoint” functional
    • New tool “kv_cache_efficiency” functional
    • New tool “karpenter_status” functional
    • New tool “karpenter_resources” functional
    • New tool “karpenter_nodepools” functional
    • New tool “karpenter_logs” functional
    • New tool “karpenter_install” functional
    • New tool “karpenter_gpu_nodes” functional
    • New tool “karpenter_events” functional
    • New tool “karpenter_delete_nodepool” functional
    • New tool “karpenter_create_nodepool” functional
    • New tool “environments_promote” functional
    • New tool “environments_list” functional
    • New tool “environments_history” functional
    • New tool “environments_create” functional
    • New tool “environments_approve” functional
    • New tool “triggers_enable” functional
    • New tool “triggers_execute” functional
    • New tool “triggers_history” functional
    • New tool “triggers_create” functional
    • New tool “triggers_list” functional
    • New tool “quote_gpu” 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
  • 25 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
  • 10 Sept 26 0

    First indexed and scored.

    • Stability: 0.03 → fail ▼ security
    • A breaking change shipped without a version bump: still 2.0.1 ▼ security
    • Tool “vault_get” was removed ▼ security
    • Tool “vault_set” was removed ▼ security
    • Tool “vault_sync” was removed ▼ security
    • Tool “vault_run” was removed ▼ security
    • Tool “vault_list” was removed ▼ security
    • Tool “vault_remove” was removed ▼ security
    • Tool “vault_env” was removed ▼ security
    • Tool “vault_verify” was removed ▼ security
    • New tool “secrets_run” functional
    • New tool “secrets_get” functional
    • New tool “secrets_list” functional
    • New tool “secrets_env” functional
    • New tool “secrets_set” functional
    • New tool “secrets_remove” functional
    • New tool “secrets_verify” functional
    • New tool “secrets_sync” functional
    • “agent_mem0_forget” reworded the description of “credentials” cosmetic
    • “phoenix_otel_env” reworded the description of “credentials” cosmetic
    • “langfuse_score” reworded the description of “credentials” cosmetic
    • “ray_status” reworded the description of “credentials” cosmetic
    • “agent_deploy” reworded the description of “credentials” cosmetic
    • “agent_mem0_get” reworded the description of “credentials” cosmetic
    • “training_launch_distributed” reworded the description of “credentials” cosmetic
    • “price_intel” reworded the description of “credentials” cosmetic
    • “agent_mem0_update” reworded the description of “credentials” cosmetic
    • “vllm_benchmark” reworded the description of “credentials” cosmetic
    • “langchain_create_workflow” reworded the description of “credentials” cosmetic
    • “train_unsloth_run” reworded the description of “credentials” cosmetic
    • “run_workflow” reworded the description of “credentials” cosmetic
    • “sglang_inference” reworded the description of “credentials” cosmetic
    • “status” reworded the description of “credentials” cosmetic
    • “active_context” reworded the description of “credentials” cosmetic
    • “manage_instance” reworded the description of “credentials” cosmetic
    • “warm_pool_start” reworded the description of “credentials” cosmetic
    • “dvc_diff” reworded the description of “credentials” cosmetic
    • “vllm_wake” reworded the description of “credentials” cosmetic
    • “agent_status” reworded the description of “credentials” cosmetic
    • “hf_smart_template” reworded the description of “credentials” cosmetic
    • “provision_gpu” reworded the description of “credentials” cosmetic
    • “train_snapshot” reworded the description of “credentials” cosmetic
    • “checkpoint_delete” reworded the description of “credentials” cosmetic
    • “hf_list_datasets” reworded the description of “credentials” cosmetic
    • “database_weaviate_query” reworded the description of “credentials” cosmetic
    • “sglang” reworded the description of “credentials” cosmetic
    • “deepeval_metrics” reworded the description of “credentials” cosmetic
    • “dvc_status” reworded the description of “credentials” cosmetic
    • “dvc_push” reworded the description of “credentials” cosmetic
    • “langgraph_workflow_status” reworded the description of “credentials” cosmetic
    • “sglang_stop” reworded the description of “credentials” cosmetic
    • “agent_langgraph_status” reworded the description of “credentials” cosmetic
    • “phoenix_spans” reworded the description of “credentials” cosmetic
    • “wandb_run_details” reworded the description of “credentials” cosmetic
    • “phoenix_k8s” reworded the description of “credentials” cosmetic
    • “guardrails_k8s” reworded the description of “credentials” cosmetic
    • “langgraph_orchestrator_worker” reworded the description of “credentials” cosmetic
    • “orchestrator_status” reworded the description of “credentials” cosmetic
    • “langfuse_quality” reworded the description of “credentials” cosmetic
    • “agent_mem0_add” reworded the description of “credentials” cosmetic
    • “get_database_connection” reworded the description of “credentials” cosmetic
    • “cost_simulate” reworded the description of “credentials” cosmetic
    • “helm_generate” reworded the description of “credentials” cosmetic
    • “agent_agentic_serving_show_config” reworded the description of “credentials” cosmetic
    • “qdrant_collections” reworded the description of “credentials” cosmetic
    • “agent_letta_list” reworded the description of “credentials” cosmetic
    • “hf_create_endpoint” reworded the description of “credentials” cosmetic
    • “inferx_usage” reworded the description of “credentials” cosmetic
    • “ollama_model_info” reworded the description of “credentials” cosmetic
    • “guardrails_chat” reworded the description of “credentials” cosmetic
    • “train_stop” reworded the description of “credentials” cosmetic
    • “infer_failover” reworded the description of “credentials” cosmetic
    • “train_resume” reworded the description of “credentials” cosmetic
    • “governance_request_consent” reworded the description of “credentials” cosmetic
    • “ollama_pull” reworded the description of “credentials” cosmetic
    • “dvc_stage_checkpoint” reworded the description of “credentials” cosmetic
    • “agent_langchain_create_langgraph” reworded the description of “credentials” cosmetic
    • “analytics” reworded the description of “credentials” cosmetic
    • “langgraph_create_workflow” reworded the description of “credentials” cosmetic
    • “sglang_start” reworded the description of “credentials” cosmetic
    • “agent_cost” reworded the description of “credentials” cosmetic
    • “agent_skill_attach” reworded the description of “credentials” cosmetic
    • “preflight” reworded the description of “credentials” cosmetic
    • “qdrant_info” reworded the description of “credentials” cosmetic
    • “agent_teardown” reworded the description of “credentials” cosmetic
    • “train_monitor” reworded the description of “credentials” cosmetic
    • “egress_cheapest_route” reworded the description of “credentials” cosmetic
    • “agent_agentic_serving_launch_args” reworded the description of “credentials” cosmetic
    • “inferx_list” reworded the description of “credentials” cosmetic
    • “database_weaviate_list_collections” reworded the description of “credentials” cosmetic
    • “hf_delete_endpoint” reworded the description of “credentials” cosmetic
    • “vllm_analyze” reworded the description of “credentials” cosmetic
    • “hf_list_endpoints” reworded the description of “credentials” cosmetic
    • “inferx_quote” reworded the description of “credentials” cosmetic
    • “query_database” reworded the description of “credentials” cosmetic
    • “ray_start” reworded the description of “credentials” cosmetic
    • “price_trends” reworded the description of “credentials” cosmetic
    • “checkpoint_list” reworded the description of “credentials” cosmetic
    • “k8s_create” reworded the description of “credentials” cosmetic
    • “hf_model_info” reworded the description of “credentials” cosmetic
    • “preflight_report” reworded the description of “credentials” cosmetic
    • “ollama_ps” reworded the description of “credentials” cosmetic
    • “vllm_info” reworded the description of “credentials” cosmetic
    • “inferx_optimize” reworded the description of “credentials” cosmetic
    • “hf_space_deploy” reworded the description of “credentials” cosmetic
    • “orchestrator_register” reworded the description of “credentials” cosmetic
    • “lora_remove” reworded the description of “credentials” cosmetic
    • “infer_route” reworded the description of “credentials” cosmetic
    • “inferx_status” reworded the description of “credentials” cosmetic
    • “hf_hardware_compare” reworded the description of “credentials” cosmetic
    • “k8s_list” reworded the description of “credentials” cosmetic
    • “checkpoint_save” reworded the description of “credentials” cosmetic
    • “agent_letta_delete” reworded the description of “credentials” cosmetic
    • “agent_langgraph_deploy” reworded the description of “credentials” cosmetic
    • “agent_vector_db_up” reworded the description of “credentials” cosmetic
    • “vllm_auto_optimize” reworded the description of “credentials” cosmetic
    • “create_sqlite_connection” reworded the description of “credentials” cosmetic
    • “train_status” reworded the description of “credentials” cosmetic
    • “agent_skill_init” reworded the description of “credentials” cosmetic
    • “langfuse_datasets” reworded the description of “credentials” cosmetic
    • “governance_record_consent” reworded the description of “credentials” cosmetic
    • “agent_letta_status” reworded the description of “credentials” cosmetic
    • “agent_letta_chat” reworded the description of “credentials” cosmetic
    • “database_weaviate_create_collection” reworded the description of “credentials” cosmetic
    • “hf_endpoint_info” reworded the description of “credentials” cosmetic
    • “ray_stop” reworded the description of “credentials” cosmetic
    • “ml_vllm_lora_sync” reworded the description of “credentials” cosmetic
    • “phoenix_snippet” reworded the description of “credentials” cosmetic
    • “agent_langchain_test” reworded the description of “credentials” cosmetic
    • “mlflow_log_run” reworded the description of “credentials” cosmetic
    • “agent_langgraph_test” reworded the description of “credentials” cosmetic
    • “egress_optimize_staging” reworded the description of “credentials” cosmetic
    • “agent_mem0_search” reworded the description of “credentials” cosmetic
    • “inferx_delete” reworded the description of “credentials” cosmetic
    • “guardrails_generate_config” reworded the description of “credentials” cosmetic
    • “k8s_device_plugin” reworded the description of “credentials” cosmetic
    • “mlflow_register_model” reworded the description of “credentials” cosmetic
    • “mlflow_list_experiments” reworded the description of “credentials” cosmetic
    • “agent_mem0_test” reworded the description of “credentials” cosmetic
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://terradev-mcp.terradev.cloud/sse

TLS unreached
DNSSEC insecure

Validation of terradev-mcp.terradev.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cloud. DS published 7041 13 Verified
terradev.cloud. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
sse https://terradev-mcp.terradev.cloud/sse Unreachable
http (plaintext) http://terradev-mcp.terradev.cloud/sse HTTPS enforced
MCP tools · 277 exposed · ~30,080 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
triggers_enable ~84

Enable or disable a trigger.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

triggers_execute ~85

Manually execute a trigger now.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

triggers_history ~83

Show trigger execution history.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

triggers_list ~82

List configured triggers.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

up ~114

CLI-native provisioning with manifest cache and drift detection. Use --fix-drift to detect and auto-fix drifted infrastructure.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
jobstringyesJob name for manifest tracking

No output schema declared.

No examples provided.

upsert_database ~137

Insert or update data in a database table. Performs upsert operation (insert or update on conflict).

NameTypeReqDescription
connection_idstringyesDatabase connection ID
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
dataobjectyesData to insert/update as key-value pairs
tablestringyesTable name (without prefix)

No output schema declared.

No examples provided.

vllm_analyze ~123

Analyze a running vLLM server's workload and return specific optimization recommendations with before/after comparisons.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
endpointstringyesvLLM endpoint URL (e.g. http://localhost:8000)

No output schema declared.

No examples provided.

vllm_auto_optimize ~122

Automatically optimize vLLM configuration by analyzing workload patterns. Selects optimal settings for the 6 critical knobs based on live endpoint metrics or sample request files.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
modelstringyesModel name

No output schema declared.

No examples provided.

vllm_benchmark ~116

Benchmark a vLLM endpoint with concurrent requests. Returns throughput (req/s), success rate, and total latency.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
endpointstringyesvLLM endpoint URL

No output schema declared.

No examples provided.

vllm_inference ~136

Test inference against a running vLLM endpoint (completions or chat).

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
endpointstringyesvLLM endpoint URL (e.g. http://10.0.0.1:8000)
modelstringyesModel name to use

No output schema declared.

No examples provided.

vllm_info ~124

Get vLLM server info: loaded models, config, and health status.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
endpointstringyesvLLM endpoint URL (e.g. http://10.0.0.1:8000)

No output schema declared.

No examples provided.

vllm_sleep ~123

Put a vLLM server to sleep. Level 1: offload to CPU (fast wake). Level 2: discard weights (minimal RAM).

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
endpointstringyesvLLM endpoint URL

No output schema declared.

No examples provided.

vllm_start ~136

Start a vLLM inference server on a remote instance via SSH/systemd. Supports Multi-LoRA, Sleep Mode, KV Offloading, Speculative Decoding.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
instance_ipstringyesTarget instance IP
modelstringyesHuggingFace model ID

No output schema declared.

No examples provided.

vllm_stop ~102

Stop a vLLM server on a remote instance.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
instance_ipstringyesTarget instance IP

No output schema declared.

No examples provided.

vllm_wake ~116

Wake a sleeping vLLM server. For Level 2 sleep, also reloads weights and resets prefix cache.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
endpointstringyesvLLM endpoint URL

No output schema declared.

No examples provided.

wandb_create_dashboard ~125

Create a custom W&B dashboard with GPU metrics, training loss, and cost panels.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
dashboard_configobjectyesDashboard config (name, panels, metrics)

No output schema declared.

No examples provided.

wandb_create_report ~125

Create a W&B report with custom sections, charts, and narrative text.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
report_configobjectyesReport config (title, sections, metrics, description)

No output schema declared.

No examples provided.

wandb_create_terradev_alerts ~123

Auto-create standard Terradev alerts: GPU cost > budget, utilization < 50%, training loss spike, straggler detection.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

wandb_create_terradev_dashboard ~119

Auto-create a Terradev-specific W&B dashboard with GPU utilization, cost tracking, training metrics, and infrastructure panels.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

wandb_create_terradev_report ~117

Auto-generate a Terradev infrastructure report: GPU costs, provider comparison, training efficiency, and recommendations.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

wandb_dashboard_status ~108

Get comprehensive W&B monitoring overview: dashboards, reports, alerts, active runs.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

wandb_list_projects ~105

List all Weights & Biases projects for the configured entity.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

wandb_list_runs ~119

List runs in a W&B project with status, metrics summary, and config.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
projectstringyesW&B project name

No output schema declared.

No examples provided.

wandb_run_details ~119

Get detailed info, metrics, and artifacts for a specific W&B run.

NameTypeReqDescription
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…
run_idstringyesW&B run ID

No output schema declared.

No examples provided.

wandb_setup_alerts ~131

Set up custom W&B alerts for GPU metrics: cost thresholds, utilization drops, training anomalies.

NameTypeReqDescription
alert_configobjectyesAlert config (metric, threshold, condition, notification_channel)
api_keystringyesW&B API key
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

warm_pool_start ~112

Start the warm pool manager for intelligent model pre-warming. 5 strategies: traffic_based, time_based, priority_based, cost_optimized, latency_optimized.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

warm_pool_status ~96

Get warm pool status: hit rate, cold starts, memory saved, cost saved.

NameTypeReqDescription
credentialsobject–BYOAPI — your own provider credentials as env vars for this call only (never stored). E.g. {"RUNPOD_API_KEY": "..."}, {"AWS_ACCESS_KEY_ID": "...", "AWS_SECRET_ACCESS_KEY": "..."}, or the TERRADEV_<PR…

No output schema declared.

No examples provided.

Install

How do I install the Terradev MCP server?

Terradev is a hosted endpoint at https://terradev-mcp.terradev.cloud/sse, 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 · terradev-mcp.terradev.cloud

# add to Claude Code
claude mcp add --transport http theoddden-terradev 'https://terradev-mcp.terradev.cloud/sse'
Common questions

What is the Terradev MCP server?

Terradev is an MCP server listed in the public MCP registry as io.github.theoddden/terradev. Cross-cloud GPU orchestration CLI. This page covers its hosted endpoint (https://terradev-mcp.terradev.cloud/sse).

Is the Terradev MCP server safe to use?

Terradev scores 72 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 Terradev MCP server expose?

Terradev exposes 277 tools: provision_gpu, preflight_report, preflight_gpu_check, preflight_network_check, local_scan, and 272 more. Their descriptions and schemas cost roughly 30,080 tokens of context every time the server is loaded.

Does the Terradev MCP server require authentication?

Its publisher declares no required credentials for Terradev. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Terradev MCP server still maintained?

Terradev is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Terradev MCP server?

VerifyMCP ran 3 checks on Terradev, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about Terradev: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.