@simonmak-ascent/esg-hub-mcp

MCPcommunitylive
v1.4.2UnknownMITUpdated 2d agonpmGitHub

MCP server for the ESG Hub knowledge base — hybrid search, glossary terms, reporting frameworks, industry taxonomy, and knowledge-graph traversal.

Endpoint healthlive
checked 15h ago · 284ms
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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
919Downloads/wk
1Forks
2d agoLast update
Package
AuthorUnknown
LicenseMIT
Version1.4.2
Sourcenpm+mcp-registry
npm@simonmak-ascent/esg-hub-mcp
GitHubsimonmak-ascent/esg-hub
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface15 tools · none privileged
Security scan✓ Cleanv1.4.2 · todayHow well does this scan work?
EvalsNone
IndexedOct 4, 2026

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

Tools

15 tools · none privileged
Statically extracted from the published packagev1.4.2 · 15h 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.

get_server_infoUse this first to confirm the ESG Hub MCP server is reachable and see its version and API base. It performs one liveness round-trip and returns only server metadata — name, version, API base, tool_count, and healthy — and never fails on an unreachable API: it returns healthy=false rather than an er…

Use this first to confirm the ESG Hub MCP server is reachable and see its version and API base. It performs one liveness round-trip and returns only server metadata — name, version, API base, tool_count, and healthy — and never fails on an unreachable API: it returns healthy=false rather than an er…

No input schema was published for this tool.

search_esgNo description published

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

search_contentNo description published

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

get_esg_pageNo description published

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

list_esg_pagesNo description published

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

list_esg_resourcesNo description published

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

get_esg_metadataDiscover the filter vocabulary for the knowledge base: total counts plus the exact `section`, `pillar`, and source-`domain` values with their counts. Call it before list_esg_pages or list_esg_resources so filters match real values; for server version and health use get_server_info. It takes no para…

Discover the filter vocabulary for the knowledge base: total counts plus the exact `section`, `pillar`, and source-`domain` values with their counts. Call it before list_esg_pages or list_esg_resources so filters match real values; for server version and health use get_server_info. It takes no para…

No input schema was published for this tool.

get_termNo description published

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

get_relatedNo description published

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

list_frameworksNo description published

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

list_industriesNo description published

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

list_termsNo description published

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

propose_termNo description published

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

tag_contentNo description published

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

flag_contentNo description published

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

2 of 15 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

MCP server for the ESG Hub knowledge base — hybrid search, glossary terms, reporting frameworks, industry taxonomy, and knowledge-graph traversal.

Keywords
mcpesgsustainabilityknowledge-basegritcfdcsrdai-tools
Alternatives
Comparing tool surfaces…

Tools exposed

15 tools · none privileged · observed 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-10-04 — observed resolution, not a publisher declaration.

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

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

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

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

+41 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.