compete-mcp

MCPcommunity
v0.6.0io.github.niyonzimabryanMITUpdated 1mo agonpmGitHub

Typed access to monitored competitive changes, evidence, dossiers, research, and collection health.

Works in
ClaudeCursorCopilotGemini

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Needs 1 credential before it runs
  • COMPETE_API_KEYAPI keyrequired

    API key for the target Compete deployment.

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
Authorio.github.niyonzimabryan
LicenseMIT
Version0.6.0
Sourcenpm+mcp-registry
npmcompete-mcp
GitHubniyonzimabryan/sentinel
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 surface29 tools · none privileged
Security scan✓ Cleanv0.5.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

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

Tools

29 tools · none privileged
Statically extracted from the published packagev0.5.0 · 1mo 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.

list_monitorsNo description published

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

get_monitorNo description published

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

changes_sinceNo description published

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

get_reportNo description published

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

get_trendNo description published

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

get_insightsNo description published

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

get_dossierNo description published

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

search_eventsNo description published

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

get_change_evidenceNo description published

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

get_collection_healthNo description published

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

get_focusNo description published

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

update_focusNo description published

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

research_packNo description published

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

submit_researchNo description published

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

get_researchNo description published

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

stack_packNo description published

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

submit_stackNo description published

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

get_stackNo description published

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

suggest_responseNo description published

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

add_monitorNo description published

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

trigger_recheckNo description published

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

scan_claimsNo description published

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

submit_claimsNo description published

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

get_claimsNo description published

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

get_predictionsNo description published

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

refresh_predictionsNo description published

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

get_response_inventoryNo description published

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

submit_response_draftNo description published

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

get_timelapseNo description published

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

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

Typed access to monitored competitive changes, evidence, dossiers, research, and collection health.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

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

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.