SEOAnalytics Read MCP (pesche012/seomcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 12 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

SEOAnalytics Read MCP

Read-only MCP server that retrieves SEO analytics data from WordPress, Google Search Console, and Google Analytics 4, enabling users to fetch posts, search performance, page metrics, and more via natural language.

→ pesche012/seomcp· listed on glama

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

⚡ 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

pesche012

Source: Glama

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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.
🔐
You'll be asked for 6 credentials: WP_APPLICATION_PASSWORD, GSC_ACCESS_TOKEN, GA4_ACCESS_TOKEN, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, MCP_HTTP_TOKEN
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.
configWP_BASE_URLis required
configWP_USERNAME
🔐 secretWP_APPLICATION_PASSWORD5. 発行されたパスワードを に入れます。
configWP_TIMEOUT_SECONDS
🔐 secretGSC_ACCESS_TOKENis required
configGSC_SITE_URLはSearch Consoleに登録されているプロパティ表記と合わせてください。
🔐 secretGA4_ACCESS_TOKEN
configGA4_PROPERTY_IDis required
configGOOGLE_CLIENT_IDOAuth Playgroundを使う場合は、右上の歯車から Use your own OAuth credentials を有効にし、Google Cloud Consoleで作成した と GOOGLE_CLIENT_SECRET を使ってください。
🔐 secretGOOGLE_CLIENT_SECRETOAuth Playgroundを使う場合は、右上の歯車から Use your own OAuth credentials を有効にし、Google Cloud Consoleで作成した GOOGLE_CLIENT_ID と を使ってください。
🔐 secretGOOGLE_REFRESH_TOKENこのMCPサーバーは、 から新しいアクセストークンを自動取得して、Search Console APIとGA4 Data APIを読みます。
configMCP_ALLOWED_ORIGIN
🔐 secretMCP_HTTP_TOKEN必要なら .env に を設定できます。その場合、Web UI側にも次のHTTPヘッダーを設定してください。
configMCP_TRANSPORT
configMCP_HTTP_HOST
configMCP_HTTP_PORT
// quality suggestions

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

12/12 tools missing one or more hints — wp.list_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wp.get_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wp.search_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

5/12 tools referenced in tests (42%)

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

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/pesche012/seomcp)](https://m8ven.ai/mcp/pesche012/seomcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 916222b92581d7608a0c15e6745152e691ffc04d
code hash: 22b245b63b26b865807e6c82876e78b0358c9bd445551c3ef452da582c27dbc5
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