@mencoro/mcp

MCPattestedlive
v1.0.1MencoroMITUpdated 2d agonpmGitHub

Stdio bridge to the hosted Mencoro MCP server for AI-search (GEO) brand monitoring.

Endpoint healthlive
checked 7 days ago · 397ms · auth required
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). 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.
55Downloads/wk
2d agoLast update
Reads these credentials
  • MENCORO_API_KEYAPI keyoptional

    Mencoro personal access token (mcp_pat_...), created at https://tool.mencoro.com/me/mcp-server

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorMencoro
LicenseMIT
Version1.0.1
Sourcenpm+mcp-registry
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 · e673c98
Dependencies✓ 14 resolved · none vulnerable
Tool surface1 tool · none privileged
Security scan✓ Cleanv1.0.1 · 2d agoHow well does this scan work?
EvalsNone
IndexedSep 16, 2026

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

Tools

1 tool · none privileged
Statically extracted from the published packagev1.0.1 · 2d 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.

mencoro-mcp-setupNo description published

This tool published no description. Forge does not invent one.

0 of 1 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

Stdio bridge to the hosted Mencoro MCP server for AI-search (GEO) brand monitoring.

Keywords
mcpmcp-servermodel-context-protocolmodelcontextprotocolgeogenerative-engine-optimizationai-searchai-visibilityshare-of-voicebrand-monitoringrank-trackingmencoro
Alternatives
Comparing tool surfaces…

Dependency tree

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

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

Topics

Related in search & retrieval