Sub Killer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_walletB | Scan a wallet address for active token approvals, recurring payments, and subscription patterns on Monad. Returns a list of detected approvals with risk levels. |
| get_known_protocolsB | Get the list of known DeFi protocols and their risk categories. Use this to identify what a spender address is. |
| identify_spenderA | Identify what a spender address is (protocol name, category, risk level). Useful when scan_wallet returns unknown spenders. |
| check_allowanceA | Check the current allowance a wallet has granted to a specific spender for a specific token. |
| get_contract_statsA | Get user statistics from the SubscriptionKiller smart contract (how many scanned, cancelled, saved). Contract address is optional if deployed contracts are configured. |
| get_contract_subscriptionsB | Get all subscriptions registered in the SubscriptionKiller smart contract for a user. Contract address is optional if deployed contracts are configured. |
| estimate_gas_savingsB | Estimate how much gas money a user saves by using Monad instead of Ethereum for subscription management. |
| get_network_infoA | Get information about the Monad network (RPC, chain ID, gas costs). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_wallet | Comprehensive wallet analysis: scan for approvals, identify risks, suggest actions |
| security_audit | Security-focused audit of a wallet's token approvals |
| compare_networks | Compare gas costs between Monad and Ethereum for subscription management |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Known Protocols Database | Complete list of known DeFi protocols with risk levels |
| Protocol Categories | Available protocol categories (DEX, Lending, Staking, etc.) |
| Deployed Contracts | Deployed SubscriptionKiller contract addresses |
| Monad Testnet Config | Monad testnet RPC, chain ID, explorer URLs |
| Monad Mainnet Config | Monad mainnet RPC, chain ID, explorer URLs |
TDQS
Scored across 8 tools
Tool purposes are mostly distinct, with minor overlap between scan_wallet (detecting approvals and subscriptions) and get_contract_subscriptions (listing subscriptions from a contract). Identify_spender and get_known_protocols are complementary but serve different immediate needs.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., scan_wallet, identify_spender, estimate_gas_savings. No mixed conventions or ambiguous verbs.
With 8 tools, the server is well-scoped for its purpose of scanning wallet subscriptions and allowances on Monad. Each tool covers a necessary function without overloading.
The server covers scanning, identification, allowance checks, contract stats, and gas savings. Missing actionable tools like revoking approvals or cancelling subscriptions, but the stated focus is on monitoring and information.