Tulimoa
REMOTE · MCP.TULIMOA.COM
Find curated AI and MCP tools in the Tulimoa directory; submit yours free with a badge or for $5.
Available components
Last scanned (16 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2717 tokens (~543/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
- 2 Nov 26 +1
- Stability: fail → pass ▲ security
- Tool “edit_listing” rewrote its description, which is the text the model reads security
- Tool “submit_listing” rewrote its description, which is the text the model reads security
- Schema quality: 356 → 543 ▼ functional
- Tool coverage: 66% → 79% ▲ functional
- Server version: 1.4.0 → 1.5.0 functional
- “edit_listing” added an optional parameter “content_blocks” cosmetic
- “edit_listing” added an optional parameter “country” cosmetic
- “edit_listing” added an optional parameter “demo_url” cosmetic
- “edit_listing” added an optional parameter “docs_url” cosmetic
- “edit_listing” added an optional parameter “founded_year” cosmetic
- “edit_listing” added an optional parameter “gallery_captions” cosmetic
- “edit_listing” added an optional parameter “gallery_urls” cosmetic
- “edit_listing” added an optional parameter “notable_customers” cosmetic
- “edit_listing” added an optional parameter “open_source” cosmetic
- “edit_listing” added an optional parameter “team_size” cosmetic
- “submit_listing” added an optional parameter “content_blocks” cosmetic
- “submit_listing” added an optional parameter “demo_url” cosmetic
- “submit_listing” added an optional parameter “docs_url” cosmetic
- “submit_listing” added an optional parameter “founded_year” cosmetic
- “submit_listing” added an optional parameter “gallery_captions” cosmetic
- “submit_listing” added an optional parameter “gallery_urls” cosmetic
- “submit_listing” added an optional parameter “notable_customers” cosmetic
- “submit_listing” added an optional parameter “open_source” cosmetic
- “submit_listing” added an optional parameter “team_size” cosmetic
- “submit_listing” added an optional parameter “test_access” cosmetic
- “submit_listing” added an optional parameter “test_note” cosmetic
- “submit_listing” added an optional parameter “test_request” cosmetic
- “submit_listing” added an optional parameter “test_x_handle” cosmetic
- “edit_listing” reworded the description of “logo_url” cosmetic
- “edit_listing” reworded the description of “mcp_server_url” cosmetic
- “edit_listing” reworded the description of “slug” cosmetic
- “edit_listing” reworded the description of “url” cosmetic
- “submit_listing” reworded the description of “agent_interfaces” cosmetic
- “submit_listing” reworded the description of “country” cosmetic
- “submit_listing” reworded the description of “logo_url” cosmetic
- “submit_listing” reworded the description of “mcp_server_url” cosmetic
- “submit_listing” reworded the description of “name” cosmetic
- “submit_listing” reworded the description of “short_description” cosmetic
- “submit_listing” reworded the description of “url” cosmetic
- “submit_listing” reworded the description of “visibility” cosmetic
- “submit_listing” reworded the description of “x_post_opt_in” cosmetic
- “edit_listing” dropped the optional parameter “tags” cosmetic
- “submit_listing” dropped the optional parameter “tags” cosmetic
- 3 Oct 26 0
- Tool “get_listing” rewrote its description, which is the text the model reads security
- Tool “submit_listing” rewrote its description, which is the text the model reads security
- Tool coverage: 73% → 66% ▼ functional
- Schema quality: 166 → 356 ▼ functional
- “submit_listing” added a required parameter “ai_usage”, so existing callers break ▼ functional
- “submit_listing” added a required parameter “visibility”, so existing callers break ▼ functional
- Server version: 1.3.0 → 1.4.0 functional
- “edit_listing” added an optional parameter “agent_interfaces” cosmetic
- “edit_listing” added an optional parameter “ai_usage” cosmetic
- “edit_listing” added an optional parameter “certifications” cosmetic
- “edit_listing” added an optional parameter “data_region” cosmetic
- “edit_listing” added an optional parameter “founder_x_handles” cosmetic
- “edit_listing” added an optional parameter “gdpr_dpa” cosmetic
- “edit_listing” added an optional parameter “hosting_provider” cosmetic
- “edit_listing” added an optional parameter “launch_hook” cosmetic
- “edit_listing” added an optional parameter “mcp_auth” cosmetic
- “edit_listing” added an optional parameter “mcp_docs_url” cosmetic
- “edit_listing” added an optional parameter “mcp_server_url” cosmetic
- “edit_listing” added an optional parameter “model_source” cosmetic
- “edit_listing” added an optional parameter “pricing_detail” cosmetic
- “edit_listing” added an optional parameter “trains_on_customer_data” cosmetic
- “edit_listing” added an optional parameter “x_handle” cosmetic
- “submit_listing” added an optional parameter “agent_interfaces” cosmetic
- “submit_listing” added an optional parameter “certifications” cosmetic
- “submit_listing” added an optional parameter “data_region” cosmetic
- “submit_listing” added an optional parameter “founder_x_handles” cosmetic
- “submit_listing” added an optional parameter “gdpr_dpa” cosmetic
- “submit_listing” added an optional parameter “hosting_provider” cosmetic
- “submit_listing” added an optional parameter “launch_hook” cosmetic
- “submit_listing” added an optional parameter “mcp_auth” cosmetic
- “submit_listing” added an optional parameter “mcp_docs_url” cosmetic
- “submit_listing” added an optional parameter “mcp_server_url” cosmetic
- “submit_listing” added an optional parameter “model_source” cosmetic
- “submit_listing” added an optional parameter “pricing_detail” cosmetic
- “submit_listing” added an optional parameter “trains_on_customer_data” cosmetic
- “submit_listing” added an optional parameter “withdrawal_consent” cosmetic
- “submit_listing” added an optional parameter “x_handle” cosmetic
- “submit_listing” added an optional parameter “x_post_opt_in” cosmetic
- Tool “submit_listing” changed its title: Submit a SaaS listing to the Tulimoa directory → Submit an AI or MCP tool to the Tulimoa directory cosmetic
- 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
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://mcp.tulimoa.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tulimoa.com | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4491621acd278d2b0ef61e1652f39f43 |
| SANs: tulimoa.com, mcp.tulimoa.com, *.mcp.tulimoa.com | ||||||
| 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 mcp.tulimoa.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tulimoa.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tulimoa.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tulimoa.com/mcp | HTTPS enforced | 301 | https://mcp.tulimoa.com/mcp |
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 →
edit_listing Edit one of your own Tulimoa listings ~859
Update fields of a listing you own (by slug), with the same fields and rules as the web editor. Only the fields you pass change. Changes to a live listing show right away and are checked by the team afterwards. A changed MCP endpoint on a live listing sends it back into review. Editing a rejected listing resubmits it for review when the rejection reason allows it (not after spam, duplicate, not a product or the listing limit). The Tulimoa badge is re-checked on every edit. Every listing needs a logo: pass logo_url to replace it (required if it has none). gallery_urls and content_blocks replace the whole list. Requires a write-scoped Tulimoa login.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_interfaces | array | – | – |
| ai_usage | string | – | 40 to 600 characters, ideally in English: how the software uses AI, or what agents can do with it. Be concrete, not salesy. Submissions without a clear AI or agent angle are rejected. |
| category | string | – | – |
| certifications | array | – | – |
| content_blocks | array | – | Optional profile sections, like in the web form. type: long_description (max 600 chars), ideal_for, not_for, key_features (one feature per line, 5 to 10 lines, max 600), use_cases, integrations (comm… |
| country | string | – | ISO-3166-1 alpha-2 code of the company's HQ. |
| data_region | string | – | Where customer data is hosted: eu (in the EU by default), eu-option (an EU region can be selected), non-eu, self-hosted (runs at the customer). Listings with EU hosting also appear on tulimoa.com/mcp… |
| demo_url | string | – | Optional demo or video URL. |
| docs_url | string | – | Optional documentation URL. |
| founded_year | integer | – | Optional founding year. |
| founder_x_handles | array | – | – |
| gallery_captions | array | – | Optional captions for gallery_urls, same order, max 120 chars each. |
| gallery_urls | array | – | Optional screenshots, up to 5 public https image URLs (PNG, JPEG, WebP, GIF or AVIF, max 10 MB each). The first one is the hero image. Tulimoa scales them to max 1280 px and stores them as WebP. Imag… |
| gdpr_dpa | boolean | – | – |
| hosting_provider | string | – | – |
| launch_hook | string | – | – |
| logo_url | string | – | New logo. Public https URL of the company logo: PNG, JPEG, WebP, GIF or AVIF, at least 64 px, max 10 MB. A square icon works best. Tulimoa downloads it, scales it to max 512 px and stores it as WebP.… |
| mcp | boolean | – | – |
| mcp_auth | array | – | – |
| mcp_docs_url | string | – | – |
| mcp_server_url | string | – | MCP endpoint. Changing it on a live listing sends it back into review. |
| model_source | string | – | – |
| name | string | – | – |
| notable_customers | string | – | Optional notable customers, e.g. 'Acme, Globex'. |
| open_source | boolean | – | Optional: the software is open source. |
| pricing_detail | string | – | – |
| pricing_model | string | – | – |
| short_description | string | – | – |
| slug | string | yes | Slug of YOUR listing to edit (from submit_listing or get_listing). |
| team_size | string | – | Optional team size: 1, 2-10, 11-50, 51-250 or 250+. |
| trains_on_customer_data | string | – | – |
| url | string | – | The product's own website (http or https). |
| x_handle | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| back_in_review | boolean | yes | true = the edit sent the listing (back) into review. |
| badge_verified | boolean | yes | – |
| id | string | yes | Listing id. |
| slug | string | yes | – |
| status | string | yes | Status after the edit: approved (live), pending (in review) or rejected. |
No examples provided.
get_listing Get one SaaS listing ~93
Fetch full detail of a single Tulimoa listing by its slug: long description, how it uses AI (ai_usage), features, use cases, integrations, pricing detail, data region and EU hosting, model source, certifications, and links. Use after search_listings when the user wants depth on a specific tool.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The listing's URL slug, e.g. 'acme-crm'. |
| Name | Type | Req | Description |
|---|---|---|---|
| listing | object | yes | Full listing row (detail projection, see DETAIL_SELECT). |
No examples provided.
list_categories List directory categories ~39
List the category ids and labels used to classify Tulimoa listings. Call this first when you need a valid `category` value for search_listings.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
No examples provided.
search_listings Search SaaS listings ~198
Find SaaS tools in the Tulimoa directory that an AI agent or team can plug into. Discover tools by topic, category, pricing, MCP support, or EU hosting. Returns only approved, published listings. Use this for any 'find/recommend a tool for X' request, then call get_listing for full detail on a specific result.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict to one category id. Call list_categories for valid ids. |
| eu_only | boolean | – | true = only tools whose company country is in the EU. |
| limit | integer | – | Max results (1-50, default 20). |
| mcp | boolean | – | true = only tools that expose their own MCP server. |
| pricing_model | string | – | Restrict to a pricing model. |
| query | string | – | Free-text terms matched against the listing name and short description. |
| sort | string | – | Result order. Default: popular. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results returned. |
| results | array | yes | Lean listing rows; call get_listing(slug) for full detail. |
No examples provided.
submit_listing Submit an AI or MCP tool to the Tulimoa directory ~1,528
Create a new listing in the Tulimoa directory on behalf of the authenticated user, with the same fields and rules as the web form (https://tulimoa.com/submit/guidelines): AI or MCP software with its own website, the user's own product, at most 2 active listings per account. It starts as 'pending' and is reviewed by hand. Required: logo_url and ai_usage (how the software uses AI or what agents can do with it). Choose how it goes live with `visibility`: 'badge' (free; the Tulimoa badge must already be on the website, this tool checks it) or 'launch' ($5 one-time, no badge, reviewed first, refunded if rejected). For 'launch' ask the user for consent and pass withdrawal_consent: true; the result has a checkout_url the user opens to pay. Optional fields match the form: gallery, content blocks, founding year, team size, demo and docs links, data points, X handles and a test request. A website that is already listed cannot be submitted again. Use list_categories first to pick a valid category id. Requires a write-scoped Tulimoa login.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_interfaces | array | – | Optional: other ways agents can use it (api, cli, sdk, webhooks). |
| ai_usage | string | yes | Required, 40 to 600 characters, ideally in English: how the software uses AI, or what agents can do with it. Be concrete, not salesy. Submissions without a clear AI or agent angle are rejected. |
| category | string | yes | One category id. Call list_categories for valid ids. |
| certifications | array | – | Optional: soc2, iso27001, hipaa. |
| content_blocks | array | – | Optional profile sections, like in the web form. type: long_description (max 600 chars), ideal_for, not_for, key_features (one feature per line, 5 to 10 lines, max 600), use_cases, integrations (comm… |
| country | string | yes | ISO-3166-1 alpha-2 code of the company's HQ, e.g. DE. Same list as the web form. |
| data_region | string | – | Optional. Where customer data is hosted: eu (in the EU by default), eu-option (an EU region can be selected), non-eu, self-hosted (runs at the customer). Listings with EU hosting also appear on tulim… |
| demo_url | string | – | Optional demo or video URL. |
| docs_url | string | – | Optional documentation URL. |
| founded_year | integer | – | Optional founding year. |
| founder_x_handles | array | – | Optional founder X handles (max 4). |
| gallery_captions | array | – | Optional captions for gallery_urls, same order, max 120 chars each. |
| gallery_urls | array | – | Optional screenshots, up to 5 public https image URLs (PNG, JPEG, WebP, GIF or AVIF, max 10 MB each). The first one is the hero image. Tulimoa scales them to max 1280 px and stores them as WebP. Imag… |
| gdpr_dpa | boolean | – | Optional: a GDPR data processing agreement (DPA) is available. |
| hosting_provider | string | – | Optional hosting provider and location, e.g. 'Hetzner, Falkenstein'. |
| launch_hook | string | – | Launch package with welcome post: one sentence why the tool matters (max 140 chars, English). |
| logo_url | string | yes | Required. Public https URL of the company logo: PNG, JPEG, WebP, GIF or AVIF, at least 64 px, max 10 MB. A square icon works best. Tulimoa downloads it, scales it to max 512 px and stores it as WebP. |
| mcp | boolean | yes | true = this tool exposes its own MCP server. |
| mcp_auth | array | – | Only if mcp is true: how agents connect (oauth, api). Empty = no auth. |
| mcp_docs_url | string | – | Only if mcp is true: link to the MCP docs. |
| mcp_server_url | string | – | Only if mcp is true: endpoint URL of the MCP server (e.g. .../mcp). |
| model_source | string | – | Optional: which AI models (own, open-weight, provider, mixed, none). |
| name | string | yes | Product name (max 60 chars). |
| notable_customers | string | – | Optional notable customers, e.g. 'Acme, Globex'. |
| open_source | boolean | – | Optional: the software is open source. |
| pricing_detail | string | – | Optional price detail, e.g. 'from $10/month'. |
| pricing_model | string | yes | Pricing model (required): free | freemium | paid | lifetime. |
| short_description | string | yes | One-line pitch (max 300 chars), ideally in English. |
| team_size | string | – | Optional team size: 1, 2-10, 11-50, 51-250 or 250+. |
| test_access | string | – | Test request only: a trial link or promo code; the test says so if access was given. |
| test_note | string | – | Test request only: what the tester should look at. |
| test_request | boolean | – | Optional: ask Florian to test the tool by hand (about an hour with a real account; result goes on the listing, on X and into the weekly Radar, including what is missing). Free for now, no right to a… |
| test_x_handle | string | – | Test request only: the submitter's X handle, to tag them and ask questions. |
| trains_on_customer_data | string | – | Optional: trains on customer data (no, opt-out, yes). |
| url | string | yes | The product's own website (http or https). A marketplace page or an app-store-only app is not accepted. |
| visibility | string | yes | How the listing goes live (required). 'badge' = free: the Tulimoa badge must ALREADY be embedded on the product website; this tool checks the page and refuses the badge route without it (the error re… |
| withdrawal_consent | boolean | – | Required (true) for visibility 'launch'. Only set it after the user agrees: Tulimoa starts the review right away, the right of withdrawal ends once the listing is live, and a rejected listing gets th… |
| x_handle | string | – | Optional company X handle, e.g. @acme. |
| x_post_opt_in | boolean | – | Launch package only: a free welcome post on X after approval. Needs launch_hook and at least one X handle. |
| Name | Type | Req | Description |
|---|---|---|---|
| badge_html | object | – | Badge route only: the badge HTML (light = for dark backgrounds, dark = for light backgrounds). Keep it on the site. |
| badge_verified | boolean | yes | true = the Tulimoa badge was found on the website. |
| checkout_url | string | – | Launch package only: opens the Polar checkout (Tulimoa login needed). |
| id | string | yes | Listing id. |
| manage_url | string | yes | Dashboard page for status, badge check and payment. |
| next_step | string | yes | What the user has to do now. |
| slug | string | yes | Final slug (may carry a conflict suffix). |
| status | string | yes | – |
| test_requested | boolean | yes | true = a hand test was requested. |
| visibility | string | yes | – |
No examples provided.
How do I install the Tulimoa MCP server?
Tulimoa is a hosted endpoint at https://mcp.tulimoa.com/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 · mcp.tulimoa.com
claude mcp add --transport http com-tulimoa-platform 'https://mcp.tulimoa.com/mcp'
What is the Tulimoa MCP server?
Tulimoa is an MCP server listed in the public MCP registry as com.tulimoa/platform. Find curated AI and MCP tools in the Tulimoa directory; submit yours free with a badge or for $5. This page covers its hosted endpoint (https://mcp.tulimoa.com/mcp).
Is the Tulimoa MCP server safe to use?
Tulimoa 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 Tulimoa MCP server expose?
Tulimoa exposes 5 tools: search_listings, get_listing, list_categories, submit_listing, edit_listing. Their descriptions and schemas cost roughly 2,717 tokens of context every time the server is loaded.
Does the Tulimoa MCP server require authentication?
No. We connected to Tulimoa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tulimoa MCP server still maintained?
Tulimoa 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 Tulimoa MCP server?
VerifyMCP ran 12 checks on Tulimoa, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Tulimoa: Authorization. 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.