io.github.PGhannmmn/hash-encoding-direct-credits

Est-ce que io.github.PGhannmmn/hash-encoding-direct-credits est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.PGhannmmn/hash-encoding-direct-credits » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• base64_decode≈ 419 tokens

  Decode a standard Base64 string into UTF-8 text. Use this only when the decoded bytes are expected to be valid UTF-8; this tool is not for arbitrary binary output. Base64 is reversible encoding, not encryption. Costs 1 credit.

  Paramètres, retour & exemple (1)

  Paramètres

  • input · string · requis
    Standard Base64 text to decode, maximum 65,536 characters.

  Exemple d'appel

  {"name": "base64_decode", "arguments": {"input": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• base64_encode≈ 428 tokens

  Encode UTF-8 text as standard Base64. Use this for transport/storage encoding of text bytes; Base64 is reversible encoding, not encryption and not a cryptographic hash. Returns the encoded Base64 string. Costs 1 credit.

  Paramètres, retour & exemple (1)

  Paramètres

  • input · string · requis
    Plain text interpreted as UTF-8, maximum 65,536 characters.

  Exemple d'appel

  {"name": "base64_encode", "arguments": {"input": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_credit_balance≈ 304 tokens

  Check the remaining prepaid API credits for the bearer token configured on this MCP connection. Use this after redeeming a payment when you need to decide whether a protected tool can be called. The bearer token is read from the Authorization header, not from tool arguments. This call is free, does not spend credits, and does not purchase or redeem credits.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_credit_balance", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_payment_info≈ 721 tokens

  Return the complete purchase and redemption instructions for this service's prepaid API credits. Use this before paying or when an agent needs the Base Mainnet network, native USDC contract, receiver address, exact package amount, credit quantity, buyer-gas requirement, or redemption steps. This call is free and does not require a bearer token. It does not return a balance; use get_credit_balance after you already have a redeemed bearer token. This payment scheme is direct USDC credits, not x402.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_payment_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"asset": "texte", "scheme": "texte", "chainId": 1, "network": "texte", "packages": [], "receiver": "texte", "redeemFlow": [], "buyerPaysGas": true, "purchasePath": "texte", "assetDecimals": 1, "x402Compatible": true, "facilitatorRequired": true}}

• hash_sha256≈ 458 tokens

  Create an unkeyed SHA-256 fingerprint of UTF-8 text. Use this for checksums, deduplication, content fingerprints, or integrity comparisons when no shared secret is involved; use hmac_sha256 instead when keyed authentication is required. Returns the 32-byte digest as 64 lowercase hexadecimal characters. Costs 1 credit.

  Paramètres, retour & exemple (1)

  Paramètres

  • input · string · requis
    Text to hash, interpreted as UTF-8, maximum 65,536 characters.

  Exemple d'appel

  {"name": "hash_sha256", "arguments": {"input": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• hash_sha512≈ 460 tokens

  Create an unkeyed SHA-512 fingerprint of UTF-8 text. Use this when a 512-bit digest is specifically required for checksums, fingerprints, or compatibility; use hash_sha256 for the more common 256-bit digest and hmac_sha256 when keyed authentication is required. Returns 128 lowercase hexadecimal characters. Costs 1 credit.

  Paramètres, retour & exemple (1)

  Paramètres

  • input · string · requis
    Text to hash, interpreted as UTF-8, maximum 65,536 characters.

  Exemple d'appel

  {"name": "hash_sha512", "arguments": {"input": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• hmac_sha256≈ 514 tokens

  Authenticate a UTF-8 message with a UTF-8 secret key using HMAC-SHA256. Use this when you need keyed integrity/authentication with a shared secret; use hash_sha256 instead for an unkeyed checksum or fingerprint. Returns the 32-byte HMAC as 64 lowercase hexadecimal characters. Costs 1 credit.

  Paramètres, retour & exemple (2)

  Paramètres

  • key · string · requis
    Secret key interpreted as UTF-8 text, maximum 1,024 characters. Do not pass a hex/base64 key unless those literal characters are the intended key bytes.
  • message · string · requis
    Message interpreted as UTF-8 text, maximum 65,536 characters.

  Exemple d'appel

  {"name": "hmac_sha256", "arguments": {"key": "texte", "message": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• jwt_decode≈ 534 tokens

  Decode a compact JWT's header and payload for inspection without verifying its signature. Use this for debugging or reading claims only; never treat the returned claims as authenticated or trusted. The response always reports signatureVerified=false, even when a signature segment is present. Costs 1 credit.

  Paramètres, retour & exemple (1)

  Paramètres

  • token · string · requis
    Compact JWT string in header.payload.signature form, maximum 8,192 characters.

  Exemple d'appel

  {"name": "jwt_decode", "arguments": {"token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://hash-encoding-001d.qqqa16521-dce.workers.dev/mcp