Bragproof

← Reports

telkomsel-product-mcp

Starts with no setup0.15.1npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing

24tools listed
0hosts contacted
0files written
0.1 sto start
95dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y telkomsel-product-mcp@0.15.1

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 5 returned a result.

telkomsel_get_capabilitiesReturned a result under 0.1 s · 21,104 characters
telkomsel_get_configReturned a result under 0.1 s · 331 characters
telkomsel_get_default_number_hintReturned a result under 0.1 s · 968 characters
telkomsel_list_productsReturned a result under 0.1 s · 1,685 characters
telkomsel_list_segmentsReturned a result under 0.1 s · 2,407 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

3 tools with commands in capitals or very long text
  • Very long description in telkomsel_resolve_intent: 2831 characters or more
  • Very long description in telkomsel_search_packages: 3000 characters or more
  • Gives the agent orders in telkomsel_get_package: package name exists at different quota and price points). IMPORTANT — ref vs id: the Telkomsel API mints a NEW `id` on every request, so an id is only usable for the r

Common and usually harmless: it is how many makers stress how a tool should be used.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

telkomsel_get_capabilities response_format
Describe what this MCP route can answer, so a retrieval router can plan against it instead of guessing.

Read this once, then call the real tools directly. It is free: the manifest is static and makes no upstream request.

Use it to decide:
  - whether this route is the right one for a question (see routingHints)
  - which tool fits a question shape (see tools[].answers)
  - which fields exist, their types and units, and which to request (see entities)
  - which fields must be read from live data rather than an indexed copy (see trust.authoritativeFields)
  - the Indonesian to English vocabulary of the catalogue (see concepts)
  - what belongs in a retrieval index and what must never go in one (see corpus)

Deliberately does not repeat tool names, descriptions or JSON schemas: MCP already publishes those through tools/list. This carries only the semantic layer the protocol has no field for.

Args:
  - response_format (string, optional): "markdown" (default) or "json". Use "json" when a router is consuming it.

Returns (markdown): a readable summary. (json): { route, fieldSelection, entities, subEntities, trust, concepts, routingHints, tools, corpus }
telkomsel_resolve_intent phrase, msisdn, response_format
Turn what a customer says into the query the catalogue actually answers.

A customer types "paket buat nonton". The Telkomsel catalogue never uses the words "nonton buat", and the brands it does name — Prime Video, WeTV, Vision+ — are not words a customer would guess. This tool is the bridge, and it exists because the mapping cannot be derived: a retrieval router knows language, not which apps an Indonesian telco bundles this month.

Every term it returns was validated against the live catalogue and is re-counted on each call, so a term that has disappeared reports 0 instead of silently returning nothing. Where the catalogue has no answer at all — it contains no package described as "unlimited", and never uses the words "murah" or "diskon" — that is reported as an absent term rather than mapped onto something plausible that would return nothing.

A misspelling is read through rather than refused, and what it was read as is reported. The rule is the shape of the error, not its size: a trigger with letters dropped — "nonn" for "nonton", "bejar" for "belajar", "mah" for "murah" — is treated as the typing slip it is, while a word needing substitutions to reach a trigger is left alone, because two substitutions turn "cheap" into "chat" and "gaming" into "going" and neither is a misspelling of the other. Every correction is reported in the corrections field with the characters that went missing, so a reader can judge it instead of trusting it.

Use it before telkomsel_search_packages when the input is a customer's phrasing rather than a filter. Use telkomsel_search_packages directly when you already know the category, price range or quota you want.

Args:
  - phrase (string, required): what the customer said or typed, in Indonesian or English, e.g. "paket buat nonton film", "saya mau ke luar negeri", "paket buat main game".
  - msisdn (string, optional): number to count matches against, since the catalogue is personalised.
  - response_format (string, optional): "markdown" (default) or "json".

