Back to MCP Trust Indexm8ven
C
Warning
74/100
4 days ago

SEO Authority MCP

Provides AI agents with typed SEO tools for domain authority, keyword opportunities, competitor gap analysis, content briefs, site audits, and internal links, backed by Common Crawl graph data and optional x402 payment settlement.

→ forgemeshlabs/seo-authority-mcp· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. 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

forgemeshlabs

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

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: SEO_X402_PRIVATE_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 1 credential: SEO_X402_PRIVATE_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.
configSEO_API_BASENo https://seo.forgemesh.io Backend URL
configSEO_MAX_PAYMENT_USDC"": "0.15"
configSEO_REQUEST_TIMEOUT_MSNo 30000 Upstream timeout, capped at 120 seconds
🔐 secretSEO_X402_PRIVATE_KEY"": "YOUR_DEDICATED_LOW_BALANCE_WALLET_KEY",
// 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

11/11 tools missing one or more hints — get_seo_capabilities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_domain_authority (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); compare_domain_authority (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 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

Only 2/11 tools referenced in tests (18%)

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

Secrets stay with their owner

1 secret/sensitive value flow into network calls (SEO_X402_PRIVATE_KEY → dynamic)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

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 Verified](https://m8ven.ai/badge/mcp/forgemeshlabs-seo-authority-mcp-9niona?variant=verified)](https://m8ven.ai/mcp/forgemeshlabs-seo-authority-mcp-9niona)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: dc233ff282ba63bc6e8c85e9f0dbc53e2926124d
code hash: c8bfb8970172df7d8a4378cb54bfd7b8be2dc11b12cfa8ae50b84f0321ed9339
verified: 8/15/2026, 9:39:06 AM
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