Clean scanStatic scanned
Lets your agent query, update and manage MongoDB databases and set up MongoDB Atlas clusters.
458.4k installs/moApache-2.0
N Seo
jeremylumanbailey · MCP server
Helps you grow organic traffic to your own sites across classic search, answer engines and AI assistants that cite sources. It pulls Search Console and GA4 data into local files, probes live sites for problems such as soft 404s and blocked AI crawlers, and turns the results into a ranked queue of concrete actions. A model you choose writes the proposals, and a read-only MCP server lets a coding agent work the queue. It needs a Google service account with access to both consoles.
Written by ooruby from the README of n-seo 0.7.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
You get a ranked list of concrete SEO and AI-search fixes drawn from your own Search Console and GA4 data, and your coding agent can work through it.
What you could do with it
- Ask your agent what to fix first this week and have it work through the ranked queue of SEO actions.
- Find pages that Search Console reports as discovered but never crawled, or as soft 404s.
- Check whether your sites block AI crawlers or serve pages that need JavaScript to show any content.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (src/config.ts:14)
- synchronous shell execution (src/config.ts:50)
- python subprocess (ops/daily.py:70)
- python subprocess (ops/daily.py:94)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Agentic, local-first SEO / AEO / GEO control plane: pulls Search Console + GA4, probes your sites, and ranks the next moves. Your LLM writes the proposals; your coding agent works the queue over MCP.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.7.1, the file with digest sha512-cI+sN9JB/AqWop49Njrf3zfbOUXgpWTy0RulMgssM3ICnLfFynjlUgP9GUhuh+VyrB8QDeEHOhKVtStyEx2Hjg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"n-seo": {
"command": "npx",
"args": [
"-y",
"n-seo@0.7.1"
]
}
}
}Or run it directly.
npx -y n-seo@0.7.1Pinned to 0.7.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- n-seo
- Version read
- 0.7.1
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/en-dash-consulting/n-seo
- Commit
- 9b76a8f03478
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/n-seo)About this listing
- Kind
- MCP server
- Category
- Data & analytics
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-05
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.