Returns (json): { phrase, tokensUsed, fillersDropped, intent, matchedOn, corrections, destination, absent, terms[{term, where, matched}], recommended, suggestedCall, intentCounts, note, otherIntents, provenance }.
A question about the customer's own line rather than a package ("cara cek masa aktif", "masa tenggang", "cek sisa pulsa") matches no intent; when the official FAQ has entries for it, they are returned under faq and suggestedCall is telkomsel_get_faq.
Terms are ALTERNATIVES, not a conjunction: they must be searched one per call and merged. Joining them into a single query would AND them and return nothing — which is exactly the behaviour this tool exists to work around.
Returns an honest no-intent result, with per-token live counts, when nothing in the phrase maps to a catalogue concept.
telkomsel_get_config
Show the current session configuration for this Telkomsel MCP server.

Returns the effective default MSISDN (used by every tool when no explicit `msisdn` argument is given), where that value came from, the built-in fallback, and the valid Telkomsel number prefixes.

Call this first when you need to know which phone number the catalogue queries will be personalised for, or when a tool result looks like it belongs to an unexpected number.

Args:
  - none

Returns (JSON): { defaultMsisdn, defaultMsisdnInternational, source, builtInFallback, validPrefixes }
telkomsel_set_default_msisdn msisdn
Change the phone number this session uses for every Telkomsel catalogue query.

This is the "swap the dummy number" switch. The new number takes effect immediately for all tools that omit an explicit `msisdn` argument, and stays set for the lifetime of the server process. Package availability, prices and recommendations are personalised per number, so changing it genuinely changes the catalogue you get back.

Validates the number first: it must normalise to a Telkomsel mobile prefix (0811, 0812, 0813, 0821, 0822, 0823, 0851, 0852, 0853, 0855) and be 10-13 digits.

Args:
  - msisdn (string, required): e.g. "081234455666", "6281234455666", "0812-3445-5666"

Returns (JSON): { previousMsisdn, defaultMsisdn, defaultMsisdnInternational }
Errors: an actionable message when the number is not a valid Telkomsel mobile number.
telkomsel_check_msisdn msisdn
Validate a phone number and ask Telkomsel what kind of customer it belongs to.

Normalises the input, checks the Telkomsel prefix and length, then queries the live API for the account type. Use this before a catalogue query to confirm the number is a real Telkomsel number and to learn whether it is prepaid (SIMPATI) or postpaid (Halo) — which determines whether prepaid package tools will return anything useful.

Args:
  - msisdn (string, optional): number to check. Omit to check the session default.

Returns (JSON): { input, normalized, international, valid, customerType?, product?, raw? }
Note: this only reads the public product type. It does not authenticate, and it cannot read balances, quota or personal data.
19 more tools
telkomsel_get_default_number_hint
Explain in plain language which number the server is currently using and what that number can and cannot do.

Useful when a user asks "which number is this using?" or "how do I change the number?". This is a documentation tool: it makes no network calls.

Args:
  - none

Returns (string, markdown): current number, how to change it, and its limitations.
telkomsel_list_products segment, type, response_format, fields
List the top-level Telkomsel product catalogue — the 11 products shown under "Produk" on telkomsel.com.

Each entry carries the official display name, the positioning line the site uses ("Prabayar", "Modem WiFi", …), a stable slug for follow-up calls, a segment grouping, the machine-readable family, the official landing-page URL, a summary scraped from that page, and the page's own section headings.

Use this as the entry point when someone asks what Telkomsel sells, wants an overview of the product line, or needs the slug for telkomsel_get_product.

Args:
  - segment (string, optional): case-insensitive substring filter over the segment label, e.g. "Internet Rumah", "Kartu", "Internasional"
  - type (string, optional): exact product family, one of: mobile-prepaid, mobile-postpaid, mobile-prepaid-digital, home-fiber, home-broadband, home-wireless, home-wireless-device, converged, international, network-technology, device-bundling
  - response_format (string, optional): "markdown" (default) or "json"
  - fields (array, optional): which product fields to return. Omit for the recall-preserving default.

Returns: the matching products, plus a `selection` block naming the fields returned and a `provenance` block marking this as a snapshot. Bundled catalogue snapshot: 2026-10-16T06:46:11.893Z.
Note: this is the marketing catalogue. For purchasable packages with live prices, use telkomsel_search_packages.
Provenance: prose here is a snapshot, so it is authoritative for nothing that changes. Pass live=true to telkomsel_get_product for current page text.
telkomsel_get_product id, live, response_format, fields
Get full detail for one Telkomsel product from the catalogue.

