MCP server · Audited from source
avansaber-seo-monster MCP server
by avansaber/seo-monsterMIT licenceAudited 26 Oct 2026 · source 5f0302a95a0e
Is it safe? With care — CAUTION, grade B (89/100). The tool list is built at runtime, so we cannot read it from the source. The audit recorded 4 findings (0 critical, 0 high, 2 medium, 2 low). Maintainer's description: SEOMonster: a local, user-credential-driven MCP server for SEO workflows over Google Search Console, GA4, PageSpeed Insights, and Cloudflare. Read-first, open source.
Cite
Cite this page
ModelsAtlas. “avansaber-seo-monster MCP server (avansaber/seo-monster)”. Retrieved 26 Oct 2026. https://modelsatlas.com/mcp/avansaber/seo-monster
Trust audit
Audit 0.4.1 · full source read 26 Oct 2026
4 findings, listed below with the file and line each was found on. Grade A needs a sandboxed behavioural run too; this audit read the source only.
What the source does
- FilesystemNone observedNothing seen in the source
- NetworkDeclared5 observations
- ShellNone observedNothing seen in the source
- DependenciesPinnedNothing floats
- SecretsFoundSee the findings
“Declared” means the server says it does this and the source agrees. Browser, file and shell access are expected of some kinds of server.
Five audit layers
| Layer | What we check | Result |
|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS 1 finding |
L1 Static source | Secrets, path traversal, supply chain | WARN 2 findings |
L2 Instructions | Prompt injection and authority framing in docs and tool descriptions | PASS |
L3 Inventory | Declared tools match the source | PASS 1 finding |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED |
Provenance & runtime
Who published it, and what the audit could and could not run
Provenance
- Repository owner
avansaberOrganizationAccount type recorded when we read the repository. - PackagePublished on PyPI
seo-monsterat version 0.9.3 - LicenceMITFrom the repository, as read at the audited commit.
- Last push7 days agoActivity of the repository when we read it.
- Source commit read5f0302a95a0eThe audit covers exactly this commit, read on 26 Oct 2026.
Runtime
- Sandbox runNot run yetThis audit read the source only; it did not execute the server.
- Tool inventoryBuilt at runtimeThe source declares no tools; the server lists them when a client connects, so we cannot read them.
Every value here is read from the record's own repository and audit.Suggest a correction
Findings (4)
Sorted by severity
MEDIUMHard-coded secretssecret.generic · DESIGN.md:490
Excerpt withheld: it is a secret, and we never print one.
- Why
- No further detail recorded for this rule.
- Fix
- —
MEDIUMHard-coded secretssecret.generic · README.md:816
Excerpt withheld: it is a secret, and we never print one.
- Why
- No further detail recorded for this rule.
- Fix
- —
LOWInventory / provenancemcp.no_tools_extracted · server.json
- Why
- the tool list is enumerated at runtime by tools/list, not declared in source
- Fix
- the page says so rather than showing an empty table
Tools it exposes
None declared in source
The tool list is built at runtime, so we cannot read it from the source.
Install
Package version 0.9.3 · audited commit 5f0302a
Read the findings first. The most severe is Hard-coded secrets (medium) at DESIGN.md.
No connect command is recorded for this server yet. Follow the repository's own instructions, and read the findings above first.
Audit history
- !CAUTION B 89 / 100
First audit ·
5f0302a95a0e
README badge
For maintainers · updates on every re-audit
[](https://modelsatlas.com/mcp/avansaber/seo-monster/)
The badge always shows the latest audit; a maintainer cannot pin an old verdict.
Other ratings
Cited, never blended into our score
No third-party security ratings are recorded for this server yet. When they exist they appear here with their source and date, beside, not inside, our grade.
Questions about avansaber-seo-monster MCP server
What is the avansaber-seo-monster MCP server?
Is avansaber-seo-monster safe to connect to an agent?
What credentials does avansaber-seo-monster need?
How does avansaber-seo-monster run?
How current is this page?
Sources
- avansaber/seo-monster on GitHub — the source we read, its licence, stars and activityObserved · 26 Oct 2026
- ModelsAtlas trust audit — CAUTION verdict for commit 5f0302a95a0eObserved · 26 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What is the avansaber-seo-monster MCP server?
- Is avansaber-seo-monster safe to connect to an agent?
- What credentials does avansaber-seo-monster need?