Clousai MCP Server
@clousai/mcp
npm
v0.1.0
Published by @clousai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Model Context Protocol server for the Clous API — entity-resolved SEC/EDGAR filings data for AI agents.
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 − 4 = 96. 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 |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 0
Tools 49
Each tool and what it can reach — statically extracted from the published source.
create_webhook_endpointnetwork egressupdate_monitornetwork egresscreate_monitorno sensitive capabilitycyber_incidentsno sensitive capabilitydelete_monitorno sensitive capabilityextract_filing_sectionno sensitive capabilityfull_text_searchno sensitive capabilityget_8k_eventsno sensitive capabilityget_accountno sensitive capabilityget_company_financialsno sensitive capability
Show 39 more tools ↓
get_crowdfunding_offeringno sensitive capabilityget_eventno sensitive capabilityget_insider_filingno sensitive capabilityget_monitorno sensitive capabilityget_proxy_votesno sensitive capabilityget_subsidiariesno sensitive capabilitylist_eventsno sensitive capabilitylist_filing_documentsno sensitive capabilitylist_monitorsno sensitive capabilitylist_sourcesno sensitive capabilitylist_webhook_deliveriesno sensitive capabilitylist_webhook_endpointsno sensitive capabilityresolve_entityno sensitive capabilitysearch_13f_holdingsno sensitive capabilitysearch_13f_managersno sensitive capabilitysearch_advisersno sensitive capabilitysearch_beneficial_ownershipno sensitive capabilitysearch_board_membersno sensitive capabilitysearch_broker_dealersno sensitive capabilitysearch_compensationno sensitive capabilitysearch_enforcementno sensitive capabilitysearch_filingsno sensitive capabilitysearch_financial_statementsno sensitive capabilitysearch_financialsno sensitive capabilitysearch_form_crsno sensitive capabilitysearch_form_d_raisesno sensitive capabilitysearch_form144no sensitive capabilitysearch_fund_holdingsno sensitive capabilitysearch_fund_providersno sensitive capabilitysearch_iapd_individualsno sensitive capabilitysearch_insider_transactionsno sensitive capabilitysearch_litigationno sensitive capabilitysearch_nt_late_filingsno sensitive capabilitysearch_patent_grantsno sensitive capabilitysearch_private_fund_statsno sensitive capabilitysearch_private_fundsno sensitive capabilitysearch_proxy_officersno sensitive capabilitysearch_trading_suspensionsno sensitive capabilitysearch_whistleblower_awardsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (49 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.1.0 latest |
A 96/100 | 0 | 1.13.0 | 2026-09-08 |
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 @clousai/mcp --onlineMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.