MCP servers › tech.tchin › tchin

MCP server · registry snapshot 2026-11-01 · last tested 2026-11-01

tech.tchin/tchin

by tchin.tech · domain (the registry's namespace rule)Website ↗

Tchin payments (Togo, Benin, Burkina Faso): pay links, account, PDF statements, payment links. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-01version 1.0.0streamable HTTP43 tools

Summary

tech.tchin/tchin is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain tchin.tech. On 2026-11-01 ProtocolProbe connected to it in read-only mode and read its inventory: 43 tools, 1 resource and 4 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Your own values: none declared (not a guarantee)
Sign-in: none needed to open a session
Tools: 43
Last tested: 2026-11-01

Tool list size

12,520 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (43 tools). Counted with Anthropic's token counter on 2026-11-01, from the tool list we read on 2026-11-01. Median across 25,471 counted servers: 2,877 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-01 (tchin.tech), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (supprimer_lien, annuler_lien_retrait). That is our reading of the names; we did not call them. Source: our connection, 2026-11-01.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-11-01
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-11-01 (registry, as of the 2026-11-01 snapshot)
First listed version: 2026-11-01 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-11-01
Package and repository: checked 2026-11-01
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-31, listed on 2026-11-01 with version 1.0.0 (published 2026-11-01).

Source: the official MCP Registry list on 2026-10-31 and on 2026-11-01.

What it is

What does this server offer?

Observed inventory

43tools

1resources

4prompts

None of its 43 tools are described as changing anything. For 43 the reading was uncertain, so no mark is shown.

afficher_lien_tchin
“À APPELER dès que l’utilisateur partage un lien tchin.tech/pay/… ou dit vouloir payer, régler ou voir un paiement Tchin.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- lienstringrequired“L’adresse du lien Tchin (https://tchin.tech/pay/abc123) ou son code (abc123).”
preparer_demande_tchin
“Crée une demande de paiement (une facture) en francs CFA (XOF) au nom d’un compte Tchin désigné par son Tchin ID (pseudo@tchin), puis affiche son formulaire de paiement sécurisé dans la conversation.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
- tchin_idstringrequired“Le Tchin ID du bénéficiaire, par exemple boutique@tchin.”
- montantintegerrequired“Le montant en francs CFA (XOF), sans décimales.”
- motifstring“Facultatif : l’objet du paiement (par exemple « Commande 42 »).”
etat_paiement
“Dit si un paiement Tchin (lien de paiement ou demande de paiement, par son code) est payé (paye), en cours de validation (en_cours) ou encore à payer (a_payer).”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- tokenstringrequired“Le token rendu par afficher_lien_tchin ou preparer_demande_tchin (ou le code d’un lien tchin.tech/pay).”
aide_tchin
“Cherche dans la documentation officielle de Tchin (frais, pays et réseaux, délais, paiements, liens, abonnements, versements, vérification d’identité, API, sécurité) et rend les passages utiles avec …”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- questionstringrequired“La question, en quelques mots (par exemple « frais Mobile Money au Bénin »).”
tchin_feuille
“Réservé à la feuille de paiement Tchin affichée dans la conversation.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- tokenstringrequired
tchin_mobile_money
“Réservé à la feuille de paiement Tchin affichée dans la conversation.”
Publisher declares: read-only no · destructive no · open-world no
6 inputs, 1 required
- tokenstringrequired
- paysstring
- reseaustring
- numerostring
- emailstring
- montantinteger
tchin_suivi
“Réservé à la feuille de paiement Tchin affichée dans la conversation.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
- tokenstringrequired
- suivistring
tchin_crypto
“Réservé à la feuille de paiement Tchin affichée dans la conversation.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 1 required
- tokenstringrequired
- devisestring
- montantinteger
tchin_crypto_etat
“Réservé à la feuille de paiement Tchin affichée dans la conversation.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 1 required
- tokenstringrequired
- jetonstring
- simulerboolean
mon_compte
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
creer_lien_paiement
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 1 required
- titrestringrequired“Ce que le client paie (ex.”
- montantinteger“Montant fixe en F CFA (XOF).”
- descriptionstring“Facultatif : détails affichés sur la page.”
- moyensstring“momo (Mobile Money), crypto, ou both (les deux).”
- testboolean“true = lien de test (aucun argent réel).”
creer_formulaire
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 3 required
- titrestringrequired
- montantintegerrequired“Prix fixe en F CFA (XOF).”
- descriptionstring
- moyensstring“momo (Mobile Money), crypto, ou both (les deux).”
- testboolean
- questionsarrayrequired

Show 31 more tools

mes_liens
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
1 input
- limiteinteger
activer_lien
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- lienstringrequired“L’adresse ou le code du lien.”
- actifbooleanrequired
rapport_ventes
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
- dustring“Premier jour (AAAA-MM-JJ).”
- austring“Dernier jour inclus (AAAA-MM-JJ).”
- modestring“reel (par défaut) : l’argent réel ; test : les opérations de test ; tous.”
detail_paiement
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- referencestringrequired“La référence (token) du paiement, ou le code d’un lien.”
mes_abonnements
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- statutstring
- limiteinteger
mes_retraits
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- limiteinteger
- modestring“reel (par défaut) : l’argent réel ; test : les opérations de test ; tous.”
mes_ventes
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
- limiteinteger
- statutstring
- modestring“reel (par défaut) : l’argent réel ; test : les opérations de test ; tous.”
mes_transactions
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
9 inputs
- genrestring“paiement (reçu), depot, retrait, envoi, recu, deplacement (entre ses soldes pays), cashback, parrainage, epargne, ajustement.”
- sensstring
- statutstring
- paysstring“TG, BJ ou BF.”
- dustring“Premier jour (AAAA-MM-JJ).”
- austring“Dernier jour inclus (AAAA-MM-JJ).”
- modestring“reel (par défaut) : l’argent réel ; test : les opérations de test ; tous.”
- limiteinteger
- pageinteger
bilan_compte
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
- dustring“Premier jour (AAAA-MM-JJ).”
- austring“Dernier jour inclus (AAAA-MM-JJ).”
- modestring“reel (par défaut) : l’argent réel ; test : les opérations de test ; tous.”
releve_pdf
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
7 inputs
- dustring“Premier jour (AAAA-MM-JJ).”
- austring“Dernier jour inclus (AAAA-MM-JJ).”
- genrestring“paiement (reçu), depot, retrait, envoi, recu, deplacement (entre ses soldes pays), cashback, parrainage, epargne, ajustement.”
- sensstring
- statutstring
- paysstring
- modestring“reel (par défaut) : l’argent réel ; test : les opérations de test ; tous.”
detail_transaction
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- referencestringrequired
mon_cashback
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
mon_parrainage
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
mes_coffres
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
mes_prelevements
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
mes_contacts
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
envoyer_argent
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 3 required
- tchin_idstringrequired
- montantintegerrequired“En F CFA.”
- depuisstringrequired“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
- versstring“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
retirer_mobile_money
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 4 required
- depuisstringrequired“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
- paysstring“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
- reseaustringrequired“Le code du réseau (donné par reseaux_retrait).”
- telephonestringrequired
- montantintegerrequired“En F CFA.”
deplacer_argent
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 3 required
- depuisstringrequired“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
- versstringrequired“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
- montantintegerrequired“En F CFA.”
creer_lien_retrait
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
8 inputs, 4 required
- moyenstringrequired
- paysstring“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
- devisestring
- montantnumberrequired“En F CFA pour momo, en unités de la crypto sinon.”
- emailstringrequired
- titrestringrequired
- messagestring
- testboolean
supprimer_application
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
- applicationstringrequired“Le nom ou le numéro de l’application.”
etat_demande
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- demandestringrequired“La référence rendue (D123).”
reseaux_retrait
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- paysstringrequired“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
mes_applications
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
mes_liens_retrait
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
1 input
- limiteinteger
modifier_lien
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
6 inputs, 1 required
- lienstringrequired“L’adresse du lien (https://tchin.tech/pay/…) ou son code.”
- titrestring
- montantinteger“En F CFA ; 0 pour un montant libre.”
- descriptionstring
- moyensstring
- testboolean
supprimer_lien
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
- lienstringrequired“L’adresse du lien (https://tchin.tech/pay/…) ou son code.”
annuler_lien_retrait
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
- lienstringrequired“L’adresse du lien de retrait ou son code.”
creer_application
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 1 required
- nomstringrequired
- descriptionstring
- mobile_moneyboolean
- cryptoboolean
- compte_tchinboolean
- frais_paiementstring
convertir_cashback
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 2 required
- paysstringrequired“TG (Togo), BJ (Bénin) ou BF (Burkina Faso).”
- montantintegerrequired“Le montant en F CFA à recevoir.”
ouvrir_tchin
“Pour l’utilisateur connecté à son compte Tchin, marchand ou particulier (connexion demandée la première fois).”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- pagestringrequired

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-01.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 50% of 107
Tools with a description: 100% of 43
Typical description length: 306 characters

The tool set

Counted from the listing

Tools: 43
Size of the list: about 9,531 tokens for an agent to load (characters ÷ 4)
Naming: 43 of 43 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 43 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-01 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://tchin.tech/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "tchin": {
      "url": "https://tchin.tech/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "tchin": {
      "type": "http",
      "url": "https://tchin.tech/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"tchin","type":"http","url":"https://tchin.tech/mcp"}'

Claude Code

claude mcp add --transport http tchin https://tchin.tech/mcp

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "tchin": {
      "type": "streamableHttp",
      "url": "https://tchin.tech/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "tchin": {
      "httpUrl": "https://tchin.tech/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.tchin]
url = "https://tchin.tech/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "tchin": {
      "url": "https://tchin.tech/mcp"
    }
  }
}

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://tchin.tech/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint tchin.tech/mcp	Session opened	matches	our test · 2026-11-01
No credential declared as required	Opened a session without any credential	matches	our test · 2026-11-01

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-01. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about tech.tchin/tchin

Answered from the data above

Who publishes tech.tchin/tchin?

The registry ties the namespace tech.tchin to the domain tchin.tech; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does tech.tchin/tchin need an API key or sign-in?

It opened a session without any credential on 2026-11-01. The registry entry declares no required credential; no declaration is not a guarantee.

Has tech.tchin/tchin been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-01

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-01, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
442 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 43 tools, 1 resource, 4 prompts.
2,046 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-11-01; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-11-01

MCP capability

prompts, resources, tools, extensions

our test · 2026-11-01

Transport

streamable HTTP

registry · 2026-11-01

Required credentials

none declared

registry · 2026-11-01 · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-11-01

Lifecycle status

active

registry · 2026-11-01

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type · 2026-11-01

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “tech.tchin/tchin: MCP server record.” Data checked 2026-11-01. https://protocolprobe.com/mcp/servers/tech.tchin/tchin

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/tech.tchin/tchin)](https://protocolprobe.com/mcp/servers/tech.tchin/tchin)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology