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-MCP · SCANNED OCT 4

GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.

Available components

npm · @tengence/geo-mcp 77
+15 this week 77 Trust /100
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 225 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 1 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 7333 tokens (~130/item across 56 items; 56 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 13 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_article" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 56 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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-mcp. 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-mcp

# add to Claude Code
claude mcp add tengence-team-geo -- npx -y @tengence/geo-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "tengence-team-geo": {
      "command": "npx",
      "args": [
        "-y",
        "@tengence/geo-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tengence-team-geo": {
      "command": "npx",
      "args": [
        "-y",
        "@tengence/geo-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add tengence-team-geo -- npx -y @tengence/geo-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tengence-team-geo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@tengence/geo-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tengence-team-geo --command npx --arg -y --arg @tengence/geo-mcp
# ~/.hermes/config.yaml
mcp_servers:
  tengence-team-geo:
    command: "npx"
    args: ["-y", "@tengence/geo-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tengence-team-geo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@tengence/geo-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add tengence-team-geo -t stdio -c npx -a -y @tengence/geo-mcp
// mcp.json
{
  "mcpServers": {
    "tengence-team-geo": {
      "command": "npx",
      "args": [
        "-y",
        "@tengence/geo-mcp"
      ]
    }
  }
}
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.

  • 28 Sept 26 +15
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 62

    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 4 Oct 2026 · Analysed npm/@tengence/geo-mcp@0.1.1

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.1
Rekor log index 2976193043
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5f6f4370bbc7fed8dd3e41500b6885d7a476d0c87e171fd7acc6daad444193f4c95813d042af9590088e629211af1e5dcfece04a2ce6719816981324b

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 225 packages
Packages resolved 225
Deprecated 3
Stale 52
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 56 exposed · ~7,333 tokens

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 →

Tool Tokens
wechat_mass_send ~237

Mass-send (PUSH to followers) a draft via message/mass/sendall (all followers or one tag) or message/mass/send (specific openids). Subscription accounts get 1 mass-send per day. After a successful send the draft is consumed (auto-deleted from the draft box). If 风险操作保护 is on, the admin must confirm in mp.weixin.qq.com before it really goes out. Safety: execution requires confirm="YES"; dryRun=true only prints the payload.

NameTypeReqDescription
client_msg_idstring–clientmsgid — de-duplicates repeated sends
confirmstring–must be "YES" to actually push to followers (not needed for dryRun)
dryRunboolean–print the payload, do not send
media_idstringyesdraft box media_id (see wechat_status drafts)
sitestring–site key; auto-selected when the workspace holds exactly one site
tag_idnumber–send to one user tag only (omit = all followers)
to_usersarray–specific openids (message/mass/send)

No output schema declared.

No examples provided.

wechat_mass_status ~62

Query a mass-send task status (message/mass/get, msg_id from wechat_mass_send).

NameTypeReqDescription
msg_idnumberyesmass-send task msg_id
sitestring–site key; auto-selected when the workspace holds exactly one site

No output schema declared.

No examples provided.

wechat_stats ~348

Read official-account statistics from the WeChat backend (datacube/*, served WITHOUT the /cgi-bin/ prefix — the /cgi-bin/datacube/* variant is blocked by the egress proxy in this environment). Returns: user growth (user_summary), cumulative users (user_cumulate), upstream/interactive messages (upstream_msg, maxSpan 30d), interface quality (interface_summary, 30d), account biz summary (biz_summary, 30d), daily article reads (article_read, single-day), shares (article_share, single-day) and per-article detail incl. 送达率/读完率/平均阅读时长/跳出 (article_detail, single-day). Read-only. Constraints: data is T+1 (end_date defaults to yesterday); most endpoints allow a <=7d window, the *_read/_share/_detail ones require begin_date === end_date. Requires 用户分析/图文分析 permissions (认证公众号); an unauthorised account returns errcode 48001. Legacy endpoints getarticletotal/getuserread/getusershare are OFFLINE (47009) and have been replaced by the new “发表内容” APIs above.

NameTypeReqDescription
actionstring–report to read; default overview = user_summary + user_cumulate + biz_summary + upstream_msg in one 7-day window
begin_datestring–YYYY-MM-DD; default = 6 days before end_date
end_datestring–YYYY-MM-DD; default = yesterday (data is T+1, today is never available)
sitestring–site key; auto-selected when the workspace holds exactly one site

No output schema declared.

No examples provided.

wechat_status ~96

Read the WeChat official-account backend: the draft box (draft/batchget — media_id + titles) and the mass-sent list (freepublish/batchget — article_id + titles). Read-only. Requires WECHAT_APP_ID/SECRET in the site .env and the current outbound IP whitelisted in mp.weixin.qq.com.

NameTypeReqDescription
sitestring–site key; auto-selected when the workspace holds exactly one site

No output schema declared.

No examples provided.

wechat_sync_progress ~131

Reconcile the channel_plan calendar with the real WeChat backend and auto-fix the DB: draft rows whose media_id is missing from the draft box and not found in the publish list are rolled back to todo (draft_ids cleared); draft rows whose titles appear in the publish list are upgraded to published. Published rows are never downgraded. Returns the reconciliation report. dryRun=true previews without writing.

NameTypeReqDescription
dryRunboolean–preview only — compute and report, do not write to the DB
sitestring–site key; auto-selected when the workspace holds exactly one site

No output schema declared.

No examples provided.

workspace_use ~91

Bind the user workspace directory (call this first): all site config, credentials and output files live under it. Ask the user which directory to use if it was not mentioned; `~` is supported and expanded here.

NameTypeReqDescription
createboolean–create the directory when missing (default false)
pathstringyesabsolute directory path chosen by the user (e.g. ~/my-geo-workspace)

No output schema declared.

No examples provided.

Common questions

What is the Tengence GEO Agent MCP server?

Tengence GEO Agent is an MCP server listed in the public MCP registry as io.github.tengence-team/geo. GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility. This page covers its npm package (@tengence/geo-mcp).

Is the Tengence GEO Agent MCP server safe to use?

Tengence GEO Agent scores 77 out of 100 on VerifyMCP. We recorded 13 known advisories against it as of 4 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.

What tools does the Tengence GEO Agent MCP server expose?

Tengence GEO Agent exposes 56 tools: workspace_use, site_init, site_list, site_status, article_list, and 51 more. Their descriptions and schemas cost roughly 7,333 tokens of context every time the server is loaded.

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 4 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.