Returns the product's identity, the summary scraped from its official landing page, and the page's own section headings (which reveal what the product actually offers, e.g. "Paket Utama Halo", "Pilihan Modem Orbit", "Jangkauan 5G"). With `live: true` it re-reads the page from telkomsel.com right now instead of using the bundled snapshot.

Args:
  - id (string, required): product slug from telkomsel_list_products, e.g. "simpati", "halo", "byu", "indihome", "orbit", "eznet", "eznet-wireless", "telkomsel-one", "roaming", "5g", "bundling". A product display name such as "SIMPATI" also works.
  - live (boolean, optional, default false): re-scrape the official page instead of using the bundled snapshot
  - response_format (string, optional): "markdown" (default) or "json"
  - fields (array, optional): which product fields to return. Omit for the recall-preserving default.

Returns: the product record, plus `live` page data when requested.
Note: the JSON form adds a selection block naming the fields returned, and a provenance block saying whether the text came from the bundled snapshot or a live re-scrape.
Errors: lists the valid ids when the slug does not match.
telkomsel_list_segments
List the segment groupings and product families in the Telkomsel catalogue, with how many products fall into each.

Use this to pick a valid `segment` or `type` value for telkomsel_list_products without guessing.

Args:
  - none

Returns (JSON): { segments: [{ segment, count, products }], types: [{ type, count, products }], total }
telkomsel_product_page_raw path, response_format
Fetch one official telkomsel.com page and return only its headings and summary.

A narrow, live read of the public site. Use it to confirm the bundled catalogue is still accurate, or to look at a page that is not one of the 11 catalogued products (any telkomsel.com path).

Args:
  - path (string, required): site path beginning with "/", e.g. "/promo", "/5G", "/shops/home"
  - response_format (string, optional): "markdown" (default) or "json"

Returns: { url, httpStatus, pageTitle, summary, headings, fetchedAt }
Errors: an actionable message when the path is not on telkomsel.com or the fetch fails.
telkomsel_list_package_categories msisdn
List the live package categories available to a phone number.

These are the categories the Telkomsel purchase flow shows for that specific number (today: "Kamu Banget", "Internet", "Roaming", "Entertainment", "Telepon & SMS"). Availability and ordering are personalised, so two numbers can differ.

Use this before telkomsel_search_packages to pick a valid `category`, or to answer "what kinds of packages can I buy?".

Args:
  - msisdn (string, optional): number to personalise for. Omit for the session default.

Returns (JSON): { msisdn, totalPackages, categories: [{ categoryName, isRoaming, hasRecommendation, icon, subcategoryCount }] }
telkomsel_list_subcategories category, msisdn
List the subcategory labels inside one package category for a phone number.

Subcategories are the bands the site groups packages into, e.g. "Super Seru Promo", "SIMPATI TikTok", "Hot Promo", "Netflix". Use one as the `subcategory` argument of telkomsel_search_packages to narrow a large category.

Args:
  - category (string, required): a category name from telkomsel_list_package_categories, e.g. "Internet". Case-insensitive; a partial name works.
  - msisdn (string, optional): number to personalise for. Omit for the session default.

Returns (JSON): { msisdn, category, subcategories: string[], withPackageCounts: [{ subcategory, packages }] }
Errors: lists the valid categories when the name does not match.
telkomsel_search_packages category, subcategory, query, exclude_query, sort, sort_by, compute, quota, quota_unit, min_quota, max_quota, min_validity_days, max_validity_days, min_price, max_price, roaming_type, region, recommended_only, limit, offset, refresh, msisdn, response_format, fields
Search the live, personalised Telkomsel package catalogue for a phone number.

This is the main catalogue tool. It returns purchasable packages with real current prices, quota, validity and bonus items, personalised to the given number. Filter by category, subcategory, price range, quota range, masa aktif, roaming type, sort order, or a free-text query.

On quota, one thing decides whether a range filter is correct: `totalQuota` is not a data quota. Across the live catalogue it holds three different quantities — 60 forms in GB, 26 in voice minutes, 4 in SMS, and 30 packages empty. So a quota range requires `quota_unit`, defaults to GB, and excludes packages measured in another unit rather than comparing them. `filtersApplied.quotaRange` reports how many it excluded and why. The same field is behind `sort: smallest_quota | largest_quota`, which also only ranks packages measured in the requested unit.

