Sora (ikenokazuki/Sora) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 1 tool. No publisher has claimed this listing.

C
Emerging
74/100

Sora

🌤️ 超高速・軽量なWebスクレイピング、ブラウザ操作&日本の日常インフラ(天気・乗換・知恵袋)統合 MCP・REST サーバー

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ikenokazuki

Source: Glama · also listed on github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: API_KEY, WEB_FETCHER_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configADMIN_ALERT_WEBHOOK_URLSQLite, Chromium, Yahoo, 気象庁 (JMA), P2P地震情報, e-Gov への並行疎通確認レポートを返します。異常検知時は が設定されていれば管理者 Webhook へ自動アラート通知を行います。
configALLOW_BROWSER_EVALUATE🛡️ 任意 JavaScript 実行の安全制御スイッチ ():
configALLOW_LOCAL_FETCHtrue の場合、localhost / プライベート IP へのスクレイピングを許可します(SSRF 対策の緩和。テスト用途のみ)
configALLOW_LOCAL_NO_AUTHtrue の場合、X-Forwarded-For / X-Real-IP が付かない直接ローカル接続に限り API キー無しでのアクセスを許可します。リバースプロキシ配下では有効化しないでください
configALL_PROXY標準汎用プロキシ URL(SOCKS5 等)
🔐 secretAPI_KEYWEB_FETCHER_API_KEY が未設定の場合に参照されるフォールバックの認証キー
configCHROME_BINChromium 実行バイナリのパスを明示指定します(未指定時は標準パスと PATH を自動探索)
configCHROME_PATHChromium 実行バイナリのパスを明示指定します(未指定時は標準パスと PATH を自動探索)
configDAILY_REQUEST_LIMITAPI キー別の日次最大リクエスト数(レートリミット制御)
configENABLED_MODULESSora は、目的に応じて 10 個の論理モジュール(全 37 ツール) で構成されています。環境変数 (デフォルト: all、または web,browser,yahoo,life,disaster,watch,music,gov,trade,media)で有効化するカテゴリを自由にカスタマイズ可能です。
configHTTPS_PROXY標準 HTTPS プロキシ URL(Chromium および外部 HTTPS 通信に自動適用)
configHTTP_PROXY標準 HTTP プロキシ URL(Bun fetch および Chromium ヘッドレスブラウザに自動適用)
configMAX_CONCURRENT_BROWSERSSimpleSemaphore により Chromium プロセスの同時実行数(、デフォルト 5)を安全に制御。サーバーの CPU/メモリ枯渇を防止。
configNO_PROXYプロキシバイパス対象ホスト一覧(カンマ区切り、例: localhost,127.0.0.1,.local)
configPUPPETEER_EXECUTABLE_PATHChromium 実行バイナリのパスを明示指定します(未指定時は標準パスと PATH を自動探索)
configSORA_DB_PATHSQLite データベースファイルのパス(キャッシュ・監視対象・ドメイン別 Cookie / localStorage を格納。ファイルは自動で 0600 に制限されます)
configSORA_DEFER_TOOLS包括ツール初期公開ハイブリッドモード(11 コアツール常時露出+特殊ツール遅延発見)を有効化するか。false で全 36 ツール静的一括ロード
configSORA_PROXY_LIST静的fetch用プロキシURLのカンマ区切りリスト。設定時はリクエストごとにランダムでローテーション(SORA_PROXY_URLより優先)。SSRF対策のためMCP/RESTのリクエストパラメータからは指定不可
configSORA_PROXY_URLSora 専用プロキシ URL(最優先)。http://, https://, socks5:// に対応
🔐 secretWEB_FETCHER_API_KEYサーバー側の API 認証キー(最優先)。設定時は Authorization: Bearer <key> または X-API-Key ヘッダーによる認証が必須化されます
configYAHOO_MCP_PATH
configall_proxy標準汎用プロキシ URL(SOCKS5 等)
confighttp_proxy標準 HTTP プロキシ URL(Bun fetch および Chromium ヘッドレスブラウザに自動適用)
confighttps_proxy標準 HTTPS プロキシ URL(Chromium および外部 HTTPS 通信に自動適用)
configno_proxyプロキシバイパス対象ホスト一覧(カンマ区切り、例: localhost,127.0.0.1,.local)
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Dependencies

12 runtime dependencies (2 dev), 1 flagged: puppeteer-core

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

37/37 tools missing one or more hints — scrape (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scrape_batch (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_deep (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +34 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

22/37 tools referenced in tests (59%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

2 calls in production code run through a shell (src/browser_engine.ts:56, src/browser_engine.ts:78)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/ikenokazuki/sora)](https://m8ven.ai/mcp/ikenokazuki/sora)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: fbf2e61d11734127eef88c89603f089324bb5d34
code hash: 12cf0ede99a87b5a1c3432fcce25667800224b547af1ebcb22d61723974b7978
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client