_ registry / mcp http-sse · checked 3h ago

Gitsim

https://chat.gitsim.com

Registry code: db73dc39a04787ec

api record

Search, order, and manage eSIM data packages for 190+ countries.

from a public catalogue that lists it, not from the operator

endpoint
https://chat.gitsim.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Gitsim live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is Gitsim free to use?
Yes — the hub reached it with no key and no payment.
What tools does Gitsim have?
9 tools: check_data_balance, get_package, search_packages, search_topup_packages, create_order, check_order_status, buy_topup, list_esims, ….
Is Gitsim safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.6%· all time 99.6%

latency
640ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 273 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
payments & commerce shopping & products
used for
  • search esim data packages by country
  • order an esim
  • buy an esim top-up
  • check esim data balance
takes → gives
text → data
tools
7 reads2 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
1 open 8 never probed 1 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_business_context reads open 10h ago

    Get Gitsim product knowledge, pricing model, IP routing guidance, and eSIM fundamentals. Call this FIRST before helping a customer so you understand the product.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • check_data_balance reads unknown 10h ago

    Check remaining data balance on an eSIM. Requires a session key and the eSIM's ICCID.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "session_key",
    "iccid"
  ],
  "properties": {
    "iccid": {
      "type": "string",
      "description": "The ICCID of the eSIM to check"
    },
    "session_key": {
      "type": "string",
      "description": "Session key from a previous tool call"
    }
  }
}
    arguments 18 lines
  • get_package reads unknown 10h ago

    Get details for a specific eSIM package by its ID. No authentication required.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package_id"
  ],
  "properties": {
    "package_id": {
      "type": "string",
      "description": "The package ID to look up"
    }
  }
}
    arguments 13 lines
  • search_packages reads unknown 18h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "country"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Case-insensitive substring match on package name"
    },
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "Page number (1-based, default 1). Each page returns up to 10 results."
    },
    "type": {
      "enum": [
        "daily",
        "regular"
      ],
      "type": "string",
      "description": "\"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."
    },
    "country": {
      "type": "string",
      "maxLength": 2,
      "minLength": 2,
      "description": "ISO 3166-1 alpha-2 country code, e.g. JP, TH, US"
    },
    "ip_route": {
      "enum": [
        "breakout",
        "hk",
        "nonhk"
      ],
      "type": "string",
      "description": "Filter by IP routing type. \"breakout\" = local IP (recommended default), \"hk\" = Hong Kong IP (restricted, cheapest), \"nonhk\" = other breakout (no HK restrictions)"
    },
    "is_regional": {
      "type": "boolean",
      "description": "true = only multi-country/regional packages (e.g. Europe, Asia). false = only single-country packages. Omit for both."
    },
    "max_data_gb": {
      "type": "number",
      "description": "Maximum data in GB. For daily packages this is the per-day amount."
    },
    "min_data_gb": {
      "type": "number",
      "description": "Minimum data in GB. For daily packages this is the per-day amount."
    },
    "max_duration_days": {
      "type": "number",
      "description": "Maximum duration in days"
    },
    "min_duration_days": {
      "type": "number",
      "description": "Minimum duration in days"
    }
  }
}
    arguments 62 lines
  • search_topup_packages reads unknown 18h ago

    Find compatible top-up packages for an existing eSIM. Requires a session key and the eSIM's ICCID.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "session_key",
    "iccid"
  ],
  "properties": {
    "iccid": {
      "type": "string",
      "description": "The ICCID of the eSIM to find top-ups for"
    },
    "session_key": {
      "type": "string",
      "description": "Session key from a previous tool call"
    }
  }
}
    arguments 18 lines
  • create_order moves money unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package_id"
  ],
  "properties": {
    "package_id": {
      "type": "string",
      "description": "The package ID to order"
    },
    "session_key": {
      "type": "string",
      "description": "Session key from a previous tool call. If not provided, a new session is created automatically."
    },
    "referral_code": {
      "type": "string",
      "description": "Optional referral code for a discount"
    }
  }
}
    arguments 21 lines
  • check_order_status reads unknown never probed

    Check the status of the most recent order. Requires a session key from a previous tool call.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "session_key"
  ],
  "properties": {
    "session_key": {
      "type": "string",
      "description": "Session key from a previous tool call"
    }
  }
}
    arguments 13 lines
  • buy_topup moves money unknown never probed

    Purchase a top-up data package for an existing eSIM. Returns a Stripe checkout URL.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "session_key",
    "iccid",
    "package_code"
  ],
  "properties": {
    "iccid": {
      "type": "string",
      "description": "The ICCID of the eSIM to top up"
    },
    "session_key": {
      "type": "string",
      "description": "Session key from a previous tool call"
    },
    "package_code": {
      "type": "string",
      "description": "The package code from search_topup_packages results"
    }
  }
}
    arguments 23 lines
  • list_esims reads unknown 18h ago

    List the customer's delivered eSIMs. Requires a session key from a previous tool call.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "session_key"
  ],
  "properties": {
    "session_key": {
      "type": "string",
      "description": "Session key from a previous tool call"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id db73dc39a04787ec.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/db73dc39a04787ec/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/db73dc39a04787ec/badge.svg)](https://brick.blue/agent/db73dc39a04787ec?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.