Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tengence GEO Agent

NPM · TENGENCE-GEO-AGENT

GEO/SEO content engine: planning, writing, gate checks, WordPress publishing, GEO monitoring.

Available components

npm · tengence-geo-agent 46
46 Trust /100

Last scanned (15 hours ago)

Scores higher than 28% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @xmldom/xmldom 0.9.10, reached via @tengence/geo-sdk > @rbbtsn0w/wechat-markdown > mathjax-full > speech-rule-engine > @xmldom/xmldom. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 53 of 227 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to tengence-team/tengence-geo-agent). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Oct 26 0
    • Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
  • 11 Oct 26 46

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Oct 2026 · Analysed npm/tengence-geo-agent@0.1.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo tengence-team/tengence-geo-agent
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/tengence-team/tengence-geo-agent/.github/workflows/release.yml@refs/tags/v0.1.3
Rekor log index 3130788363
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:435b1ceecfe02c81fabc7b777ce34d3fbb63ba786ed1525b82007a26d3fe4a73190cac7b67a328cde9e809315f3c884c7f6a327eca395a197d79f79a7

Background: How many MCP packages publish verified provenance →

Vulnerabilities 13 findings
ID CVE Severity Vector Fix available
GHSA-27p8-2357-5qqv CVE-2026-83608 high yes
GHSA-3px3-54cx-rmw9 CVE-2026-83609 high yes
GHSA-4w3w-2rp5-g8jm CVE-2026-83605 high yes
GHSA-6gmq-8vp8-gcm6 CVE-2026-83610 medium yes
GHSA-6h8r-xr42-gp59 CVE-2026-83611 medium yes
GHSA-6mj3-qw4j-hgrw CVE-2026-83612 high yes
GHSA-8344-3jmq-59r6 CVE-2026-83613 high yes
GHSA-93r5-fhx6-vmg9 CVE-2026-83614 high yes
GHSA-965w-775f-mr7g CVE-2026-83615 high yes
GHSA-c7q8-3ch8-vqpv CVE-2026-83616 high yes
GHSA-g53g-w8rj-fmg7 CVE-2026-83606 high yes
GHSA-vr34-hp96-76pp CVE-2026-83618 high yes
GHSA-w2rr-34g9-rvrj CVE-2026-83607 high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 227 packages
Packages resolved 227
Deprecated 3
Stale 52
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Tengence GEO Agent MCP server?

Tengence GEO Agent runs locally as an npm package, launched with npx -y tengence-geo-agent. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · tengence-geo-agent

# add to Claude Code
claude mcp add com-tengence-geo-agent -- npx -y tengence-geo-agent
Common questions

What is the Tengence GEO Agent MCP server?

Tengence GEO Agent is an MCP server listed in the public MCP registry as com.tengence/geo-agent. GEO/SEO content engine: planning, writing, gate checks, WordPress publishing, GEO monitoring. This page covers its npm package (tengence-geo-agent).

Is the Tengence GEO Agent MCP server safe to use?

Tengence GEO Agent scores 46 out of 100 on VerifyMCP. We recorded 13 known advisories against it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Tengence GEO Agent MCP server still maintained?

Tengence GEO Agent is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Tengence GEO Agent MCP server under?

Tengence GEO Agent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.