Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,071Paid calls: 1,537Letters: 14Defects: 1,323counted just now
teppi

Server definition

Hash
sha256:57ab78cae82646cb07658386b7550efa602d829242db5d4f590134385f452c8c
What it is
What a remote MCP server returned when asked what it offers: 1 tools

The blob, as servednamed by its sha256

{ "instructions": null, "tools": [ { "description": "Use this when you need to decode and inspect a JWT token without verifying its signature. Returns the full header, payload, and expiration status.\n\n1. header -- algorithm (RS256, HS256, etc.) and token type\n2. payload -- all claims (sub, iss, aud, iat, exp, custom claims)\n3. issuedAt -- human-readable issued date\n4. expiresAt -- human-readable expiry date\n5. isExpired -- boolean indicating if the token has expired\n\nExample output: {\"header\":{\"alg\":\"RS256\",\"typ\":\"JWT\"},\"payload\":{\"sub\":\"user123\",\"exp\":1720000000},\"issuedAt\":\"2025-01-01T00:00:00Z\",\"expiresAt\":\"2025-07-03T00:00:00Z\",\"isExpired\":false}\n\nUse this FOR debugging authentication issues, inspecting token claims before API calls, or verifying token expiry. Use this BEFORE making authenticated requests to check if a token needs refreshing.\n\nDo NOT use for hashing data -- use crypto_generate_hash instead. Do NOT use for base64 encoding/decoding -- use utility_encode_base64 instead. Do NOT use for password analysis -- use security_check_password instead.", "inputSchema": { "properties": { "token": { "description": "The JWT token to decode (format: header.payload.signature)", "type": "string" } }, "required": [ "token" ], "type": "object" }, "name": "security_decode_jwt", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:57ab78cae82646cb07658386b7550efa602d829242db5d4f590134385f452c8c | sha256sum