When `category` Every search reads one complete catalogue and filters it here, category or not. The upstream listing returns at most twelve products per subcategory and offers no paging, so filtering through it returns a twelfth of a category and calls it the category: a flat fetch saw 315 of the 600 packages the same endpoint can be made to yield, and 24 roaming packages instead of 262. The catalogue is walked instead — price bands, then quota buckets, then rotated upstream orders, which is the only set of axes the endpoint honours. `filtersApplied.catalogueSize` is how many packages that walk collected; `filtersApplied.catalogueComplete` is false only if some subcategory group was still full at the cap after every axis was spent, and then `filtersApplied.cataloguePartial` names those groups, so a count is never quietly a floor.

A `query` decides membership; the filters decide it too; neither decides order. Results are ranked by Okapi BM25 over the same text the query was matched against, so the packages that actually carry a partner outrank the ones that merely mention it in a description — a search for "netflix" returns the four Netflix packages first rather than the twelve that contain the word. When nothing matches the query as written, it is retried with a small edit distance per term (the standard remedy for an exact index), and `filtersApplied.queryFuzzy` reports both that it happened and what the query was read as. A range spoken in words ("30GB sampai 50GB") is deliberately NOT answered: a text index cannot express BETWEEN, so it returns nothing and the caller should use min_quota/max_quota.

Args:
  - category (string, optional): package category, e.g. "Internet". Run telkomsel_list_package_categories for valid values.
  - subcategory (string, optional): narrow within a category, e.g. "Hot Promo". Requires category.
  - query (string, optional): free text, all words must match. Searched across package name, short and long description, category, subcategory, type, price, bonus names and descriptions. The long description carries the wordin
telkomsel_get_package ref, id, name, include_terms, refresh, msisdn, response_format, fields
Get the full detail of a package: price, quota, validity, every bonus item, description, and optionally the terms and conditions.

Identify the package with `ref` (durable, recommended), `id` (ephemeral: resolvable only while this process still remembers it, and only for the same number), or `name` (may match several variants — the same package name exists at different quota and price points).

IMPORTANT — ref vs id: the Telkomsel API mints a NEW `id` on every request, so an id is only usable for the rest of this server session. `ref` is derived from stable fields (`name@quota@price`) and can be reused in a later session, stored in a note, or handed to a user. Prefer `ref` whenever the value has to outlive the current turn.

Args:
  - ref (string, optional): durable reference from a search result, e.g. "super-seru-promo@53gb@100000".
  - id (string, optional): ephemeral id from a search result for the same number. It can stop resolving; prefer ref.
  - name (string, optional): package name, e.g. "Super Seru Promo". Case-insensitive partial match.
  - include_terms (boolean, optional, default false): include the full terms and conditions text.
  - refresh (boolean, optional, default false): rebuild the catalogue cache before falling back to a full scan.
  - msisdn (string, optional): number to personalise for.
  - response_format (string, optional): "markdown" (default) or "json"
  - fields (array, optional): which package fields to return. Omit for the recall-preserving default; pass ["all"] to include the terms and longdesc HTML.

Provide at least one of `ref`, `id` or `name`.
Returns: the full package record with its bonus breakdown and its `ref`. When a name matches several variants, the cheapest is shown in full and the alternatives are listed.
Note: offerId is the right key for a corpus index, because it does not change when only the price moves. ref is the right key for resolving this exact priced offer again.
Errors: suggests how to find the package when nothing matches.
telkomsel_compare_packages package_refs, msisdn, response_format
Compare two to ten packages side by side on price, quota, validity and what each one includes.

Fetches each package's current record and returns a comparison table plus computed facts: price per GB, the cheapest option, and the largest quota. Useful for "which of these is the best value?" questions.

Identify packages by their `ref` (durable, recommended — the ref column of telkomsel_search_packages) or by a same-session `id`.

Args:
  - package_refs (string[], required): 2-10 refs. A same-session package id also works. A short unique ref prefix, e.g. "super-seru-promo@53gb", is accepted too.
  - msisdn (string, optional): number to personalise for.
  - response_format (string, optional): "markdown" (default) or "json"

