Top Repos· Jev Integrations· Harness· Last updated 2026-09-21

AkashPriyadarshii / jev-seo

“100% free ₹0 agent-first SEO & GEO CLI suite and MCP server in Rust replacing Semrush and OpenSEO via DuckDuckGo and TypeSafe Jev System One”

Jev Integrations rank #39In Harness #18

• 23Stars
• —Stars Δ / 1d
• —Stars Δ / 7d
• —Stars Δ / 30d
• 2Forks
• 0Watchers

GitHub ↗Official docs ↗Back to ranking

TL;DR

AkashPriyadarshii/jev-seo showed up as Jev / System One related work: Agent skill, MCP, or harness that routes work through Jev-style decisions.

The author describes it as: “100% free ₹0 agent-first SEO & GEO CLI suite and MCP server in Rust replacing Semrush and OpenSEO via DuckDuckGo and TypeSafe Jev System One” That is their claim, not a bench this site ran.

Who it’s for

• Agent / harness authors who need a typed gate, route, or prune step
• Anyone who needs the unofficial line: jev.pro does not issue keys and is not TypeSafe

What’s inside

Top-level entries on GitHub at generation time: .github, .gitignore, AGENTS.md, CHANGELOG.md, CLAUDE.md, Cargo.lock, Cargo.toml, LICENSE, README.md, STATE.md, docs, memory, src. Read those before you trust a one-line install.

How to use

1. Clone and follow the author’s Rust toolchain. Do not invent a package name.

git clone https://github.com/AkashPriyadarshii/jev-seo.git
cd jev-seo

2. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
3. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "AkashPriyadarshii/jev-seo", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

Put Jev on one real brief

Wire AkashPriyadarshii/jev-seo so one real state (ticket, diff, or utterance) becomes a Choice plus a Noul. Do not ask Jev to write the user-facing reply.

Schema-safe ≠ correct

On a case AkashPriyadarshii/jev-seo gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.