ingravity-security
Related Servers
Alternatives to ingravity-security
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceLocal stdio MCP server for x402-powered paid crypto intelligence, decision verification, and agent automation search over USDC micropayments on Base.707 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.MIT

tereno-mcpofficial
AlicenseNot gradedqualityCmaintenanceMCP server for verifying blockchain safety on Base via x402, with free pricing/receipt tools and paid per-call guard, contract, and metadata checks settled in USDC.458 npmMIT- AlicenseAqualityBmaintenanceFully autonomous, crypto-monetized MCP server on the Base network. Provides premium smart contract auditing, patching, and token data arbitrage using the x402 micro-transaction protocol.9MIT
- AlicenseNot gradedqualityCmaintenanceA stdio MCP server that exposes guard_token, guard_tx, and guard_address endpoints for pre-execution security and trust evaluation of tokens, transactions, and addresses on Base.MIT
- AlicenseBqualityBmaintenanceMCP server exposing x402 Bazaar's paid Base APIs (token risk/honeypot, prices, gas, wallet intel, tx decode + AI utilities) as agent tools. Your agent pays per call in USDC over x402 — no API keys, no signup.17123 npmMIT
TDQS
Scored across 9 tools
Most tools target clearly distinct artifacts: local calldata encode, local calldata decode, address gate, tx firewall, token scan, DeFi math, single-contract audit, multi-contract dossier, and exploit simulation. The only real overlap is among the three audit-style tools (auditSolidityContract vs generateMultiContractProtocolDossier vs simulateDeepExploitAndWhitehatBounty), which descriptions do disambiguate via scope (single vs 1-20 contracts vs exploit simulation) and payload type. Descriptions also include explicit cross-references (decode says 'use inspectEvmTransactionFirewall for live risk verdicts'), which further reduces misselection.
All nine tools use the same ingravity_ prefix and verb-first camelCase, with descriptive multi-word object names. Minor deviations exist: internal word order varies (encodeErc8021Calldata vs fastPingAddressSafety, which starts with an adjective rather than a verb) and some names append a risk-domain qualifier. Overall still highly predictable.
Nine tools is well within a comfortable scope, and each appears to map to a distinct endpoint or local capability with a distinct job (no duplicate wrappers of the same API route). No padding or thin 1-2 tool surface.
The domain (EVM security triage, contract auditing, and transaction safety) is covered end to end: pre-trade address gating, calldata encode/decode, live tx firewall, token rug scanning, DeFi math, and static/dynamic audits. Gaps remain around approval/allowance enumeration and a standalone revocation builder (revocation bundles only appear embedded as unsigned output), EIP-712/permit phishing verification, and detailed per-address risk reporting beyond the binary SAFE/DANGER gate.