Returns (markdown): a comparison table plus a verdict line. (json): { packages, computed: { cheapest, largestQuota, bestValuePerGb } }
Errors: names the refs that were not found and points back at telkomsel_search_packages.
telkomsel_get_filter_options
Return the filter options the Telkomsel purchase flow itself offers: sort orders, the price range inputs, and the quota buckets.

Each option carries the exact `value` string the API expects, so you can pass them straight to telkomsel_search_packages without guessing. Also reports the live roaming-type options.

Args:
  - none

Returns (JSON): { filterSections: [{ sectionName, title, type, defaultValue, items }], roamingTypes: [{ name, value }], quotaBuckets }
Note: makes two read-only GET requests to the Telkomsel API.
telkomsel_list_roaming_countries query, limit, offset
List the destination countries Telkomsel roaming packages cover, in both Indonesian and English.

Use the returned name as the `region` argument of telkomsel_search_packages to find packages for one destination.

Args:
  - query (string, optional): filter by country name in Indonesian or English, e.g. "singapore" matches "Singapura".
  - limit / offset (number, optional): paging, default limit 40.

Returns (JSON): { total, matched, page, countries: [{ original, en }] }
Note: `original` is the Indonesian name, and it is the value the `region` filter of telkomsel_search_packages accepts. `en` is the English name, for matching an English question.
telkomsel_get_offer_break offer, msisdn, response_format, fields
List the featured offer groups Telkomsel promotes, and optionally expand one into its packages.

The offer break is the promotional band the site shows (e.g. "Super Seru", "Seru Internet", "Bisa Bayar Nanti"), each with its own internal list of offer groups such as Promo, Combo, Weekly or RoaMAX.

Args:
  - offer (string, optional): name of an offer group to expand into its packages, e.g. "Seru Internet". Omit to just list the groups.
  - msisdn (string, optional): number to personalise for.
  - response_format (string, optional): "markdown" (default) or "json"
  - fields (array, optional): which package fields to return when expanding an offer.

Returns (JSON): { categories, limit, offers: [{ name, enabled, groups: [...] }] }, plus expansion as { expanded, packageCount, packages, selection, provenance, truncated }
telkomsel_list_credit_options msisdn, response_format
List the pulsa (airtime top-up) denominations offered for a phone number, with the active-period extension each one grants.

Use this when a user asks how much pulsa they can buy or how much extra active period a top-up gives.

Args:
  - msisdn (string, optional): number to personalise for.
  - response_format (string, optional): "markdown" (default) or "json"

Returns (markdown): a table of denominations. (json): { msisdn, total, options }
telkomsel_get_faq product, query, msisdn, response_format
Fetch the official FAQ entries for a Telkomsel product line.

Args:
  - product (string, optional): "simpati" (default) or "halo".
  - query (string, optional): the customer's question, e.g. "cara cek masa aktif". Only the entries whose question shares its words are returned, best first; all of them when none does.
  - msisdn (string, optional): number to personalise for.
  - response_format (string, optional): "markdown" (default) or "json"

Returns: the FAQ content as published on the site. The upstream shape varies, so markdown output is best-effort and json is returned whenever the structure is not a simple question/answer list.
telkomsel_aggregate_packages category, subcategory, query, quota, quota_unit, min_quota, max_quota, min_validity_days, max_validity_days, min_price, max_price, roaming_type, region, recommended_only, top, refresh, msisdn, response_format
Summarise a set of packages instead of listing them.

telkomsel_search_packages answers "which packages match". This answers "what do they cost, and what do I tell a customer about the range" — the questions a single listing cannot, because the answer is a statistic over hundreds of rows and a listing shows twenty-five.

It takes exactly the same filters as telkomsel_search_packages and runs the same pipeline, so an aggregate can never describe a different set of packages than a search for the same filters. Where telkomsel_compare_packages summarises 2-10 packages the caller already named, this summarises everything that matches.

Args:
  - category, subcategory, query, quota, quota_unit, min_quota, max_quota, min_validity_days, max_validity_days, min_price, max_price, roaming_type, region, recommended_only: identical to telkomsel_search_packages.
  - refresh (boolean, optional): rebuild the catalogue cache instead of reusing it.
  - top (number, optional): how many entries in each shortlist, default 5, max 20.
  - msisdn (string, optional): number to personalise for.
  - response_format (string, optional): "markdown" (default) or "json".

