Typesense Cloud
REMOTE · CLOUD.TYPESENSE.ORG
Add fast, typo-tolerant search to your site or app, and run the Typesense clusters behind it.
Available components
Last scanned (5 hours ago)
Scores higher than 26% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 30 Oct 26 −44
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.27 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 29 Oct 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.
- 28 Oct 26 +4
- HTTPS: unverified → pass ▲ security
- 27 Oct 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.
- 25 Oct 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.
- 23 Oct 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.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
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://cloud.typesense.org/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cloud.typesense.org | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 21 Jan 2026 | 18 Feb 2027 | RSA 2048 | SHA256-RSA | cd6c847334aebd48c6eb0dac58215fc |
| SANs: cloud.typesense.org | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cloud.typesense.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 725, 26974 | 8, 8 | Verified |
| typesense.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="missing_token", resource_metadata="https://cloud.typesense.org/.well-known/oauth-protected-resource/mcp/v1", scope="clusters:read metrics:read backups:read clusters:create clusters:configure clusters:restart cluster_parameters:manage search_insights:read data:view data:search data:full_access data:manage_synonyms data:manage_overrides data:manage_presets data:manage_stopwords data:manage_stemming data:manage_analytics_rules data:manage_conversation_models data:manage_natural_language_models"
Bearer error="missing_token", resource_metadata="https://cloud.typesense.org/.well-known/oauth-protected-resource/mcp/v1", scope="clusters:read metrics:read backups:read clusters:create clusters:configure clusters:restart cluster_parameters:manage search_insights:read data:view data:search data:full_access data:manage_synonyms data:manage_overrides data:manage_presets data:manage_stopwords data:manage_stemming data:manage_analytics_rules data:manage_conversation_models data:manage_natural_language_models"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| www-authenticate | Bearer error="missing_token", resource_metadata="https://cloud.typesense.org/.well-known/oauth-protected-resource/mcp/v1", scope="clusters:read metrics:read backups:read clusters:create clusters:configure clusters:restart cluster_parameters:manage search_insights:read data:view data:search data:full_access data:manage_synonyms data:manage_overrides data:manage_presets data:manage_stopwords data:manage_stemming data:manage_analytics_rules data:manage_conversation_models data:manage_natural_language_models" |
Protected resource metadata
| Document | https://cloud.typesense.org/.well-known/oauth-protected-resource/mcp/v1 |
|---|---|
| Retrieved | Yes |
| Resource | https://cloud.typesense.org/mcp/v1 |
| Authorisation server | https://cloud.typesense.org |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cloud.typesense.org/mcp/v1 | Auth required | 401 | |
| http (plaintext) | http://cloud.typesense.org/mcp/v1 | HTTPS enforced | 301 | https://cloud.typesense.org/mcp/v1 |
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 →
create_claimable_cluster Create a free cluster without an account ~221
Creates a free-tier cluster (0.5 GB memory, 2 vCPU burst, one node) with no account and no credential, in the region nearest the caller unless one is given. The answer carries a claim_url for the person you are working with and an access_token for polling; when a ready cluster is on hand it also carries the hostname and an api_key, otherwise status is provisioning and next says what to do (poll get_claimable_cluster about every 60 seconds until ready, and tell the user you are waiting). The api_key reads, writes and searches every collection but cannot delete anything or manage keys; it stays valid for 24 hours after the person claims the cluster. The cluster is deleted 72 hours after creation unless a signed-in person opens the claim_url and claims it into their Typesense Cloud account: give them the link; never open it yourself. Limits per address: 2 clusters per hour, 5 per day.
| Name | Type | Req | Description |
|---|---|---|---|
| region | – | – | A Typesense Cloud region. Defaults to the region nearest the caller. |
No output schema declared.
No examples provided.
get_claimable_cluster Get a claimable cluster's status ~129
Pass the cluster_id from the create answer as id. Returns the cluster's status: provisioning (poll again in about 60 seconds), ready (with hostname and api_key, on every call until the person claims), claimed, or expired. Authenticate with the access_token from create_claimable_cluster as a bearer token. Limit: 120 calls per hour per cluster.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The access_token returned when the claimable cluster was created, sent as a bearer token. It reads that one cluster's status and nothing else. |
| id | string | yes | Cluster reference ID. |
No output schema declared.
No examples provided.
How do I install the Typesense Cloud MCP server?
Typesense Cloud is a hosted endpoint at https://cloud.typesense.org/mcp/v1, 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 · cloud.typesense.org
claude mcp add --transport http org-typesense-typesense-cloud 'https://cloud.typesense.org/mcp/v1'
What is the Typesense Cloud MCP server?
Typesense Cloud is an MCP server listed in the public MCP registry as org.typesense/typesense-cloud. Add fast, typo-tolerant search to your site or app, and run the Typesense clusters behind it. This page covers its hosted endpoint (https://cloud.typesense.org/mcp/v1).
Is the Typesense Cloud MCP server safe to use?
Typesense Cloud scores 37 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 Typesense Cloud MCP server expose?
Typesense Cloud exposes 2 tools: create_claimable_cluster, get_claimable_cluster. Their descriptions and schemas cost roughly 350 tokens of context every time the server is loaded.
Does the Typesense Cloud MCP server require authentication?
Yes. Typesense Cloud 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 Typesense Cloud MCP server still maintained?
Typesense Cloud 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.