Gitsim Chat
REMOTE · CHAT.GITSIM.COM · SCANNED AUG 3
Search, order, and manage eSIM data packages for 190+ countries.
Available components
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 →
Endpoint Security63
- 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 7 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 935 tokens (~103/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · chat.gitsim.com
claude mcp add --transport http com-gitsim-chat https://chat.gitsim.com/api/mcp
[mcp_servers.com-gitsim-chat] url = "https://chat.gitsim.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-gitsim-chat": {
"type": "remote",
"url": "https://chat.gitsim.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-gitsim-chat --url https://chat.gitsim.com/api/mcp --transport streamable-http
mcp_servers:
com-gitsim-chat:
url: "https://chat.gitsim.com/api/mcp" {
"mcpServers": {
"com-gitsim-chat": {
"type": "http",
"url": "https://chat.gitsim.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 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.
- 27 Jul 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
- 26 Jul 26 64
First indexed and scored.
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 3 Aug 2026 · Probed https://chat.gitsim.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chat.gitsim.com | CN=YR1,O=Let's Encrypt,C=US | 21 Jul 2026 | 19 Oct 2026 | RSA 2048 | SHA256-RSA | 5f6dd8735b21913b1f1d37c67432241c37f |
| SANs: chat.gitsim.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of chat.gitsim.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| gitsim.com. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chat.gitsim.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://chat.gitsim.com/api/mcp | HTTPS enforced | 308 | https://chat.gitsim.com/api/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.
buy_topup Buy Top-Up ~77
Purchase a top-up data package for an existing eSIM. Returns a Stripe checkout URL.
| Name | Type | Req | Description |
|---|---|---|---|
| iccid | string | yes | The ICCID of the eSIM to top up |
| package_code | string | yes | The package code from search_topup_packages results |
| session_key | string | yes | Session key from a previous tool call |
No output schema declared.
No examples provided.
check_data_balance Check Data Balance ~62
Check remaining data balance on an eSIM. Requires a session key and the eSIM's ICCID.
| Name | Type | Req | Description |
|---|---|---|---|
| iccid | string | yes | The ICCID of the eSIM to check |
| session_key | string | yes | Session key from a previous tool call |
No output schema declared.
No examples provided.
check_order_status Check Order Status ~43
Check the status of the most recent order. Requires a session key from a previous tool call.
| Name | Type | Req | Description |
|---|---|---|---|
| session_key | string | yes | Session key from a previous tool call |
No output schema declared.
No examples provided.
create_order Create Order ~100
Create an order for an eSIM package. Returns a Stripe checkout URL where the user can pay. Requires a session key (from a previous tool call's structuredContent) or creates one automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| package_id | string | yes | The package ID to order |
| referral_code | string | — | Optional referral code for a discount |
| session_key | string | — | Session key from a previous tool call. If not provided, a new session is created automatically. |
No output schema declared.
No examples provided.
get_business_context Get Business Context ~41
Get Gitsim product knowledge, pricing model, IP routing guidance, and eSIM fundamentals. Call this FIRST before helping a customer so you understand the product.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_package Get Package Details ~38
Get details for a specific eSIM package by its ID. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| package_id | string | yes | The package ID to look up |
No output schema declared.
No examples provided.
list_esims List eSIMs ~42
List the customer's delivered eSIMs. Requires a session key from a previous tool call.
| Name | Type | Req | Description |
|---|---|---|---|
| session_key | string | yes | Session key from a previous tool call |
No output schema declared.
No examples provided.
search_packages Search eSIM Packages ~464
Search for eSIM data packages by country. Returns up to 10 packages per page sorted by price. Use the page parameter to paginate. No auth required. Call get_business_context first to understand IP routing and package types. Package types: - "regular": Fixed data pool (e.g. 3GB for 30 days). Best for most travelers. - "daily": Data resets each day (e.g. 2GB/day for 5 days). Good for short trips with predictable daily usage. Top-up days are available. IP routing (important for Asia): - "breakout": Local IP in destination country. Best for streaming, banking, social media. ALWAYS recommend by default. - "hk": Hong Kong IP. Cheapest but TikTok app and Facebook app are BLOCKED. - "nonhk": Third-country IP (UK, Singapore). No HK restrictions but IP won't match destination.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. JP, TH, US |
| ip_route | string | — | Filter by IP routing type. "breakout" = local IP (recommended default), "hk" = Hong Kong IP (restricted, cheapest), "nonhk" = other breakout (no HK restrictions) |
| is_regional | boolean | — | true = only multi-country/regional packages (e.g. Europe, Asia). false = only single-country packages. Omit for both. |
| max_data_gb | number | — | Maximum data in GB. For daily packages this is the per-day amount. |
| max_duration_days | number | — | Maximum duration in days |
| min_data_gb | number | — | Minimum data in GB. For daily packages this is the per-day amount. |
| min_duration_days | number | — | Minimum duration in days |
| name | string | — | Case-insensitive substring match on package name |
| page | integer | — | Page number (1-based, default 1). Each page returns up to 10 results. |
| type | string | — | "daily" = data resets each day (e.g. 2GB/day for 5 days, can top-up days). "regular" = fixed data pool for the full duration. Omit for both. |
No output schema declared.
No examples provided.
search_topup_packages Search Top-Up Packages ~68
Find compatible top-up packages for an existing eSIM. Requires a session key and the eSIM's ICCID.
| Name | Type | Req | Description |
|---|---|---|---|
| iccid | string | yes | The ICCID of the eSIM to find top-ups for |
| session_key | string | yes | Session key from a previous tool call |
No output schema declared.
No examples provided.