geo-mcp@0.1.2
CAUTIONPublisher claims: "GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Server started and answered tools/list.- Tested
- MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with real credentials
Before you give it your token
- It will ask for
BAIDU_TOKENBING_WEBMASTER_API_KEYGEO_MCP_TOKENConfiguration, not credentials: APP_ID, BAIDU_SITE, DB_DATABASE, GEO_MCP_PORT, INDEXNOW_HOST, INDEXNOW_KEY, INDEXNOW_KEY_LOCATION, SITE_DOMAIN- Where it talks to
- tengence.com (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- what the tools do when called with real credentials
Connect it with a scoped credential, under the guard. It asks for BAIDU_TOKEN, BING_WEBMASTER_API_KEY, GEO_MCP_TOKEN and talks to tengence.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-16 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 35 s · 2 scenariosStatic findings
'Scaffold a site inside the bound workspace: <workspace>/<key>/{config,data/inbox,data/reports,.env} (idempotent, never overwrites existing files)',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if (!apiKey) return fail(new Error('BING_WEBMASTER_API_KEY not configured in the site .env'));Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.description: 'Site status: config paths, .env readiness, DB driver and SQLite init state',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* npx -y @tengence/geo-mcp-httpFix: Pin versions and sources; vendor anything fetched at install time.'Write to Bing Webmaster: submit URL(s) (comma-separated = batch, ≤10000 per call). Requires BING_WEBMASTER_API_KEY in the site .env.',Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…uota / query stats / crawl issues). Requires BING_WEBMASTER_API_KEY in the site .env. Note: Bing trimmed its JSON API on 2026-08-31 (GetPages/GetSitemaps/GetTraffic…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* it without a local checkout via `npx -y @tengence/geo-mcp` (the package resolves itsFix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @tengence/geo-mcp@0.1.2 as of 14 min ago. This is the package itself, not its dependencies.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim tengence: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.