Local MCP server that installs ProAbono into a website, from the developer IDE: hosted pages, catalogue introspection, customers and subscriptions.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
PROABONO_AGENT_KEYAPI keyrequiredBasic auth username
PROABONO_API_KEYAPI keyrequiredBasic auth password
PROABONO_PORTAL_SECRETAPI keyrequiredHMAC key for the portal security hash
PROABONO_WEBHOOK_SECRETAPI keyrequiredSecret for the notification signature
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge has no scan on record for this entry, so it holds no observation of its tool surface. That is an absence of evidence, not evidence that it exposes no tools.
Local MCP server that installs ProAbono into a website, from the developer IDE: hosted pages, catalogue introspection, customers and subscriptions.
This package has not been scanned yet, so no dependency tree has been resolved.