Returns (json): { msisdn, matched, filtersApplied, price{min,max,median,mean}, pricePerGb{min,median,considered,excludedNotGb}, quota{byUnit,byBucket}, validityDays{min,max,median,unmeasured}, byCategory, cheapest[], bestValuePerGb[], notes[], provenance }.
Money is integer rupiah. Price per GB is computed only over packages whose allowance is actually measured in GB, and the count it skipped is reported rather than hidden.
telkomsel_site_search query, type, lang, page, response_format
Search the content of telkomsel.com the way its own search box does: promo pages, FAQ entries and news.

This is not the package catalogue. It finds the page that talks about something ("AMI Awards", "Umrah", "Paket Jagoan", "masa tenggang"), with a link and a short snippet. For purchasable packages with prices, use telkomsel_search_packages.

Args:
  - query (string, required): what to look for, 2-100 characters, Indonesian or English
  - type (string, optional): "page" (promo and product pages), "faq" (help answers) or "news" (press releases). Omit for all.
  - lang (string, optional): "id" (default) or "en"
  - page (integer, optional): zero-based page, 16 results each. Read `hasMore` to know whether another exists.
  - response_format (string, optional): "markdown" (default) or "json"

Returns: { query, type, lang, page, results: [{ title, url, description }], hasMore, fetchedAt }
Note: results are cached for 10 minutes and upstream calls are spaced half a second apart; the site asks crawlers to stay off its search, so this is one request per call, never a crawl. A snippet is a lead, not a statement of terms: open the url for the authoritative text.
Errors: an empty result is not an error; it says so and suggests broader words.
telkomsel_latest_content kind, lang, response_format
What telkomsel.com is publishing right now: the newest news and press releases, or the promos on its promo page. Use it to answer "what's new" and "what promos are running".

Args:
  - kind (string, required): "news" or "promo"
  - lang (string, optional): "id" (default) or "en"
  - response_format (string, optional): "markdown" (default) or "json"

Returns: { kind, lang, count, items: [{ title, url, date, category, image, readable }], source, fetchedAt }
  - news items carry a date (ISO); promo items carry a category (SIMPATI, Package, ...) and no date
  - pass an item's url to telkomsel_read_content for the full text; readable is false for a card that links to a page that tool does not open

Note: this is the site's first page only (about 8 items), read live and cached for 15 minutes. A few cards (and some English news cards) link to internal addresses that carry readable: false. For older items or a topic, use telkomsel_site_search. Promo dates and terms are on each promo page, not in the list.
telkomsel_read_content url, response_format
Read one telkomsel.com news article or promo page in full, as text.

A news article returns its headline, publication date and body. A promo returns its period, what it offers, the prize or discount details, how to take part, the FAQ and the terms and conditions, plus whether the period has already ended.

Args:
  - url (string, required): a telkomsel.com address under /about-us/news/ or /promo/ (also /en/...), as returned by telkomsel_latest_content or telkomsel_site_search. Query strings are ignored.
  - response_format (string, optional): "markdown" (default) or "json"

Returns: { kind, title, description, date, readTime, period, periodEnd, expired, body, sections, steps, tags, faq, truncated, url, fetchedAt }
Note: only these two kinds of page are opened, one page per call, cached for an hour. Package pages, other site sections and other hosts are refused. Quote the terms as written; a snippet from search is not a substitute.
Campaign hub pages (one page listing many offers) come back with their description and FAQ only; open the offers they list one by one.
Errors: a missing page, a refused address or a page whose layout could not be read comes back as an error message.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=20
Sourcegithub.com/EgiStr/telkomsel-product-mcp
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-Rxv/T0wHWiDddoyVF3jq6SzNGgkriCKnWnX+EOllecQuOIxcZE47x9EyhF3qCsvuAZsENT2+p47BPUM4hzT6Tw==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/telkomsel-product-mcp.svg)](https://bragproof.smaverk.com/r/telkomsel-product-mcp)

New version out? Ask for a fresh report.