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.

SandBase

REMOTE · API.SANDBASE.AI · 2 COMPONENTS

Connect MCP clients to 2,000+ AI models without managing provider API keys.

+4 this week 75 Trust /100

Last scanned (19 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 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 Security83
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1263 tokens (~180/item across 7 items; 7 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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 72% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 70

    First indexed and scored.

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 21 Nov 2026 · Probed https://api.sandbase.ai/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sandbase.ai CN=YE2,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA384 6930d70b253e8f3530a7fec6da659fa92c2
SANs: *.sandbase.ai, sandbase.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.sandbase.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
sandbase.ai. No DS 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

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.sandbase.ai/v1/mcp Verified 200
http (plaintext) http://api.sandbase.ai/v1/mcp HTTPS enforced 301 https://api.sandbase.ai/v1/mcp
MCP tools · 7 exposed · ~741 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
sandbase_account ~27

Check your SandBase account balance. This call is not billed. Use before expensive operations.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sandbase_discover ~231

Find a model, API, or Agent Service for the task. Call this proactively before writing a scraper, before a generic web fetch for structured data, before telling the user something is inaccessible, and whenever you need image/video/music/speech generation, social media data, search results, web scraping, product/company/people data, embeddings, or a specific third-party model. Supports keyword search (q), type filtering (llm/api/multimodal/embedding/service), and vendor filtering. Discovery is not billed; start here.

NameTypeReqDescription
limitinteger–Maximum results to return (default 20, max 100).
qstring–Short description of what you need (e.g. 'twitter posts', 'text to video', 'gpt-4o', '小红书'). At most 4096 UTF-8 bytes and 64 tokens after normalization.
typestring–Filter by capability type; use service to discover Agent Services.
vendorstring–Filter by vendor slug (e.g. 'openai', 'twitter', 'anthropic').

No output schema declared.

No examples provided.

sandbase_inspect ~79

Inspect a model, API, or Agent Service: input schema, available pricing, and an execution template. Service names are svc_ IDs. Always inspect before running.

NameTypeReqDescription
namestringyesModel name (e.g. 'openai/gpt-4o'), tool name, or Agent Service ID (svc_...) from discover results.

No output schema declared.

No examples provided.

sandbase_run ~148

Execute a model, API, or Agent Service. Sync models return the result directly; async models (image/video/audio jobs) return status running with a run_id — poll sandbase_run_get for the output. Services require arguments.idempotency_key and optionally input; reuse the same key and input on retries. Service acceptance is not completion: poll sandbase_run_get with service_id and run_id. Omit the MCP task parameter for Services.

NameTypeReqDescription
argumentsobjectyesInput matching the inspected schema. For Services: {idempotency_key: string, input?: string}.
namestringyesModel name, tool name, or Agent Service ID (svc_...) to execute.

No output schema declared.

No examples provided.

sandbase_run_cancel ~49

Request cancellation of an Agent Service run; inspect its status afterward.

NameTypeReqDescription
idempotency_keystringyes–
run_idstringyes–
service_idstringyes–

No output schema declared.

No examples provided.

sandbase_run_get ~111

Get async run status and results. For Agent Services supply both service_id and run_id; succeeded, failed, and cancelled are terminal. Session items are paginated: use cursor for subsequent pages; items_available=false means retry output retrieval. Model runs use completed or failed.

NameTypeReqDescription
cursorstring–Session items continuation cursor.
limitinteger––
run_idstringyesThe run ID returned by sandbase_run.
service_idstring–Required for Agent Service runs.

No output schema declared.

No examples provided.

sandbase_runs ~96

List recent model/API calls, or supply service_id to list runs of an Agent Service.

NameTypeReqDescription
limitinteger–Number of recent runs to return (default 10, max 50).
modelstring–Filter by model name (e.g. 'openai/gpt-4o').
offsetinteger––
service_idstring–List runs of this Agent Service instead of model predictions.

No output schema declared.

No examples provided.

Install

How do I install the SandBase MCP server?

SandBase is a hosted endpoint at https://api.sandbase.ai/v1/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.sandbase.ai

# add to Claude Code
claude mcp add --transport http sandbaseai-cli 'https://api.sandbase.ai/v1/mcp'
Common questions

What is the SandBase MCP server?

SandBase is an MCP server listed in the public MCP registry as io.github.sandbaseai/cli. Connect MCP clients to 2,000+ AI models without managing provider API keys. This page covers its hosted endpoint (https://api.sandbase.ai/v1/mcp).

Is the SandBase MCP server safe to use?

SandBase scores 75 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 SandBase MCP server expose?

SandBase exposes 7 tools: sandbase_run_cancel, sandbase_discover, sandbase_inspect, sandbase_run, sandbase_run_get, and 2 more. Their descriptions and schemas cost roughly 741 tokens of context every time the server is loaded.

Does the SandBase MCP server require authentication?

Yes. SandBase 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 SandBase MCP server still maintained?

SandBase is still listed as active in the MCP registry. We last reached this channel on 21 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 SandBase MCP server?

VerifyMCP ran 13 checks on SandBase, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.