@iliasabk/geolint

MCPattested

v0.4.0io.github.iliasabkMITUpdated 1d agonpm GitHub

ESLint for AI search: audits AI-crawler access, llms.txt, schema and citability.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

2GitHub stars

2Forks

1d agoLast update

Package

Authorio.github.iliasabk

LicenseMIT

Version0.4.0

Sourcenpm+mcp-registry

npm@iliasabk/geolint

GitHubiliasabk/geolint

SBOMCycloneDX 1.6 ↓

Trust Status

A

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 8bfa738

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface5 tools · none privileged

Security scan✓ Cleanv0.4.0 · todayHow well does this scan work?

EvalsNone

IndexedSep 15, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

5 tools · none privileged

Statically extracted from the published packagev0.4.0 · 14h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

audit_urlAudit a URL for AI-search readiness: GEO score (0–100), grade, per-category scores and findings (AI crawler access, llms.txt, structured data, citability, technical).

Audit a URL for AI-search readiness: GEO score (0–100), grade, per-category scores and findings (AI crawler access, llms.txt, structured data, citability, technical).

No input schema was published for this tool.

generate_llms_txtCrawl a site and generate a spec-conformant llms.txt document listing its pages, grouped by top-level section.

Crawl a site and generate a spec-conformant llms.txt document listing its pages, grouped by top-level section.

No input schema was published for this tool.

list_rulesList geolint audit rules (id, category, severity, title, description).

List geolint audit rules (id, category, severity, title, description).

No input schema was published for this tool.

list_ai_botsList known AI crawler/fetcher user-agent tokens: vendor, purpose (training/search/user-fetch/mixed), documented robots.txt behavior, retired flag.

List known AI crawler/fetcher user-agent tokens: vendor, purpose (training/search/user-fetch/mixed), documented robots.txt behavior, retired flag.

No input schema was published for this tool.

compare_urlsAudit two URLs and compare them: score delta plus findings added in B and resolved vs A.

Audit two URLs and compare them: score delta plus findings added in B and resolved vs A.

No input schema was published for this tool.

5 of 5 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

ESLint for AI search: audits AI-crawler access, llms.txt, schema and citability.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

5 tools · none privileged · observed 2026-09-17 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-17 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.6.5
cheerio1.2.011 dependencies
- parse57.3.0+1 not drawn
- undici7.29.1
- domutils3.2.2+1 not drawn2 dependencies
  - domhandler5.0.3+1 not drawn
  - dom-serializer2.0.0+2 not drawn1 dependency
    domhandler5.0.3shown above+1 not drawn
- domhandler5.0.3shown above+1 not drawn
- htmlparser210.1.0+2 not drawn2 dependencies
  - domutils3.2.2shown above+1 not drawn
  - domhandler5.0.3shown above+1 not drawn
- cheerio-select2.1.0+4 not drawn2 dependencies
  - domutils3.2.2shown above+1 not drawn
  - domhandler5.0.3shown above+1 not drawn
- dom-serializer2.0.0shown above+2 not drawn
- whatwg-mimetype4.0.0
- encoding-sniffer0.2.1+2 not drawn
- parse5-parser-stream7.1.21 dependency
  - parse57.3.0shown above+1 not drawn
- parse5-htmlparser2-tree-adapter7.1.02 dependencies
  - parse57.3.0shown above+1 not drawn
  - domhandler5.0.3shown above+1 not drawn
commander12.1.0
@modelcontextprotocol/sdk1.30.0+7 not drawn10 dependencies
- ajv8.20.0+4 not drawn
- zod4.6.5shown above
- cors2.8.6+2 not drawn
- hono4.13.8
- jose6.2.12
- express5.2.1incomplete+19 not drawn
- raw-body3.0.2incomplete
- ajv-formats3.0.1incomplete
- cross-spawn7.0.6incomplete
- eventsource3.0.7incomplete

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

56 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 56

mime-types ^3.0.0 — required by express@5.2.1package cap reached
proxy-addr ^2.0.7 — required by express@5.2.1package cap reached
body-parser ^2.2.1 — required by express@5.2.1package cap reached
escape-html ^1.0.3 — required by express@5.2.1package cap reached
http-errors ^2.0.0 — required by express@5.2.1package cap reached
on-finished ^2.4.1 — required by express@5.2.1package cap reached
content-type ^1.0.5 — required by express@5.2.1package cap reached
finalhandler ^2.1.0 — required by express@5.2.1package cap reached
range-parser ^1.2.1 — required by express@5.2.1package cap reached
serve-static ^2.2.0 — required by express@5.2.1package cap reached
cookie-signature ^1.2.1 — required by express@5.2.1package cap reached
merge-descriptors ^2.0.0 — required by express@5.2.1package cap reached

+44 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.