Logiqical MCP Server
logiqical
npm
v0.5.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: social_messages → bridge_tokens → social_send_message. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow social_messages → bridge_tokens → social_send_message
Tools 91
Each tool and what it can reach — statically extracted from the published source.
bridge_tokensreads sensitive datasocial_messagesingests untrusted inputsocial_send_messagenetwork egressagent_registerno sensitive capabilitybridge_chainsno sensitive capabilitybridge_infono sensitive capabilitybridge_quoteno sensitive capabilitybridge_routesno sensitive capabilitybridge_statusno sensitive capabilitybuy_and_stakeno sensitive capability
Show 81 more tools ↓
call_contractno sensitive capabilitycopy_calculate_ordersno sensitive capabilitycopy_executeno sensitive capabilitycopy_get_positionsno sensitive capabilitydefi_savax_infono sensitive capabilitydefi_savax_quoteno sensitive capabilitydefi_savax_stakeno sensitive capabilitydefi_savax_unstakeno sensitive capabilitydefi_vault_depositno sensitive capabilitydefi_vault_infono sensitive capabilitydefi_vault_quoteno sensitive capabilitydefi_vault_withdrawno sensitive capabilitydex_balanceno sensitive capabilitydex_quoteno sensitive capabilitydex_swapno sensitive capabilitydex_token_infono sensitive capabilitydex_tokensno sensitive capabilityget_addressno sensitive capabilityget_balanceno sensitive capabilityget_balancesno sensitive capabilitylaunchpad_buyno sensitive capabilitylaunchpad_overviewno sensitive capabilitylaunchpad_quoteno sensitive capabilitylaunchpad_recentno sensitive capabilitylaunchpad_sellno sensitive capabilitylaunchpad_tokenno sensitive capabilitymarket_arena_priceno sensitive capabilitymarket_avax_priceno sensitive capabilitymarket_priceno sensitive capabilitymarket_searchno sensitive capabilitymarket_topno sensitive capabilitymarket_trendingno sensitive capabilityperps_arbitrum_usdc_balanceno sensitive capabilityperps_cancel_ordersno sensitive capabilityperps_close_positionno sensitive capabilityperps_deposit_infono sensitive capabilityperps_deposit_usdcno sensitive capabilityperps_ordersno sensitive capabilityperps_place_orderno sensitive capabilityperps_positionsno sensitive capabilityperps_registerno sensitive capabilityperps_registration_statusno sensitive capabilityperps_trading_pairsno sensitive capabilityperps_update_leverageno sensitive capabilityperps_wallet_addressno sensitive capabilitypolicy_budgetno sensitive capabilitypolicy_getno sensitive capabilitypolicy_setno sensitive capabilitysend_avaxno sensitive capabilitysign_messageno sensitive capabilitysignals_fundingno sensitive capabilitysignals_marketno sensitive capabilitysignals_scanno sensitive capabilitysignals_summaryno sensitive capabilitysignals_technicalno sensitive capabilitysignals_whalesno sensitive capabilitysocial_conversationsno sensitive capabilitysocial_create_threadno sensitive capabilitysocial_followno sensitive capabilitysocial_like_threadno sensitive capabilitysocial_meno sensitive capabilitysocial_post_tradeno sensitive capabilitysocial_search_usersno sensitive capabilitysocial_top_usersno sensitive capabilitysocial_unfollowno sensitive capabilitysocial_update_profileno sensitive capabilitysocial_user_by_handleno sensitive capabilitystake_arenano sensitive capabilitystake_infono sensitive capabilityswap_buy_arenano sensitive capabilityswap_quote_buyno sensitive capabilityswap_quote_sellno sensitive capabilityswap_sell_arenano sensitive capabilitytickets_balanceno sensitive capabilitytickets_buyno sensitive capabilitytickets_buy_priceno sensitive capabilitytickets_feesno sensitive capabilitytickets_sellno sensitive capabilitytickets_sell_priceno sensitive capabilitytickets_supplyno sensitive capabilityunstake_arenano sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (91 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.5.0 latest |
A 92/100 | 1 | 1.9.0 | 2026-07-24 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan logiqical --onlineMore in Gaming & Entertainment
Security scan results for the Aether MCP server.
Security scan results for the Bedbook MCP server.
Grade any bet against thousands of play-by-play game simulations: win probability, odds, edge.
Security scan results for the Claudinho MCP server.
Security scan results for the Cpu Game MCP server.
Security scan results for the Dfhack MCP server.